Customer onboarding checklist

1. Read the request and the order.
2. Check it against the refund policy.
3. Draft the reply.
4. A person approves the refund and the reply.
5. Record the outcome.

Needs from you: Refund request; Order record.

What it needs connected: Support inbox; Customer records, read only.

Where a person is designed to decide: A person approves the refund and the reply.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: UPI.

1. Read the message and label topic and urgency.
2. Draft a reply from your approved answers.
3. A person edits and sends the reply.
4. Escalate to a named person if it is unusual.
5. Close the ticket when the customer confirms.

Needs from you: Customer message; Approved answers.

What it needs connected: Support inbox.

Where a person is designed to decide: A person edits and sends the reply.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp, Hindi and regional.

1. Read each ticket.
2. Classify it by topic and urgency.
3. Suggest a reply from your approved answers.
4. Route urgent or unusual tickets to a named person.

Needs from you: Incoming tickets; Approved answers; Escalation rules.

What it needs connected: Support inbox.

Where a person is designed to decide: Route urgent or unusual tickets to a named person.

These approval steps describe how an entry is designed. Whether a deployment enforces them depends on how it is set up with you, and no run has been measured yet.

India: WhatsApp, Hindi and regional.