AI × Customer Service
How to test ticket assistance, voice, routing, self-service, quality review, and WhatsApp without hiding uncertainty or removing consent, accessibility, and human escalation.
Chatbots & Virtual Agents
Begin with retrieval and draft assistance for a narrow, low-risk task; expand only when reviewed evidence supports it.
Fragmented support context
Policies, order data, and prior contact are spread across tools → repeated work and inconsistent answers are hard to measure → accessibility and escalation vary.
Grounded draft with safe handoff
Retrieve from approved, versioned sources → cite the evidence → draft an accessible response → disclose automation where appropriate → route uncertainty, complaints, distress, exceptions, and human requests → require approval for refunds, credits, cancellations, or account changes.
Baseline worksheet: document current ticket count, handling-time assumption, and loaded hourly cost. It does not estimate automation or savings.
Evidence to collect
Voice Agents
Voice assistance needs explicit disclosure, recording consent where required, an accessible alternative, and immediate human escalation.
Notice, consent, identity checks, language support, recording retention, and escalation are inconsistent → sensitive content can be captured unnecessarily.
Disclose the automated system → obtain required recording consent → offer keypad/text/human alternatives → authenticate before account data → minimise/redact recordings → escalate uncertainty or sensitive intent → keep bookings, payments, and account changes as approved drafts.
Pilot evidence to collect
Ticket Routing & Prioritisation
Routing can assist triage, but urgency, language, sentiment, and intent labels require evaluation and a safe manual path.
Queue rules and categories are undocumented → reroutes and missed urgency are not measured → labels can encode subjective or biased assumptions.
Define routing taxonomy and service capacity → test with representative languages and groups → use confidence thresholds → default uncertainty to manual triage → preserve override → monitor missed urgency, reroutes, fairness, and SLA impact.
Pilot evidence to collect
Self-Service
Self-service is useful when it gives a correct, accessible answer and a clear path to a person—not when it merely suppresses contact.
Policies are stale or difficult to navigate → search does not match customer language → contact paths are hidden → repeat contacts are mislabelled as deflection.
Version approved sources → retrieve and cite the applicable passage → show effective date and uncertainty → use accessible interaction patterns → offer human contact at every step → measure verified completion and repeat contact.
Pilot evidence to collect
Quality Assurance
Automated review can broaden screening, but model scores are not ground truth and must not silently determine employee discipline.
Sampling and rubric choices are undocumented → rare high-severity failures may be missed → employees cannot understand or contest conclusions.
Define a task-specific rubric with staff input → stratify sampling by risk → validate model findings against trained reviewers → test languages and groups → expose evidence and uncertainty → require human review and an appeal path before employment consequences.
Pilot evidence to collect
WhatsApp Business
WhatsApp can be one consented support channel. Design for current platform rules, accessible alternatives, and reliable human handoff.
Channel eligibility, template rules, consent, identity, accessibility, and handoff are handled inconsistently → messages can expose account information or persist too long.
Confirm opt-in and conversation window → disclose assistance → authenticate before account data → retrieve approved sources → minimise data → provide accessible alternatives → hand off uncertainty and human requests → approve consequential actions separately.
Baseline worksheet: document current monthly inquiries and reported after-hours share. It does not estimate resolution or repeat purchase.
Pilot evidence to collect
Reference pattern: a controlled support workflow.
Start with read-only retrieval and drafts, evaluated on representative and adversarial conversations. Separate tenants; minimise and encrypt data; use least-privilege identities; enforce consent, suppression, identity checks, accessibility, retention, redaction, and human escalation outside the model. Refunds, credits, returns, bookings, messages, and account changes stay PAUSED until deterministic policy validates an unexpired signed approval bound to the exact customer, resource, values, and time window. Require caps, idempotency, complete logs, stop controls, and tested rollback.
Vendor discovery links — verify before use
These links identify products mentioned in the earlier lesson. They do not prove a performance result. Locate precise, dated official documentation, terms, security/privacy material, and case methodology before relying on a feature or claim.
- Intercom Fin 2 — intercom.com
- Klarna AI — klarna.com
- Zendesk — zendesk.com
- Ada.cx — ada.cx
- Bland AI — bland.ai
- Retell AI — retell.ai
- Vapi — vapi.ai
- Zendesk Triage — zendesk.com
- Forethought Solve — forethought.ai
- SentiSum — sentisum.com
- Stonly — stonly.com
- Shopify AI — shopify.com
- Klaus / Zendesk QA — klausapp.com
- Observe.AI — observe.ai
- CallMiner — callminer.com
- Haptik — haptik.ai
- WATI — wati.io
- Zoko — zoko.io