Messaging channels
Run the same flows over WhatsApp, SMS, email and Slack — and start conversations yourself from the API.
Flows are not only for calls. The same logic can hold a conversation in writing, on the channels your customers already use.
Channels
| Channel | Connected through |
|---|---|
| Twilio or the Meta WhatsApp Cloud API | |
| SMS | An SMS-enabled number, such as a Twilio number |
| Your own mail server over SMTP | |
| Slack | A connected Slack workspace |
| Website chat | The website widget |
A flow can be built for calls only, chats only, or both — steps that make sense only on a call, such as transferring or recording, are available only where they apply.
Starting a conversation
Inbound messages start a conversation on the flow assigned to that channel. To start
one yourself — a WhatsApp follow-up after a missed call, for example — use
POST /outbound/chats. It takes the same flow-selection options as outbound calls: see
Outbound calls.
Injecting messages
A message can be pushed into a chat that is already running — to hand the assistant new information mid-conversation. See Live injections.
Note
WhatsApp's own rules apply on top of Kilevel's: business-initiated conversations outside the customer-service window generally require an approved template.