Salesforce MVP Hall of Fame (Shivanath Devinarayanan) · Founded 2022
WhatsApp for customers, Slack for the company
Customers write on WhatsApp and your team answers from Slack, so the same question is retyped twice. One agent job runs in both, with the record in Salesforce.
Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio
The stack
How we would assemble it.
The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
Before and after
Typed twice, or once.
Today
With the agent
- The customer writes on WhatsApp
- The customer writes on WhatsApp
- Someone retypes it into Slack
- The team decides in Slack, record attached
- Someone else updates Salesforce
- Salesforce is updated once
Spec, shadow, gate
How the first agent goes live.
One named job. A shadow run before any write.
Week one
The job on one page: inputs, the write, the limit, who approves, and what it may never do.
Before go-live
The agent acts as the person it works for, with their access. Knowledge and permissions checked before it takes a job.
Shadow run
Shadow
The agent runs beside the person and writes nothing. You compare its calls with theirs.
Go-live
Writes go live behind a human approval. The gate loosens only where the shadow run earned it.
Every week
Every run is logged. On the Run plan we read the transcripts every week and fix what went wrong.
For example
One desk, for example.
Example
Service lead at a Dubai property manager
Today: Tenant requests on WhatsApp are forwarded to a Slack channel by hand.
After: Requests land in the channel with the tenant record attached, and the reply goes back on WhatsApp.
The job
What has to be true.
Channel seat
The brief
Send the situation.
Name the process. Name the object. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days.
