Lorixen.
EN

Answer web enquiries in minutes: auto-acknowledge and route leads

Short answer: Send every web enquiry an instant, specific acknowledgment that says who will reply and by when, then route it by rules (service type, ZIP code, urgency) to one named person who gets a phone notification. Add a fallback path for anything the rules don't catch and an escalation if nobody responds within your target time. A form, a CRM or simple automation tool, and a shared inbox are enough to build it.

Most service businesses lose web leads in the gap between "form submitted" and "someone calls back." The enquiry lands in a general inbox, three people assume someone else has it, and by the afternoon the homeowner has booked a competitor. The fix is less about software than about deciding the rules. The example below walks through one setup end to end.

The worked example: a fictional HVAC company

This is a hypothetical business, used only to illustrate the build. "Northside Heating & Air" is a small HVAC contractor with an office manager, two service coordinators and a sales estimator who handles replacement quotes. Their website has one "Request service" form.

Step 1: Fix the form so routing is possible

Routing can only use what the form collects. Northside changes its form to ask:

  • What do you need? Repair / Maintenance / New system quote / Something else
  • Is your heating or cooling out right now? Yes / No
  • ZIP code
  • Name, phone, email, preferred contact method
  • Optional: a short description and a photo of the unit's label

The "out right now" question is the most valuable one on the form. It separates an emergency that needs a call within the hour from a tune-up that can wait until tomorrow.

Step 2: The instant acknowledgment

Within seconds, the customer gets an email and (if they chose text) an SMS. A generic "Thanks for contacting us" wastes the moment. Northside's message says what happens next:

Hi Maria, thanks, we've got your repair request for 60614. Since your heat is out, Dana from our service team will call you at 312-555-0142 within the hour during business hours. If it's after 6 p.m., our on-call line is 312-555-0199.

The details come from the form fields. The promise ("within the hour") must match what the team can actually do; a broken promise in the first message is worse than a modest one. Texts need the customer's consent to be contacted that way, so tie SMS to the preferred-contact choice.

Step 3: The routing rules

Northside writes its rules in plain English first:

If… Then assign to Notify by
Heating/cooling is out, during business hours Service coordinator on duty Push notification + SMS
Heating/cooling is out, after hours On-call technician SMS + phone call alert
Repair or maintenance, not urgent Service coordinators in rotation CRM task + email
New system quote Sales estimator CRM task + push notification
ZIP code outside the service area Office manager Email, with a polite "outside our area" reply template
Anything else / missing fields Office manager (fallback) Email

Then they build it. In a CRM such as HubSpot, a workflow triggered by the form submission can branch on the form answers and assign an owner. HubSpot's knowledge base describes a "Rotate record to owner" workflow action that distributes records equally between selected users or within a team (as of November 2026). It also lists requirements worth checking before you plan around it: it's available on Sales Hub or Service Hub Professional and Enterprise, the users being assigned need paid seats, and if no eligible user exists, no owner is assigned at all.

With a lighter stack (a website form plus Zapier or Make plus a spreadsheet or simple CRM), the same logic uses branching. Zapier's help center describes Paths as conditional logic: "if A happens in your trigger app, then do X; if B happens, do Y," with rule types including custom rules, always run and fallback (as of November 2026). That fallback branch is exactly what the last row of the table needs.

Step 4: Notifications people actually see

An email to a shared inbox is not a notification. Each assignee gets an alert on their phone through the CRM's mobile app or a text, containing the customer name, the need, the ZIP code, the urgency and a tap-to-call link. The lead record also gets a "first response due" time: one hour for urgent, end of next business day for quotes.

Check whether your tool actually notifies the person it assigns. Assignment and notification are often separate actions, so test it by submitting the form yourself and watching who gets pinged.

Step 5: Escalation when nobody responds

Rules fail when people are busy. Northside adds two timers:

  • Urgent lead not marked "contacted" after 20 minutes: alert the office manager and the second coordinator.
  • Quote lead untouched by the next morning: reassign to the office manager and add a note.

"Contacted" should mean a logged call or reply, not just opening the record. Most CRMs can check a property after a delay and branch on it.

Step 6: Round-the-clock coverage

After hours, the acknowledgment changes wording automatically (based on the submission time) and routes urgent jobs to the on-call phone. Non-urgent leads get an honest "we'll call you first thing tomorrow" message. An AI chat or phone assistant can also take details overnight, but it should hand off into the same routing rules rather than create a separate queue.

Measuring time to first response

You can't improve what you don't measure. Track:

  • Time to first response per lead: the gap between submission and the first logged call, email or text from a person.
  • Share answered within target, split by urgent and non-urgent.
  • Leads that hit the fallback path, which tell you where the form or rules have gaps.
  • Outcome by response speed, using your own data over a few months, rather than borrowed industry claims.

Review these monthly in a short meeting. If the fallback path catches a lot of "Something else" enquiries, add an option to the form.

Build checklist

  • [ ] Form asks for service, urgency and location
  • [ ] Acknowledgment names a person or team and a realistic time
  • [ ] After-hours version of the acknowledgment
  • [ ] Routing rules written down before building
  • [ ] Fallback owner for unmatched leads
  • [ ] Phone notification tested for each assignee
  • [ ] Escalation timer on urgent leads
  • [ ] "Contacted" status that requires a logged action
  • [ ] Monthly report on response times

FAQ

Should the auto-reply pretend to be a person?

No. Write it in a human voice, but don't imply someone typed it. Naming who will call and when is more reassuring than a fake personal note.

Is round-robin fair if some coordinators specialize?

Only for interchangeable work. Route specialist jobs (such as replacement quotes) by rule first, and use rotation only within a group of people who can all handle the job.

What if two forms on the site feed different inboxes?

Point every form at the same automation so the same rules apply. Separate inboxes are where leads disappear.

Do we need a CRM to do this?

Not at first. A form tool, an automation service and a shared spreadsheet with an owner column can work for a small team. A CRM becomes worthwhile when you need escalation timers and reporting without manual work.

Speed-to-lead rules are simple to write and fiddly to wire, and we can connect your form, inbox and phones so every enquiry lands with someone.

Sources

WhatsAppLet’s talk