- Customer
Where is my order 48213?
- Agent
Failed delivery yesterday, the carrier is retrying today. No confirmed time yet; I will write as soon as there is one.
Platform · Layer 05
The work happens in the channel.
Voice, WhatsApp, email, Slack, Teams and web chat, with the Agent Console showing all of it against the KPI you signed.

Components
What runs in this layer.
Hi, where is my order 48213? It said today.
- Looking up order 48213 in the OMS
Hi Ana. Order 48213 is out for delivery, arriving between 4 and 6 pm. Do you want to change the address or leave instructions for the driver?
Leave it with the doorman please
Done. I added the instruction to the delivery and the driver has it. You will get a message when it is delivered.
Resolved without a human
Ticket #48213 · 1.9 s to first answer · CSAT survey queued
06 components in this layer
- In production× 5
- Pilot× 1
Voice
Vapi, Retell or our own stack, transcripts written back.
WhatsApp Business
Official API, approved templates, hand-off in the same thread.
Email and web chat
Shared inboxes and embedded chat, same agent, same trail.
Slack and Microsoft Teams
Ask, approve and get the weekly report in the channel.
Internal apps
Queues, cases and approvals in your stack and design system.
Agent Console
KPI vs baseline, evals, cost, audit log and approvals.
In production: A real client, or DaCodes itself labeled as internal use, with a KPI measured in the Proof Ledger.
Channels
Six channels, one agent, one audit trail.
Moving from WhatsApp to a call does not restart the conversation.
- Voice
- Web chat
One conversation, three channels
- Customer
It failed again. I would rather get a refund.
- Agent
Both attempts are in your thread. The refund is above my limit, so a person decides it now.
- Agent
Refund request, order 48213: second failed delivery. Evidence attached.
- Ops lead
Approved.
- System
Written to the CRM, customer notified.
Same case, same context, same audit trail
- Case 48213
- Customer, order, shipment, carrier
- Refund rule and approval threshold
- Every step in the audit log
Illustrative hand-off with demo data, drawn from retail deployments in México. Sep 2026.
Internal apps
Screens for the people beside the agent.
Queues
What the agent handled, what it left for a person, sorted by SLA.
Case views
The full thread, the evidence the agent used and the action it proposes.
Approvals
One screen, one decision, logged with who and when.
Assembled from DaCodes Solutions modules: weeks of configuration, not months of development.
Agent Console
Every agent, against the number you signed.
One view per client, the same one the pod uses in the QBR.
What the Console shows
- 01Agents and their status
- 02Agreed KPI vs baseline, with trend
- 03Evals, drift and cost per run
- 04Audit log and pending approvals
Available for clients in production. Login in the next version.
KPI Contract
90d
Autonomous resolution, tier 1
28.0%
Cost per ticket
$0.74
$5.20 → $0.74
Evals · last run
96.2%
312 · pass
Spend this month
$2,140
alert at $3,000
Pending approvals
2
Audit log
- 09:44resolved ticket #48213 · refund policy · 1.9 s
- 09:43escalated #48219 to human · sentiment low
- 09:42eval batch 312 · 96.2% pass · no drift
- 09:41invoice INV-77120 posted to SAP · 3 fields verified
Demo data. Agent Console v0.1, Sep 2026.
Questions
Architects ask.
Talk to an architect
45 minutes with the people who run the platform. No slides.
We reply in under one business day.
