Architecture Overview¶
Kewbot follows a modular SaaS architecture centered on message routing, agent operations, and campaign automation.
Logical components¶
- Channel layer: WhatsApp Business API connectivity.
- Routing layer: Inbound routes, ITR destinations, invalid-input handling.
- Agent layer: Inbox, case ownership, transfer/close actions.
- Outbound layer: Templates and campaign execution.
- Operational layer: Realtime metrics and supervision views.
High-level flow¶
- Message enters through WhatsApp integration.
- Inbound route decides initial destination.
- Automation (ITR/announcements/conditions) may continue routing.
- Conversation lands with a group/agent when human handling is required.
- Outbound templates/campaigns can re-engage customers.
Data entities (functional)¶
- Contacts (phonebook + attributes)
- Conversations
- Messages
- Templates
- Campaigns
- Users and groups
- Tags and conditions
Design principles¶
- Keep routing deterministic.
- Separate automation from human queue handling.
- Use templates for compliant outbound initiation.
Screenshot coming soon.