Problem
One request becomes three conversations
An employee needs a letter confirming their employment. They email HR. The next day, they mention it to their manager. When they haven’t heard back, they send a message in Teams. Now three conversations concern the same request. The employee still doesn’t know who is handling it.
Each follow-up makes sense. They have a deadline and need an answer. But someone must connect the conversations, check what has already happened, and decide who should respond. That coordination can become more work than preparing the letter.
Examples
Follow one request through the business
Consider a fictional employee, Alex, who needs an employment-verification letter by Friday. Alex emails the shared HR inbox on Monday. One HR colleague reads the message but needs to confirm what the letter must include. Before they reply, Alex asks their manager for help.
The manager forwards the request to another HR colleague. That person begins gathering information, unaware someone else has already picked it up. On Wednesday, Alex follows up in Teams. A third person asks what the request concerns. Alex explains it again.
Nobody deliberately ignored the request. Each person saw a different part of it. The employee’s follow-ups became the mechanism for keeping the work moving.
Solutions
Give the request a home
A useful process lets the employee and the people handling the work see whether the request has been received, who owns it, what information is missing, and when to expect an update.
For Alex’s letter, a useful acknowledgment might say: “Your request has been received. Morgan in HR is handling it. Please confirm the recipient and required date. We’ll update you by Wednesday.” That response establishes ownership, asks for specific information, and gives Alex a reason to wait before contacting someone else.
The employee should not need to understand the company’s internal structure to find the person who can help.
Where automation can reduce the coordination
Start by checking what your existing HR or service-request software supports. Request records, assignment, acknowledgments, and status updates may already be available. For one agreed request category, a workflow could:
- Create a record when the request arrives.
- Ask for the information needed to proceed.
- Assign a responsible person and a backup.
- Send an update when the next action changes.
- Flag requests that have passed an agreed response date.
- Record delivery and provide a way to report an unresolved issue.
Connect follow-ups and keep review explicit
Follow-ups should attach to the existing request where possible. When a connection is uncertain, a person should check before combining records. If an update fails, make that failure visible to an owner and retain a manual way to move the request forward.
Preparing the letter may still require an authorized HR reviewer. Automation can collect the details and prepare the work without deciding what the company should certify.
Make progress visible without exposing private details
An employee needs to see what is happening with their own request. That does not mean their manager—or everyone with access to a general task board—needs to see its contents. Define who can view the request, supporting documents, and internal notes. Sensitive matters need an appropriate private route.
Even a simple status can be useful: received, waiting for your information, under review, or delivered. Each should explain the next action clearly enough that the employee does not have to ask what it means.
Check whether the employee actually got help
Dovetail’s HR Service Delivery Pulse Survey, conducted in December 2025, found that 56% of respondents relied on shared inboxes or spreadsheets to manage employee questions. The vendor survey covered midsize and large organizations; its public summary does not disclose the sample size. It provides context for this pattern, rather than a benchmark for every business.
To understand your own process, review a few recently completed requests from one category. Count how often employees followed up, repeated information, or were redirected. Record how long requests waited without an owner or next action. Check whether “completed” meant the employee received what they needed.
After making a change, compare those same measures. Include the effort required to correct routing mistakes and maintain the workflow. A faster acknowledgment helps. A request that reaches the right person and gets resolved helps more.
How Zoevin helps
Bring one request that took too many conversations
At Zoevin, I build scoped automations in your business’s own environment and hand them over on an agreed date.
If a routine employee request keeps becoming several conversations, bring one recent example. We can follow where it started, who became involved, and what someone had to explain or chase more than once.
- Discuss one request and the repeated work around it.
- Identify a possible automation scope and the decisions your team retains.
Zoevin has no delivered automation projects yet. Discovery names the seam. If I build, I hand it over on a written date. You get the workflow, the logins, and the write-up. I don't stay on to run it. You buy the software.
Evidence
Sources
Primary reporting first. Open the sources yourself rather than taking this account alone.
primary source
Dovetail — HR Service Delivery Pulse Survey findingsPublished February 4, 2026; survey conducted December 2025. Vendor research among HR professionals in midsize and large organizations; the public summary does not disclose sample size. The 56% finding describes respondents, not all businesses. Alex’s story is a fictional teaching example, not a client result.