Skip to content
Youssef Alouani
← Projects

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

Sowtek omnichannel chatChannel connectors for WhatsApp, email, X, Instagram and Facebook normalise incoming messages into one conversation model. The conversation service stores them, routes them to queues and agents, and pushes updates to agent workspaces over WebSockets. Outgoing messages go back through the same connectors.ChannelsWhatsAppEmailX · Instagram · FacebookIntegrationChannel connectorswebhooks · normalisationEvent busidempotent ingestionCoreConversation serviceone model for all channelsRoutingqueues · agents · botsAgentsInboxWebSocketsCustomer profilecross-channel history
Sowtek omnichannel inbox: conversation list across WhatsApp, email, X and Instagram, a WhatsApp conversation with an agent, and the customer profile with interaction history
The omnichannel inbox: one conversation model for every channel (product marketing image, demo data).
Sowtek social media monitoring dashboard with Facebook and Instagram timelines and comment feeds side by side
Social channels integrated into the same platform (product marketing image, demo data).

Key decisions

  1. One conversation model. Every connector translates its channel into the same messages and conversations, so routing, history and analytics are written once.
  2. Connectors are isolated. A channel API outage or change only touches its connector, not the inbox.
  3. 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