Begin with the customer’s actual concern
Imagine a customer whose delivery has not arrived. The first reply should acknowledge the inconvenience and explain that the team is checking. It should not describe internal systems or promise a delivery time that has not been verified.
Illustrative customer reply: “I’m sorry your order hasn’t arrived. I understand the delay is frustrating. I’m checking the latest information and will help you with the next step.”
Check the facts and coordinate internally
With the appropriate customer details and access, the agent checks the order and available shipment information. If the record is missing or contradictory, the next step is clarification or a human handoff, not an invented explanation.
In this example, a delivery delay qualifies for a proposed credit under the team’s policy, but the credit still requires manager approval. The internal request includes the verified delay, the policy basis and the proposed action.
| Customer conversation | Internal coordination |
|---|---|
| “I’m sorry for the delay. I’m checking this for you.” | Look up the order and verify the shipment status. |
| A factual update when information is available. | Ask the manager to approve the proposed credit. |
| Explain the approved resolution and next step. | After approval, apply the permitted action and record the result. |
Keep the approval separate from execution
A proposed credit is not an issued credit. While approval is pending, the agent can keep the customer informed without saying the credit has been applied. If the request is declined, the team selects a different next step.
The record should distinguish requested, approved and completed actions. This makes it possible for the next teammate to see what actually happened.
Give the whole service team shared context
A department can include different roles for initial response, investigation and escalations. Passing a case between them should preserve the customer’s request, confirmed facts, earlier replies and the outstanding decision, within each role’s access.
Start with one service journey and test missing records, unavailable systems and a customer asking for a person. Expand the scope only after the team can reliably handle those cases.
Explore how AI agents for customer service work as a departmentKeep context across channels
Common questions
Can the agent issue a credit without manager approval?
In this example, no. It prepares the request and waits for the designated manager. Actual permissions and approval requirements must be defined for each implementation.
What if the agent cannot find the order?
It should ask for the missing details or route the case to a person. It should not invent shipment information or make an unsupported delivery promise.
What does the human representative receive?
The customer’s request, verified case information, earlier replies, actions already taken and the decision still needed, limited to the permitted scope.
About this guide
Prepared by the Uniforce editorial team. Examples illustrate proposed workflows, not customer results. The role’s access, actions and review requirements depend on the configured implementation.
