The situation
Fictional planning example. These are sample decisions, not customer results or a demonstration of a live configuration.
A caller to a fictional multi-department business disputes an invoice and reports a separate service interruption. Finance and Service have different responsibilities. Finance is unavailable, while Service can receive a request for review.
Sample intake record
Use the distinction between reported information and confirmed outcomes when reviewing your own process.
| Field | Sample entry | How to use it |
|---|---|---|
| Billing issue | Caller disputes an invoice item. | Record the question without deciding whether the charge is valid. |
| Service issue | Caller reports an interruption. | Capture reported symptoms; do not assume cause or scope. |
| Account reference | Caller supplies the reference allowed by the intake process. | Apply approved identity and disclosure checks before sharing account information. |
| Department owners | Finance for billing; Service for the interruption. | Keep separate ownership and status for each request. |
| Coordination | Named customer-request coordinator. | Illustrative role; the business must assign its actual owner. |
Walk through the decisions
- Separate the requests. Confirm that the caller needs help with two issues. Give each its own recorded next step rather than treating a successful transfer as resolution of both.
- Apply the department rules. Use the approved intake and urgency criteria for Service. Billing remains a Finance question; neither the agent nor this example determines its outcome.
- Handle unavailable Finance. Use the defined message or follow-up route. Preserve the invoice question and any permitted reference details without promising a decision or response time.
- Confirm coordination. Identify who checks that both departments receive the relevant context. Record which request was routed and which still awaits review.
Example handoff note
Billing dispute awaits Finance review; no adjustment approved. Service interruption reported and directed to the configured Service review path; diagnosis unknown. Coordination owner checks both request statuses. A routed request is not a resolved request.
When the routine path does not fit
- The caller requests restricted account details: Use the organization’s approved identity and authorization process before disclosure.
- The Service route is also unavailable: Apply its documented backup path and keep the interruption request open for the responsible owner.
- The two departments disagree about ownership: Send the conflict to the designated business escalation owner rather than cycling the caller between teams.
Use this with your team
Who owns each request? Who coordinates cross-department follow-up? What information may be disclosed? Which signal shows that a request is still awaiting review?
Replace the fictional choices with your approved process before configuring service. This page does not collect or send your answers.