Axelerated Solutions · shipped
Sowtek: omnichannel chat and channel integrations
Backend services for Sowtek's omnichannel inbox, with WhatsApp, email, X, Instagram and Facebook integrated behind one conversation model.
Problem
Contact-centre agents in Saudi Arabia answer customers on WhatsApp, email, X, Instagram and Facebook, often the same customer on several of them. Each channel has its own API, webhooks, message formats, rate limits and delivery rules. Agents need one inbox and one customer history, in real time.
Constraints
- Every channel is different: webhooks, polling, media types, message windows and rate limits all vary.
- Real time: messages appear for the right agent immediately, with typing and delivery states.
- No lost messages: channel webhooks retry and duplicate, so ingestion must be idempotent.
- Routing: conversations go to the right queue and agent, and can be handed to bots and workflows.
Architecture


Key decisions
- One conversation model. Every connector translates its channel into the same messages and conversations, so routing, history and analytics are written once.
- Connectors are isolated. A channel API outage or change only touches its connector, not the inbox.
- Idempotent ingestion. Webhook retries and duplicates are expected, so every message is keyed by its channel ID.
Results
Numbers to come.
Stack and links
Deep dives
- Sowtek FlowBuilder: an in-house low-code engine: The engine behind FlowBuilder, Sowtek's low-code builder for call, chat and SMS workflows, from IVRs to database lookups and agent routing.