aminobots assist · standalone product
customer ops across every channel.
Multi-channel ops agent across WhatsApp, voice, web, email, and Slack. Identifier · Support · Expert · HIL routing. T0 rules pre-filter strips half the traffic before any LLM call.
01 · capabilities
what's inside
- Multi-channelWhatsApp Business · voice (IVR + TTS) · web chat · email · Slack — one conversation across channels.
- 4-agent routingIdentifier classifies. Support resolves L1. Expert handles edge cases. HIL escalates only when needed.
- T0 pre-filterRule-based deflection layer handles ~50% of traffic at $0 LLM cost.
- Tiered LLM routingT1 self-hosted OSS for 80% · T2 mid-cloud for 15% · T3 frontier for 5%.
- PII redaction pre-LLMAadhaar, PAN, mobile, account numbers stripped before any model call.
- CRM / ITSM connectorsFreshdesk, Zendesk, ServiceNow, HubSpot, Salesforce. Bidirectional.
- Immutable audit trailEvery external call, model invocation, human decision written to WORM store. DPDP-compliant.
02 · architecture
channels in. agents in the middle. systems out.
Inbound channels feed an intent + sentiment router. Routes hit the multi-agent core (Identifier → Support → Expert → HIL). Tools layer reaches your CRM, ITSM, FAQ knowledge base. Outbound delivery fans across SMS, push, email, voice callback, webhook.
whatsapp · voice · web · email · slack
↓
identifier (intent + sentiment)
↓
support → expert → hil
↓
crm · itsm · knowledge · webhooks
↓
identifier (intent + sentiment)
↓
support → expert → hil
↓
crm · itsm · knowledge · webhooks
03 · lighthouse
live in production
ready to evaluate
start with a diagnose.
Two to three weeks. Five to ten lakh. A written scorecard with topology recommendation, cost ranges, and remediation plan. No commitment to build.
request diagnose
DPDP-ready by design
AWS · Azure · GCP
blueprint · patent pending
India residency · on-prem option