Skip to main content
Assistants & Messaging

The handover is where most greeting flows lose the person

Acknowledge the first message at once. When someone sends a first message and receives no reply, they conclude that no one is there, and that conclusion is hard to change later in the conversation.

The next failure is the greeting. It gathers a description of the problem, routes the person to a team, and the team then starts with 'how can I help'. The person has to type everything again. Instead of reducing steps, the automation has added one.

The point of the handover is to pass on the context: what was said, what has been understood, and what still is not clear.

The other part is knowing when not to route. If a greeting flow insists on categorizing an unusual request, it routes it incorrectly. When classification is uncertain, hand it to a person.

How the ActionFlow runs on the canvas

For first contact, acknowledgment must be as quick as possible, which is why the response is sent before a full reason is given. When a Webhook trigger receives the message, it immediately sends the acknowledgment through a Slack, Telegram, or WhatsApp node.

The Text Classifier node identifies the intent. The Generate Object node returns what the person is asking for, what remains unclear, and a confidence level for the intent.

The If node checks the confidence level. If something is uncertain, it goes immediately to the human queue with the message included, not to the category with the highest score.

When the intents are confident, the Switch node sends the message to the relevant team, including a summary of what has been said and what is still unknown.

A Google Sheets node stores the intent-to-team mapping. A second node logs every routing with its confidence.

When a documented self-service solution is available, the Notion node provides the article and presents it together with the greeting, while still keeping an ordinary option for contacting a person. That is what distinguishes offering help from blocking access to it.

Nodes this ActionFlow uses

  • Webhook (Trigger): receives the first message.
  • Telegram (Communication): sends the acknowledgment before any reasoning runs. WhatsApp and Slack fit the same slot.
  • Text Classifier (AI Custom): assigns an intent cheaply.
  • Generate Object (AI Core): returns the ask, what is unclear, and a confidence value.
  • If (Control): sends uncertain cases to a person rather than a best-guess category.
  • Switch (Control): routes confident intents to the owning team with the context attached.
  • Notion (Integration): supplies a self-serve article where one exists, offered rather than imposed.

Frequently asked questions

Start building AI workflows

Create a free account, open a template or a blank canvas, and run your first ActionFlow.

Newsletter

Get product updates

New nodes, agents, and product notes. We send mail only when we have something worth opening.

Unsubscribe at any time.