REQUEST HANDLING · Workflow idea
A simple service interaction needs a clear starting point, a consistent way to handle the request, and a useful reply. Define what information is expected, decide what should happen, and return a response that makes the outcome understandable.
01 / The starting point
An incoming request containing details for a straightforward service task
“Review the request, handle the agreed simple task, and return a clear response that reflects what happened.”
02 / The work
Helps teams offer a simple, repeatable request-and-response experience for routine service tasks.
Gather the information needed to understand what the person is asking for.
Identify missing or unclear details and seek clarification when the next step is not obvious.
Carry out only the action the team has defined for this kind of request.
Explain whether the request was completed and include the relevant result or next step.
Refer unusual, sensitive, or unsuccessful cases to someone who can make the right decision.
03 / The result
A consistent reply with the outcome of the request and a helpful next step when it cannot be completed as expected.
Customer support · Example outcome
A consistent reply with the outcome of the request and a helpful next step when it cannot be completed as expected.
Keep the information requested to a minimum and make unclear, sensitive, or consequential requests available for human review before taking action.
04 / Make it yours
A few choices shape the work around your team.
Describe the kinds of routine requests this service should handle and which ones need a person.
Ask only for details that are necessary to understand and respond to the request.
Prepare clear success, clarification, and unable-to-complete messages for the people making requests.
Check that missing information and exceptional cases are safely routed for human review.