cleandataengineering.aiAgent Harness, drawn simply
You are here: Tech stack › CH · Channels & human desk

Agent Harness Tutorial · Tech stack

CH · Channels & human desk

How customers and staff reach the agent, and how a person takes over with the full history. Family: Act · one turn, in order.

AZURE OPTIONSCommunication Services◐ planned: WhatsApp, SMS, emailBot Service◐ planned: Teams connector onlyWeb PubSub· considered: push replies to the windowDynamics 365 Contact Center· considered: not pickedOUR CHOICEOur chat pagestarlette, builtDesk API /opsfastapi, builtChatwootplanned: web chat + deskOPEN-SOURCE OPTIONSChatwoot◐ planned: chat + desk without building oneA Next.js window alone· considered: 6 more things to buildWHO DOES THE WORKAzure gives 50% · we code once 35% · each agent team still does 15%
Dark boxes are what we run. Solid boxes are used or planned; dashed boxes were considered or dropped (crossed). The bar: grey is what Azure gives, dark is what we code once, hatched is what each agent team writes.
Why our choiceChatwoot gives the web chat and the human desk without us building a desk. Azure covers the messaging channels.
OptionWhere fromVerdictWhy
Our chat pageours✓ chosenstarlette, built
Desk API /opsours✓ chosenfastapi, built
Chatwootours✓ chosenplanned: web chat + desk
Communication ServicesAzure◐ plannedWhatsApp, SMS, email
Bot ServiceAzure◐ plannedTeams connector only
Web PubSubAzure· consideredpush replies to the window
Dynamics 365 Contact CenterAzure· considerednot picked
Chatwootopen source◐ plannedchat + desk without building one
A Next.js window aloneopen source· considered6 more things to build

Not built yet in the claims assistant; designed in the Series.

Compared: Which channels and which human desk?

Next.js window + …open sourcechosenNext.js window on…oursrejectedChatwoot widget +…open sourcerejected for customersAzure Communicati…AzurechosenAzure Bot ServiceAzureTeams onlyDynamics 365 Cont…vendorwhere it exists
Dark: what we chose. Crossed and dashed: rejected or not for us. From the Series.
OptionFromVerdictCustomer windowStaff desk and hand-offChannelsVerdict reason
Next.js window + Chatwoot deskopen sourcechosenbest: our cards, upload, brandgood: queues, hand-offweb, WhatsApp, SMS, emailour default
Next.js window onlyoursrejectedbestnone: build itweb onlya contact centre isn't our job
Chatwoot widget + deskopen sourcerejected for customersgenericgoodweb, WhatsApp, SMS, emailclaims needs rich cards, upload
Azure Communication ServicesAzurechosenno windowno deskWhatsApp, SMS, emailthe channel pipes
Azure Bot ServiceAzureTeams onlynono human deskTeams connectornever as the desk
Dynamics 365 Contact Centervendorwhere it existsits ownbest: staff already use itmanyonly if already owned
DecisionCustomers use our own Next.js chat window, staff use the Chatwoot desk, and Communication Services carries WhatsApp, SMS and email. Where the insurer already runs a contact centre such as Dynamics 365, we hand off into that instead of Chatwoot.