# Example support playbook: one order-status queue

Original Culvion Technologies example · 7 November 2026

ILLUSTRATIVE ONLY. The business, contacts and workflow below are fictional. This is a discussion artifact, not a description of a client operation, a service commitment or a certification.

## 1. The example scope

A retailer wants help with order-status questions in one email queue. The client supplies current order information, delivery guidance and approved response examples. Service hours, demand, staffing, access and commercial terms must be agreed separately.

Included example work:

- Read the question and find the relevant order using the approved process.
- Check the available delivery information.
- Explain the recorded status without guessing a delivery date.
- Record the action and next step in the case.
- Escalate an exception with the context needed by its receiving owner.

Outside this example scope:

- Approving refunds, compensation or exceptions to policy.
- Changing a delivery address without the client's approved checks.
- Providing payment-card, legal or other specialist advice.
- Promising a delivery or response time that has not been agreed.

## 2. Before an agent handles the queue

| Input | Client-side owner | Readiness evidence to agree |
| --- | --- | --- |
| Product and delivery guidance | Knowledge owner | Current, approved source and a route for unclear instructions |
| Account and order checks | Access owner | The permitted identification process and tested permissions |
| Decision limits | Business owner | Written actions agents may take and actions needing approval |
| Escalation route | Receiving specialist | Named role, required context and agreed review window |
| Tone examples | Brand/service owner | Examples of clear, respectful answers for review |
| Reporting | Both teams | Definitions, review owner and first review arrangement |

The role labels identify responsibilities to assign. They do not identify Culvion employees or establish an existing control environment.

## 3. Example handling sequence

1. Read the full request. Identify the question and any relevant earlier contact.
2. Follow the approved account/order checks. Do not ask for unnecessary sensitive information.
3. Open the permitted order record and note the source and time checked.
4. Compare the available status with the approved guidance.
5. If the next action is within the agreed scope, explain it plainly and complete it.
6. If a decision or missing information is needed, use the escalation map below.
7. Record the outcome, remaining action, owner and customer-update arrangement.

## 4. Example escalation map

| Situation | Agent action | Receiving role | Context to hand over |
| --- | --- | --- | --- |
| Status is missing or inconsistent | Stop short of a delivery promise; identify the gap | Fulfilment owner | Question, record checked, missing information and customer impact |
| Customer requests an exception or refund | Capture the request without approving it | Client decision-maker | Reason, relevant order context and decision requested |
| Request needs identity or access review | Follow the approved stop/escalation instruction | Access/security owner | Minimum necessary reference and the issue requiring review |
| Complaint remains unresolved | Acknowledge the concern and follow the escalation rule | Service owner | Earlier actions, unresolved concern and proposed next update |
| Tool is unavailable | Use the agreed fallback or hold route | System/operations owner | Affected task, time, observed error and unfinished work |

Actual recipients, priorities and update windows are project-specific. No automatic response-time promise is made by this sample.

## 5. A useful escalation record

- Case reference:
- Reason for contact:
- Customer impact:
- Approved information checked:
- Work already completed:
- Remaining question or decision:
- Receiving owner:
- Priority and reason:
- Next customer update, owner and agreed timing:
- Information that must not be copied into the handoff:

## 6. Example response pattern

“I checked the order record and the latest delivery status is incomplete. I’ve passed the request to the fulfilment owner to confirm the next step. We will update you through the channel and timing agreed for this case.”

This is a writing pattern, not a message to use without adapting the actual next action and update arrangement. If no update timing has been agreed, that is an open item to resolve before the response is complete.

## 7. First-review questions

- Was the information accurate and traceable to an approved source?
- Did the agent remain within the decision limit?
- Can the next owner continue without repeating the investigation?
- Does the case show what happens next and who will update the customer?
- Did any missing guidance require a change to the playbook?

Agree the review criteria and sample with the client before using a score to assess live work.