Skip to content

Follow-Up Intelligence

Not a reminder to follow up. The actual message, with its reasoning attached.

A nudge that says check in with this deal puts the work back on the rep. Macklore writes the specific follow-up the thread calls for, cites the activity that prompted it, and proposes when to send it. Then it waits for a person.

A real suggestion, start to finish

Every draft arrives with the evidence that produced it.

The reasoning is not decoration. It is what lets a rep decide in ten seconds whether to send, edit or dismiss.

The last thing the buyer said

Including any question in it that was never answered.

How long the silence has run

Measured against this deal's own rhythm, not a fixed cadence.

What was sent and what was opened

A proposal nobody opened leads to a different message than one read four times.

Who is on the thread

A single-threaded deal gets a suggestion aimed at widening it.

Macklore never sends on its own. The send button belongs to your rep, on every suggestion, with no exception and no setting to change it.

Suggested follow-up

Hexfield Interiors, illustrative

At risk, score 18Send today, before 16:00

Why now

  • Nine days since the last inbound reply, against a four day norm on this deal
  • The pricing annexe has not been opened since 12 March
  • Your question about the approval route was never answered
  • Only one contact has ever replied, and it is not the budget holder

Draft

Subject: Approval route for the Hexfield fit-out quote

Hi Meera,

Picking up the thread from the second of March. You had asked how the phased billing would work, and I set that out in the annexe rather than the main document, which is easy to miss.

One question so I can plan properly: does this need sign-off from finance before you can confirm, or does it sit with you? If it is finance, I am happy to send a one page version written for them.

I have copied Ravi in case he is the right person for that part.

Review and sendEdit draftDismiss with reason

What makes this different from a sequence

A sequence fires on day seven regardless of what happened. This message exists because a specific question went unanswered, a specific document went unopened, and a specific person has never replied. Remove those facts and the suggestion changes.

How timing is decided

Four rules, because when a follow-up lands matters as much as what it says.

Most missed deals are not missed for lack of a message. They are missed because the message came three weeks late or three days too early.

01

Against the deal's own rhythm

If a buyer normally replies in two days, a five day gap is late. If they normally take a week, five days is nothing. Timing is relative to the pattern on that specific record.

02

Before the gap becomes a habit

The suggestion lands while the thread is still warm enough to revive. Once a reply gap crosses roughly double the deal's norm, recovery rates fall sharply.

03

Around known commitments

If the buyer said they would come back after a board meeting on the eighteenth, the suggestion waits until the nineteenth rather than nagging into a known blackout.

04

Inside working hours of the recipient

Send windows are proposed for the buyer's working day, not the rep's. A follow-up delivered at 23:40 reads as automation.

The review queue is designed to stay short.

A suggestion engine that produces thirty drafts a day gets ignored by the end of week one. Macklore raises suggestions only where the activity pattern says the deal is drifting, and dismissals teach it where it was wrong.

  • One suggestion per deal at a time, never a stack of competing drafts
  • A dismissed suggestion does not reappear until the deal's activity changes
  • Suggestions pause while a reply is pending from the buyer
  • Nothing is raised on a deal the rep marked as deliberately parked

Questions

What reps want settled before they use the drafts.

No. Every suggestion sits in a review state. A rep reads it, edits it if they want, and presses send. There is no setting that turns this into an autonomous sender, by design.

Fully. The draft is a starting point, not a template to approve. Most reps change a line or two and keep the structure, because the structure is built from the actual thread.

Dismiss it with a reason. Those dismissals feed back into how aggressively suggestions are raised for that deal shape, so the queue gets quieter and more accurate over time.

Suggestions follow the tone of the existing thread rather than a generic sales voice. On Growth and Enterprise plans you can also set house rules, such as length limits and phrases to avoid.

Pipeline bulletin

Four follow-ups are waiting for review in this sample pipeline.

Stop writing the same recovery email from scratch while the reply gap widens.

Macklore writes the first version from the thread itself. Your rep decides whether it is right, changes what they want, and presses send.

  • Hexfield Interiors moved to at risk
  • Varun Steelworks flagged hot
  • 4 follow-ups queued for review