Samarpit Santoki

CommAgent

One API for email, SMS, RCS, and voice, used across Decklar’s products.

Where
At Decklar
Status
In production
My part
Designed and built it, from proof of concept to production.
150k+
conversations a month
100+
customer environments

As of July 2026.

Decklar’s products used to reach people through separate channel integrations. Every new feature that needed to message someone meant more channel-specific code.

I built CommAgent to put those channels behind one API: the architecture, the provider integrations, and delivery tracking. Other products and the workflow platform send through it, including the agents that run customer workflows.

Email, SMS, RCS, and voice are in production. WhatsApp is tested but not rolled out yet, and Microsoft Teams is on the roadmap.

Running it

Most of the work is making several outside providers behave like one system. Each has its own API, limits, and ways of failing. Webhooks arrive late, twice, or out of order. A retry must not send the same message twice. Delivery status has to be pieced together from whatever each provider reports.

Each customer environment’s data and configuration has to stay separate. And when something goes wrong, someone needs to find out what happened to one specific message.