Skip to main content
Four steps, in this order. Each depends on the one before, which is why an assistant that seems finished but stays silent is almost always missing one of them.
1

Set the languages

Admin panel → Settings → Languages.Choose the language flows will be written in, and any others you will translate into.
The source language cannot be changed once a flow has been published. This is the only step here that is hard to undo, which is why it comes first.
See Settings.
2

Create an assistant

Admin panel → Assistants → New Assistant.A name, a default language, active. Then Manage to open its console — everything after this happens there.See Assistants.
3

Connect a channel

Console → Channels → New Channel.Have the bot token ready: saving contacts the provider and registers the webhook, so a token that does not belong to a real bot will not save.Once it saves, messages sent to that bot reach the assistant — and, with nothing to answer them yet, produce nothing.See Channels.
4

Build and publish a flow

Console → Flows → New Flow, then Builder.Start small: one node that sends a message. Give the flow a trigger so something starts it, or set it as the assistant’s default flow in Assistant settings.Then publish it. A flow that is built and saved is still invisible — contacts only ever see published versions.See The flow builder and Publishing.

​
Checking it worked

Write to the bot from your own messaging account. If nothing comes back, work backwards through the four steps — the failure is almost always one of these: The console’s Assistant Dashboard shows live sessions and errors in the last 24 hours, which is the fastest place to see whether anything arrived at all.

​
What next