Skip to content

Sort every contact form message with AI before anyone reads it

Add an Ask AI step that sorts, summarizes and flags urgent messages, then route each submission to the team that should answer.

2 min read

On this page

One contact form on a website ends up doing five jobs. Sales questions, support problems, invoices, job applications and the occasional partnership pitch all arrive in the same inbox, and someone has to read each one just to decide who should read it properly. An Ask AI step can make that first decision for you, on every submission, in the second after it arrives.

Add an Ask AI step

In the form's flow, add Ask AI after the trigger and pick what it should do with the text:

  • Summarize: two or three sentences, so nobody has to read a wall of text in Slack.
  • Sort into a category: picks exactly one of the categories you list, such as Sales, Support, Billing or Other.
  • Detect the mood: positive, neutral or negative, plus urgent when someone needs help fast.
  • Pull out details: an order number, a company name, anything you describe.
  • Translate, Draft a reply, or Your own instructions for anything else.

Each step saves its answer under a key, such as ai_category or ai_summary, that later steps can use like any field.

Route on the AI's answer

Add a Route by answer step and point it at ai_category. Give each category its own path and connect each path to where that kind of message belongs: Sales to the sales channel, Support to the help desk inbox, Billing to whoever handles invoices. Route by answer reads the visitor's answers first and step values after, so the same step works whether the category came from a dropdown on the form or from the AI.

Flag what is urgent

Run Detect the mood as a second Ask AI step, then add an If / else that checks whether ai_sentiment contains urgent. Connect the yes path to a post in an urgent channel, and the angry customer whose site is down gets seen in minutes instead of after lunch.

Put the summary where people look

Step values work in messages too. A Slack post that leads with the summary lets the team decide at a glance:

{{ai_category}} from {{name | someone}}: {{ai_summary}}
Reply to {{email}}

When the AI does not answer

A failed AI step never stops the flow. Its value stays empty and the step is skipped, so the submission still moves on: a Route by answer step sends it down the path for anything else, and it still reaches a person. Build that last path to a shared inbox and nothing ever gets lost.

Safe by design

A reply to the sender cuts AI values after 80 characters, so nobody can make the AI write a long message to a stranger through your form. Use Draft a reply in emails to your own team, who read the draft and send the real answer themselves.

Try it with a test submission

Test submissions from the form's Build tab run the flow step by step without delivering anything. Ask AI steps use a stand-in answer in tests, so you can check the routes and messages before turning the flow on, then watch the first real submissions in the inbox to see the AI's real answers.

The AI guide covers every task and how to write your own instructions, and the flows guide covers routing.

Keep reading

More from the blog