How to Decide Who Follows up with New Leads

When someone asks about buying, a shared inbox isn't the same thing as a clear owner. Decide who is responsible for the next response, and what happens if that person can't take it.

You can make that decision before adding another sales tool.

Give the Inquiry One Current Owner

Start with a simple distinction: an owner is the person responsible for moving the inquiry forward. Other people may help, but they should not independently contact the same person without checking the record.

In a one-person business, you may be the owner. In a small team, choose a named person or a rota with a visible current owner. "Sales will handle it" isn't enough if everyone believes someone else has replied.

Keep the owner, latest contact and next action in one place the team actually checks. If the owner changes, record that change rather than leaving two competing assignments.

Use Rules That Match the Inquiry

An existing customer's message may belong with the person already handling the account. A specialist service request may need someone who knows that service. A general new inquiry might go to the next available person.

Choose the few distinctions your team genuinely needs. Too many categories make it harder to tell where an unusual request belongs. Include a route for "not sure" rather than forcing every message into a category.

Don't assume every inbound message is a sales lead. Support requests, supplier messages and job inquiries need a different next step.

Decide What Happens When the Owner Is Away

Set a response expectation your team can meet and a backup route when someone is absent. The appropriate timing depends on your operating hours, the inquiry and what you've promised. A solo business that answers messages during working hours needs a different backup arrangement from a team that promises round-the-clock replies.

A backup should take over through the same record, with the previous conversation visible. Avoid making someone repeat their request because the first owner was unavailable.

Make reassignment explicit. A reminder to an absent person isn't the same as another person accepting responsibility.

Keep Acknowledgement and a Real Reply Separate

An automatic acknowledgement can confirm that a message arrived. Keep any price, availability or deadline promise tied to a current check.

The useful reply answers the person's actual question or explains the information needed to do so. Record that reply and the next step. If the person isn't a fit, close the loop rather than leaving the inquiry open forever.

Check the Rule with a Few Examples

Before switching on automated assignment, try a new prospect, an existing customer, an unclear request, a duplicate and an inquiry arriving while the usual owner is away. For each, ask who owns it now and who would notice if nothing happened.

If those answers are unclear, fix the ownership rule before automating it. Automation can apply a rule; it should not invent one your team has not agreed.

Write and Test Your First Ownership Rule

For a fictional two-person service business, try this draft: new inquiries go to the person on today's rota; existing customers go to their current account owner; uncertain messages go to the rota person for review. If that person is away, a named backup accepts the transfer in the shared record.

Choose your own response expectation based on operating hours and capacity. Then run the draft against five invented messages. Include a duplicate sent through two channels and a message from an existing customer asking about a new service.

For each one, write the current owner, the next action and what the backup sees. If two people can reasonably read the rule and choose different owners, clarify that branch. Once the rule works, you can decide whether manual assignment is enough or whether your existing system should apply it.

---