The CRM follow-up queue: a next action on every record, approved in one sitting

Most lost deals aren't lost to competitors. They're lost to silence: a quote nobody chased, a callback that slipped, an enquiry that sat over a long weekend. A follow-up queue fixes this by making the next step a required part of every record, then putting the due steps in front of you as ready-to-approve drafts.

This is the single most useful habit in an agent-native CRM. Here's how to design the queue, define stages so it stays honest, approve drafts quickly, and track opt-outs properly.

Rule one: every open record has one next action

A next action has four parts: what, who, when, and why. 'Follow up' isn't a next action. 'Evie drafts a chaser for quote Q-1042, Thu 6 Nov, because Priya said she'd confirm the lease date by then' is.

• One, not several. Multiple open tasks on one record means none of them is clearly next. Finish or replace.
• Dated. No date, no action. 'Sometime next month' becomes the 1st.
• Owned. A person or an agent. If it's an agent, a person still owns the approval.
• Closed records have none. Won, lost and opted-out records come off the queue entirely, apart from a handover or a long-term check-in you've deliberately set.

Agents make this rule cheap to keep, because they write the next action as part of logging each event. We cover which events write what in agents that write the CRM for you.

Deal stages that mean the same thing to everyone

A queue is only as good as the stages behind it. If 'active lead' means 'someone we spoke to once in March' to one person and 'someone who asked for a quote this week' to another, nobody trusts the numbers. Define each stage by an observable event and a time limit.

'Stale after' is the important column. A deal past its limit shows up in your review, not because it's lost, but because someone needs to decide what happens next.

A CRM follow-up process that builds your day

Each morning the agent builds the queue from the CRM and sends it to your channel. Sort it by what costs you most to miss, not by date alone:

1. New enquiries not yet answered.
2. Commitments you made with a date (we promised to send something).
3. Quotes due for a chase.
4. Verbal yeses waiting on paperwork.
5. Stale deals needing a decision.
6. Long-term check-ins.

Each item comes with a drafted message where one is needed, so the queue is a list of decisions, not a list of chores. In Cortex this arrives in Telegram, WhatsApp, Slack or Discord, and you can reply with a voice note to change a draft.

Approving drafted follow-ups in one sitting

Approval-first is the default in Fulcrum Cortex: agents draft emails and SMS and you approve before anything goes out. The trick is to approve in a batch, once or twice a day, rather than one message at a time all day.

An illustrative draft chaser:

Short, specific, references what she actually said, and offers an easy reply. If you find yourself rewriting most drafts, the problem is usually missing context in the notes, not the drafting. For deciding which messages should ever skip approval, see approval gates for autonomous agents. Our view: for customer-facing follow-ups in a small business, almost none.

Tracking opt-outs across every workflow

An opt-out has to stop messages everywhere, not just in the tool where it was received. If someone replies STOP to an SMS, your email follow-up must not go out the next morning either, if it's marketing.

The Spam Act rules are specific. The ACMA says every commercial message must include an unsubscribe option that honours a request within 5 working days, is free, and stays functional for at least 30 days after the message was sent; messages must also identify the sender and include contact details (ACMA: Avoid sending spam). That's general information, not legal advice, but it tells you how to build the queue:

• One consent field per contact, with date and method, that every agent and every channel checks before drafting.
• Opt-outs recorded immediately, whatever channel they arrive through: email reply, SMS reply, phone call, in person.
• Drafts blocked, not just flagged. If a contact has opted out of marketing, the agent shouldn't prepare a marketing message at all.
• Transactional messages kept separate. A reminder about an invoice they owe is different from a promotion. Be clear with yourself about which is which.

Lead scores only matter if they change the queue

Plenty of CRMs calculate a lead score that nobody uses. If a score doesn't change what happens next, delete it. A useful score does one of three things: moves a record up the daily queue, changes who handles it, or triggers a specific action such as a same-day call. For researched prospects, a simple 1-3 fit rating with a written reason, as described in AI prospect research, is usually enough.

A weekly pipeline review built around decisions

Don't read every deal aloud. Have the agent prepare a review with only the deals that need a decision:

• Deals past their 'stale after' limit: chase, change the approach, or close as lost.
• Deals above your value threshold: anything that needs your personal attention.
• Records missing a next action: there should be none; if there are, find out why.
• Lost reasons this week: patterns worth acting on, such as price, timing or a competitor.

That's typically a 15-minute meeting for a small team instead of an hour.

Won is the start of a handover, not the end

When a deal is won, the last next action is a handover note to whoever delivers the work. It should say what was sold, at what price, what was promised and by when, who the contacts are, and anything that could go wrong. Delivery reads that, not the email thread. It's also a good place to schedule a check-in a few weeks after delivery, which is where referrals and repeat work come from.

Worked example: following up after an event

Say 40 people registered for a webinar you ran. An illustrative queue: the agent tags attendees and no-shows from the registration list, checks consent on each, drafts a thank-you with the recording for attendees and a 'sorry we missed you' for no-shows, creates deals only for the four who asked a specific question about pricing, and sets next actions for those four. You approve two templates and four personal messages, not 40.

To see how next actions and drafted follow-ups sit on the shared record, look at Fulcrum CRM.