A follow-up should not live in your head.

The quote is not the last step

You send a proposal, get back to the day and intend to follow up later. The next request arrives. The conversation slips down the inbox. Nothing dramatic happens; the next step simply never gets its own place.

The first improvement does not have to be automatic sending. It can be making the follow-up visible: who it concerns, what was sent, when someone should review it and what needs to happen next.

That creates a process you can hand over more reliably than “remind me to chase my quotes”.

Keep the conversation attached to the task

A useful follow-up depends on context. Was the customer waiting for revised pricing? Did they ask you to contact them next month? Have they already replied through another channel?

Before preparing a message, the workflow needs access to the relevant record and a way to recognise missing information. A timer on its own is not enough.

• The customer and intended recipient.
• The correct proposal or quote reference.
• The most recent relevant conversation.
• Any promised date or next step.
• The person responsible for checking the draft.

If those details are scattered, start by agreeing which record is authoritative. The assistant should not decide between conflicting customer details without an agreed rule or a clarification.

Prepare the draft before approving the action

A good review step shows the actual message. “Approve follow-up” is less useful than seeing the recipient, subject, body and proposal it relates to.

The reviewer can then decide whether the wording is appropriate and whether now is the right time. They might approve it, reject it or ask for a revision. That decision should be attached to the specific draft.

If the recipient or wording changes afterwards, the earlier approval should not silently carry over. The person reviewing needs to know what will actually leave the business.

Record the result, not just the intention

There is a difference between a follow-up being prepared, approved and sent. Each tells you something different about the work.

A draft can be ready while waiting for review. An approved message can still fail to send. A sent message may need a later next step. If every stage simply appears as “done”, useful information disappears.

Keep the outcome visible alongside the task. The person opening the workspace should be able to see whether anything still needs attention without opening several systems and guessing what happened.

Begin with a defined example

For a first pilot, choose one type of proposal and one agreed follow-up process. Define the information needed, who approves the message and what happens when the customer replies before the planned action.

Use the first examples to refine the rules. You may find that the most helpful part is preparing accurate drafts, not sending more messages. That is a useful result in its own right.

AskMace’s interactive demo illustrates this pattern with fictional data. A live pilot would need the relevant connection, review rules and execution process configured for your business.