A lead follow-up process your team can actually use

A usable lead follow-up process gives every active enquiry an owner, a current stage, a specific next action and a due date.

Start there before choosing reminders or writing a sequence of messages. If the record says only 'follow up', the next person still has to work out what the customer needs and why they are being contacted.

Use the process below as a starting point to adapt with your team. It is a suggested way of working, rather than a claim that every step runs automatically in Atlas.

Assign one person to keep each lead's next step current. Other people may help with a quotation, a technical answer or an appointment, but the lead owner checks that the promised response happens.

Define a handover rule for leave, reassignment and enquiries received outside working hours. Name the person responsible for checking unassigned enquiries. Avoid assuming that everyone watching a shared inbox knows who should act.

Agree a response target that your team is staffed to meet and review it against actual work. A website form, a booked consultation and an existing customer asking for support need different handling. Keep their queues distinguishable.

Define the evidence required to move a lead into each stage. 'Interested' means little if one salesperson uses it after a missed call and another uses it after a detailed buying discussion.

For a hypothetical services business, the stages below describe observable progress. They are an example to adapt, not a universal pipeline. A business that needs a site visit or a technical assessment should include that work in its own definitions.

A useful next action names the task, the reason and the date. In a hypothetical example, 'send the revised maintenance proposal on Thursday, including the weekend coverage option requested' gives a colleague enough context to help. 'Call again' leaves the important detail elsewhere.

Record the outcome after contact and decide the next step while the conversation is fresh. If a quotation depends on a technical answer, record who owes that answer and when it needs to reach the lead owner.

Keep notes relevant to the business conversation. Distinguish what the customer said from a salesperson's assumption about their intent. An expected purchase date and a confirmed purchase date deserve different wording.

Ask when and how the customer wants to hear back. Use an agreed callback date where there is one. A customer waiting for an internal meeting has a different next step from someone asking for a missing price or document.

For an unanswered enquiry, agree a bounded follow-up approach with your team, including when to stop and how to record the result. There is no contact count prescribed by this workflow. Do not keep sending the same message because the record remains open.

If someone asks you to stop contacting them, record that request and take it out of the active follow-up queue. Keep that decision visible during reassignment. Closing an enquiry with a clear reason is more useful than leaving it active indefinitely.

Hold a short team review of work that needs attention. Begin with overdue promises and unassigned enquiries, then look at the day's scheduled actions. Read the context before deciding that an old record needs another call.

Use the review to remove obstacles. If several proposals are waiting on the same technical answer, speak to the person responsible for that answer. Moving all the follow-up dates forward hides the dependency without resolving it.

Run a small set of representative enquiries through the proposed workflow with the people who will use it. Include a missed callback, an absent owner, a proposal needing revision and a request to stop contact. Ask the team to explain what happens next in each case.

Atlas provides configurable sales stages, assignment, follow-ups and a shared view of progress. Discuss which fields, views and responsibilities fit your process with the builders. Confirm any extra automation or integration separately rather than assuming that a written workflow makes it available.

After the trial, keep the rules that help someone decide what to do. Rewrite ambiguous stage definitions and remove fields nobody uses to make a decision. The process is ready to expand when the next action stays clear even during a handover.