To route form submissions on Qwenvo, switch on AI triage in the form's Settings and add a routing rule. A rule matches a priority (low, normal, high, urgent), a category, or both, and sends the submission to up to 5 email addresses or to a Slack incoming webhook. It is free and needs no Zapier.
Why route at all
One shared inbox for every form response means the urgent message sits behind ten newsletter signups. Routing sends each kind of submission to the person who handles it, so nobody has to forward anything.
Set up your first rule
- Open the form and click Settings.
- In the AI triage section, switch on Triage submissions with AI.
- Add a routing rule and choose the priorities or categories to match.
- Enter up to 5 email addresses, or paste a Slack incoming webhook URL.
- Submit a test response and check that it arrives where you expect.
A Slack incoming webhook is created in your Slack workspace's app settings. You paste its URL into the rule, so Qwenvo only posts to that one channel.
Rules that work in practice
- Urgent, any category goes to a Slack channel the whole on-call team watches.
- Category: sales lead goes to the sales inbox, even at normal priority.
- Category: bug report, priority high or urgent goes to engineering.
- Feedback with negative sentiment goes to whoever owns customer success.
- Everything else keeps arriving in your normal notification email.
Start with two rules. Add more only when you see a real pile-up.
What the recipient sees
Routed submissions carry the category, priority and short summary the AI gave them, so the person reading can decide in seconds whether to act. The suggested reply is there to copy and edit before sending.
When you need more than email and Slack
Qwenvo also connects to Google Sheets, Notion, Airtable, Discord, Linear, Zapier and Make, and sends webhooks. Use those when you want a row in a sheet, a task in Linear or a custom flow. See webhooks for that side.
Limits and care
- AI triage covers up to 10,000 submissions a month per account.
- AI can pick the wrong category. For anything where a miss is costly, keep a catch-all so nothing depends on the AI being right.
- A Slack webhook URL is a secret. Anyone who has it can post to that channel, so keep it out of public places.
Honest note: routing runs on the priority and category the AI assigns. If you need routing by an exact answer, such as department equals Billing, collect it with a Dropdown and branch in Zapier, Make or a webhook, where you control the field.
Example setups for three kinds of team
- A freelancer with one contact form: one rule sending sales leads to a personal inbox, and one for urgent messages to a Slack channel on a phone. Everything else lands in the normal notification email.
- A small support team: urgent and high priority bug reports go to the engineering channel, billing questions go to the finance address, and the shared inbox gets the rest. Pair this with the support request triage setup.
- An events organizer: negative-sentiment feedback after an event goes to the person running the debrief, while positive comments go nowhere special. You can forward the good ones into a testimonials folder later.
Check your rules after launch
Routing rules are easy to forget. After the first week, open Submissions and compare what the AI labelled with what you would have labelled. If urgent is firing too often, tighten the rule by adding a category. If something important slipped through, add a rule or widen one. Review again after a month, and whenever someone joins or leaves, so alerts do not go to a former teammate.
If you are choosing between building this in Zapier and using a routing rule, a rule is quicker for email and Slack. Zapier or Make is the better route when the destination is a tool Qwenvo does not send to directly.
Questions people ask
Can I send submissions to different emails by dropdown answer?
Not with routing rules, which work on triage results. Send the data to Zapier, Make or a webhook and branch there.
Do I still get normal notifications?
Yes. Email notifications to you work as usual, and you can also send confirmation emails to respondents.
What does it cost?
Nothing. Will this stay free? If paid plans are ever introduced, everything you already use stays available and you will be told well in advance. Today there is no plan to pick and no card on file.
Next step: copy the support ticket template, switch triage on, and add the two rules above. For the feature itself, read AI form triage.
Every feature, $0, no card.
Set up routing free