Gurugram health-insurance broker, 40 staff, leads from Google Ads and web forms, Zoho CRM, WhatsApp Business app on two phones
Weeks 1–2Use-case pickTag 500 past chats by enquiry type; score each type by volume, risk and data accessTwo jobs chosen: policy FAQ answers and renewal-date lookups; claim advice stays with humans
Weeks 2–3Data and guardrailsLoad approved policy wordings into a retrieval index; write refusal rules for medical and claim-outcome questionsSigned-off knowledge base and a list of questions the agent must never answer
Weeks 3–4Tool accessConnect read-only Zoho CRM lookups and a create-callback tool through scoped API keysAgent can read policy status and book callbacks but cannot edit records
Weeks 4–5Evaluation setBuild 200 real questions with expected answers, including 20 that must be refused; run model and prompt variants against themModel choice and pass threshold agreed before any customer sees the agent
Weeks 5–6Shadow runAgent drafts replies; advisers approve or edit them in the WhatsApp inbox; every edit is loggedEdit rate per intent decides automation; rule of thumb: an intent goes automatic below 5% edits across 100+ drafts
Weeks 7–8Live on WhatsAppLow-risk intents go automatic through the BSP; other chats hand over to an adviser with a summaryGo-live with human handover and daily transcript review
Weeks 9–10Tune and hand overWeekly review of failed answers, escalations and cost per conversation; runbook and dashboards handed overBroker's team owns prompts, eval set and the monthly review
Where it starts2,500 enquiries/month, median first reply 6 hours, 3 advisers spend most of their day answering the same policy questions, no record of unanswered chats
Where it endsThe broker has a WhatsApp agent answering routine policy queries with logged handovers to advisers. Weekly they watch automated resolution rate, escalation accuracy and cost per resolved conversation.