Channels · WhatsApp
Executen Sales can run WhatsApp: inbound, templates, consent. The same agent, the same knowledge, a channel people actually answer.
In a lot of markets the email is a museum. WhatsApp is the doorbell. We built for the doorbell — and we will not skip Meta’s rules to look faster.
Webhooks, text, templates. Real code, real constraints.
Opt-out is a path, not a footnote in the footer.
Knowledge and playbook follow the shopper from widget to WhatsApp.
The inbox does not care which door they used.
Campaigns stay blocked until the number is connected and the template is approved. The UI will not throw confetti for a message that never left.
Shoppers reply. The agent answers from knowledge. Custom work and complaints escalate. That is sales, not a drip.
Widget on the site. WhatsApp in the pocket. Growth Command Center still reads what they did on the shop. The story should match.
Details
When Meta keys exist. 501 when they do not — on purpose.
We keep the door closed if they asked us to.
When the template allows it.
Tied to the workspace, not a vanity CSV.
Voice is rehearsal until live calling is actually configured.
On the map. Not sold as live until they are live.
Not a first-class Executen channel. We will not pretend.
Templates, windows, STOP — treated as product, not legal theatre.
Yes. We walk you through Cloud API. We do not invent a number for you.
Outside an open window, approved templates only. That is Meta. We respect it.
WhatsApp lives on the Sales desk. The Command Center is the shop’s brain. They share a brand.
On the schema. Not a channel we will headline until it behaves like WhatsApp does.
Tell us a little about your shop. We’ll write back, and we’ll take it from there.
Keep reading
If the leak is tracking, wait. If the region is the whole theme, stop. If the sentence would be weird in WhatsApp too, do not put it on the hero.
Tighten the adjectives. Kill the slogan you would never print. Confirm. Then the specialists may draft.
Page, cart, and order events you choose to send. KVKK and GDPR. SOC here is operations with Oriana — not a SOC 2 badge.
Channels
One snippet. Your shop starts talking to the Growth Command Center
Learn moreA desk on the storefront that answers when your team has gone home
Learn moreExperiences, editor, experiments — the page becomes the campaign
Learn moreInbox, CRM, automations, campaigns — the team behind the agent
Learn more
