Automation

Agree Who Picks Up Each New Website Enquiry Before It Arrives

When nobody knows whose job the first reply is, website enquiries sit unanswered. Here is how a small team can agree simple ownership rules in advance.

✍️ Sham Kamboj 📅 October 30, 2026 ⏱ 6 min read
Abstract emerald and teal enquiry form card linked to three round markers, the middle one ticked

A new enquiry arrives through the website form. Three people see it. Each assumes one of the others will reply, and by the next morning nobody has. The person who asked has moved on to another supplier, and the team only notices when someone scrolls back through the inbox.

This is rarely a question of effort. It is a question of ownership. When a small team has not agreed whose job the first reply is, every enquiry becomes everyone's job, which in practice means nobody's. The fix is a short set of rules, agreed in advance and written down, so each new enquiry has a named owner from the moment it lands.

Why new enquiries sit unanswered

Most small businesses share one enquiries inbox or one phone, and several people can see what comes in. That feels safe, because more eyes should mean faster replies. In practice it creates three common gaps:

  • Shared visibility without a named owner. Everyone can see the enquiry, so each person waits for someone else to act.
  • Unclear hand-offs. One person replies once, then goes on leave, and the conversation has no obvious next owner.
  • Quiet hours. Enquiries that arrive in the evening or at the weekend wait for whoever opens the inbox first, which may be nobody in particular.

None of these needs new software to spot. Look back over last month's enquiries and ask, for each one, who replied first and how they knew it was theirs. If the answer is often "whoever saw it", the rules are worth writing.

Decide what ownership actually means

Before choosing a rule, agree what the owner is responsible for. A useful definition for a small team is simple: the owner sends the first reply, keeps the conversation moving until it reaches a clear next step, and hands it over properly if they cannot carry on.

Write that down in one or two sentences. It sounds obvious, but it settles arguments later. It also separates ownership from seniority. A junior team member can own the first reply on a new enquiry while a manager steps in for pricing or a site visit, as long as the hand-over is clear.

If you already use pipeline stages, link ownership to them. Our piece on writing entry and exit rules for every pipeline stage explains how to agree when an enquiry moves forward. Ownership rules answer the question that comes just before: who moves it.

Choose one simple ownership rule

There is no single right way to share out new enquiries. What matters is that the rule is easy to apply without discussion. Small teams usually pick one of these:

  • A daily rota. One named person owns every new enquiry that arrives on their day. It is the easiest rule to explain and the easiest to check.
  • By product or service. If your team has clear specialists, each one owns enquiries about their area. This works when the form asks what the person is interested in.
  • By source. One person owns enquiries from a particular campaign, partner or page. If you already tag every enquiry with its source, or carry campaign details in UTM hidden fields, the label is there to read.
  • By area or language. Useful when different team members cover different cities or reply more comfortably in Hindi, Punjabi or English.

Pick one rule to start. Mixing two or three rules at once usually brings back the confusion you are trying to remove. You can refine it once the team has used it for a few weeks.

Cover leave, weekends and quiet hours

Every ownership rule needs a back-up. Agree in advance what happens when the owner is away, busy with a customer or off for the day. A simple approach is to name a second person on the rota for each day, who takes over any enquiry the owner has not picked up by an agreed point in the day.

Decide too how you treat enquiries that arrive outside working hours. Some teams give them to the next day's owner. Others give them to whoever is on the weekend rota. Either works, provided everyone knows which one you use. Put the rota somewhere the whole team can see it, such as a shared calendar or a pinned note, rather than in one person's head.

Set a first-reply habit the team can keep

Ownership only helps if the owner acts. Agree a realistic internal target for the first reply during working hours, one the team can meet on a busy day as well as a quiet one. Then agree what a good first reply contains: a thank-you, an answer to the question asked, and one clear next step, such as a call time or the details needed for a quote.

A short written template helps new team members and keeps replies consistent. Review a handful of first replies each month together. The aim is not to check up on anyone, but to keep the habit visible and adjust the rule where it is not working.

The rule also depends on enquiries landing in one place. If form enquiries are forwarded to several personal inboxes, the owner may never see theirs. Our guide to sending form enquiries by webhook explains how a website form can hand each enquiry to a single intake point instead.

Where Flo fits

In Flo, a workflow runs each time a new website-form lead arrives, so every enquiry starts in the same place with a contact, a pipeline opportunity and a note.

Who picks up each enquiry, how you share them out and what the first reply says remain decisions for your team. A single starting place for every enquiry simply makes it clearer where those decisions are applied and checked.

A short checklist for this week

  1. Look back at last month's website enquiries and note who sent each first reply and how they knew it was theirs.
  2. Write a one or two sentence definition of what the owner of a new enquiry is responsible for.
  3. Choose one ownership rule: daily rota, product, source, or area and language.
  4. Name a back-up for each day and agree how out-of-hours enquiries are handled.
  5. Agree an internal first-reply target and a short first-reply template.
  6. Put the rota where the whole team can see it, and review it together after a few weeks.

If you'd like a walkthrough of Flo, book a short conversation.

Running a business on WhatsApp? FLO automates the follow-up.

Book a free demo →