How to Set Up an Enquiry Triage Workflow That Sorts and Routes Leads

Enquiries arrive through a web form, email, a phone message, social media and a booking tool. They land in different places and wait for whoever notices. A triage workflow collects them in one place, sorts them and puts each one in front of the right person quickly. This guide explains the design in concepts that apply to Zapier, Make or n8n, and Zapier vs Make vs n8n helps you choose between them. It does not walk through screens, because those change and differ between tools. You finish with a design you can build yourself or hand to someone else.

Step 1: Decide what a good outcome looks like

Write the goal as a testable sentence. For example: "Every enquiry is recorded in one list, labelled by type and urgency, assigned to a person and acknowledged to the customer within ten minutes during business hours."

Without that sentence you will build something clever that does not help. Keep the first version small.

Step 2: List every entry point

Write down every route an enquiry can take into the business:

• Website contact form.
• Shared email inbox.
• Phone messages or voicemail transcripts.
• Facebook or Instagram messages.
• Booking or quoting tools.
• Referral emails from partners.

Pick the two or three that carry most of the volume. Automate those first. Trying to catch everything on day one leads to a fragile build. Most form and booking tools can pass an enquiry on through a webhook, and the glossary explains webhooks in plain terms.

Step 3: Choose one place for the records

Every enquiry should end up in a single list. This could be a CRM such as HubSpot, a shared spreadsheet or a project tool. The tool matters less than having one source of truth. Give each record the same fields:

Field	Example
Received	Date and time
Source	Web form, email, phone
Name and contact	As given
Message	Original text
Type	Quote, support, supplier, spam, other
Urgency	Urgent, normal, low
Owner	Person responsible
Status	New, replied, quoted, won, lost

If your team is not ready for a CRM, a spreadsheet works for a first version.

Step 4: Define the categories and the rules

Sorting is where a workflow earns its keep. Start with a short category list that matches how your team already thinks. Three to six types are plenty.

For each category, write the routing rule in plain words:

• Quote requests go to the estimator.
• Support questions from existing customers go to the account manager.
• Supplier and sales pitches go to a low-priority folder.
• Anything mentioning "urgent", "emergency" or "leak" goes to the on-call person immediately.
• Anything unclear goes to the fallback queue.

Where the input is structured, such as a dropdown on your form, rules do the whole job. Where the input is free text, such as an email, an AI model can read the message and suggest a type and urgency. Tools like Zapier, Make and n8n all have ways to call an AI model within a workflow. Treat its output as a suggestion that gets logged, and give a person the final say on urgent or high-value items. Our answer on whether AI can answer customer emails covers the limits.

Step 5: Add the acknowledgement

The first reply is the one customers judge you on. Plan an automatic acknowledgement that does three things:

1. Confirms you have the enquiry.
2. States honestly when a person will reply.
3. Asks for any missing information that will speed up the answer.

Write it in your normal voice, and keep it short. Do not imitate a human typing live. A clear, friendly automatic message works better than a fake personal one. For the quote stage, see automating quote follow-up.

Step 6: Notify the owner

When a record is created and assigned, tell the owner where they will see it, such as email, Slack or Microsoft Teams. Include the key details in the message so they can act without opening the list. Add a reminder if the status is still "New" after a set time.

Step 7: Build the fallback and the error path

Every workflow fails sometimes. A form changes, a connection expires or an unusual message confuses the sorting. Plan for it:

• A fallback queue for anything the rules cannot place, checked daily by a named person.
• An alert to you when a workflow run fails. Zapier, Make and n8n all offer failure notifications.
• A weekly look at the fallback queue and misrouted items to improve the rules.

Skipping this step is the most common reason triage workflows quietly drop leads.

Step 8: Test with real examples

Collect 20 to 30 real past enquiries, including messy ones, spam and odd cases. Run them through the design on paper or in test mode and check each result. Ask the people who handle enquiries whether the routing matches what they would have done.

Fix the rules, then run the examples again. Only then switch it on for live traffic. Start with one source, watch it for a week and add the others afterwards.

Step 9: Measure and adjust

Pick two or three measures from the start: time to first reply, number of enquiries with no owner, share that end up in the fallback queue. Our guide on measuring whether an AI change is working explains how to take a baseline before you switch on the workflow so you can see the change.

Where AI belongs and where it does not

Task	Rules	AI model	Person
Logging the enquiry	Yes
Sorting a dropdown choice	Yes
Reading a free-text email for type		Yes, with checks
Detecting urgency	Keywords	Optional	Confirms
Replying to a complaint			Yes
Pricing a custom job		Draft only	Yes

For help with the review side, see keeping a human in the loop on AI output.

Copyable design sheet

GOAL: ____________________________
ENTRY POINTS: ____ ____ ____
RECORD LOCATION: ____________
CATEGORIES: ____ ____ ____ ____
ROUTING RULES:
  If ____ then ____ (owner: ____)
URGENCY KEYWORDS: ____ ____ ____
ACKNOWLEDGEMENT TEXT: ____________
OWNER ALERT VIA: ____________
FALLBACK QUEUE OWNER: ____________
FAILURE ALERT TO: ____________
TEST SET: 20-30 real enquiries collected? Y/N
MEASURES: ____ ____ ____

What to do next

If you want the design built and tested without taking your team away from their work, workflow automation from 21Labs starts with a free discovery. We map your enquiry routes, tell you honestly what is worth automating and give you a price before any work starts. Use the form below and we reply within 24 hours. If you want to check the process first, read how to map a process before automating it.