Build and validate WhatsApp templates with header, body and buttons, personalize them with record variables, then deliver on WhatsApp, Email and Slack — all fired by a workflow. Replies land back in your conversation inbox.
Every message your business sends is just another step in a process. Processo gives you a proper template designer for WhatsApp, native Email and Slack channels, and one wiring point — the workflow — so the right message goes out the moment a record changes.
Compose header, body and buttons with a live preview, drop in variables, and validate against WhatsApp’s rules before you submit for approval.
Send transactional and broadcast email through Microsoft or Gmail, and post to Slack channels — the same personalized content, different channels.
Trigger on create, edit, status change or a schedule. Conditions decide who gets messaged, and variables pull live values straight from the record.
A WhatsApp template is assembled from typed components. The designer guides each one, enforces the limits, and previews exactly what the customer will see — so submissions get approved the first time.
Text, or a media header (image, video, document). Personalize text headers with a variable.
Rich body text with numbered variables and an optional footer line — character counts validated as you type.
Call-to-action buttons (visit a URL, call a number) and quick-reply buttons that bring the reply back into your inbox.
Tag the template as Utility, Marketing or Authentication, and manage versions per language.
Text or media · 60 char limit
Text + variables · 1024 char limit
Plain text · 60 char limit
URL · Call · Quick reply
Each placeholder is bound to a field on the record.
People · Textbox field
Object reference
Date field
Numbered placeholders bind to any field — a name, an order reference, an ETA, a currency amount. At send time the workflow resolves them from the live record, so every customer gets the right details.
Map each placeholder to an entity field — textbox, number, currency, date or an object reference across related records.
The designer flags missing variables, over-length text, broken button URLs and unmapped placeholders before you can submit.
Provide sample values to render the exact card reviewers and customers will see — header, body, buttons and all.
A workflow action chooses the channel. Notify the customer on WhatsApp, email a receipt through Microsoft or Gmail, and ping the fulfillment team in Slack — all from the same status change, with the same record data.
order-shipped template to customer
receipt via Microsoft or Gmail
#fulfillment channel ping
Approved templates sent to a customer’s number, with quick-reply and CTA buttons that route replies into your inbox.
Transactional and broadcast email through Microsoft or Gmail, or send from a connected Gmail account using personalized content.
Post internal alerts to a channel — new high-value order, SLA breach, approval needed — to keep the team in the loop.
Messages don’t vanish after sending. Track delivery, and when a customer taps a button or replies, the thread opens in your two-way conversation inbox.
channels from one workflow
delivery & read receipts
shared inbox for replies
lines of code to wire it up
See whether each message was sent, delivered and read, so you know your customer got the update.
Quick-reply taps and free-text answers open a thread in the conversation inbox — text, image, audio, document and contact bubbles.
WhatsApp, Microsoft, Gmail and Slack keys live in the secrets manager — never hard-coded into a template or workflow.
Messaging plugs straight into the rest of Processo — the inbox replies land in, the workflows that fire it, the connectors it rides on, and the agents that can send on their own.
The two-way inbox where every reply to your messages lands.
Explore →The triggers and conditions that decide when each message goes out.
Explore →WhatsApp, Microsoft, Gmail and Slack connectors, with keys in the secrets manager.
Explore →Agents that use messaging as a tool to reply and follow up on their own.
Explore →