# Support handoff example

Illustrative sample created by Remote Partners AI, a marketing partner of Azpired. This is fictional training material, not a client record or a result. Adapt it with your delivery provider before use.

## Example: a routine appointment request needs owner approval

- Record: DEMO-001; no real customer details.
- Request: customer asks to move a routine appointment to a time outside approved booking hours.
- Action completed: recorded the requested window and added an internal note.
- Action not taken: no appointment change, price promise or exception approval.
- Reason for escalation: requested time is outside the written booking rule.
- Next owner: designated scheduling supervisor (replace with your real role/contact).
- Due time: supervisor-defined callback deadline; confirm before promising a time.
- Customer communication: explain that the scheduling owner will review the request; do not promise availability.
- Closure evidence: record supervisor decision, actual customer callback and any approved update.

## Reusable blank fields

Request/reference:
Current approved system record:
Request and urgency:
Required details captured:
Action completed:
Action blocked or not attempted:
Escalation reason:
Next owner and backup:
Agreed deadline:
Customer communication:
Final decision and callback evidence:

Keep sensitive data in approved systems. This template does not authorize access, regulated decisions or customer commitments.
