Build a lead follow-up workflow your team can run

Give every active inquiry an owner and next action

A follow-up workflow is an operating rule that turns a sales event into an appropriate next step. It can create a task, prepare a message or carry out an approved action. The record must tell the team why that action is relevant.

At minimum, keep the inquiry status, owner, last meaningful interaction and next action visible. A generic “follow up” task is weaker than “confirm the installation date before preparing the quote.” The specific purpose helps both the person and the automation decide whether the task is still needed.

Use a practical workflow specification

The example is a design worksheet, not a universal cadence. Set timing around the customer’s decision and the team’s capacity. A same-day event request and a longer B2B proposal need different handling.

Write the workflow as a set of decisions

Start with a real inquiry type rather than a generic sequence. For a quote request, identify the information needed to prepare the quote, the person responsible for collecting it and the event that confirms it has been sent. Each step should make the next decision easier.

Then write the branches. A reply should pause an irrelevant reminder. A confirmed appointment should update the relevant record under the agreed stage and approval rules. A decline or opt-out should end the relevant outreach. An overdue task should become visible to someone who can act, not simply generate another notification to the same absent owner.

Run through these scenarios with the people who will use the workflow. Ask them to explain the next action from the record alone. If they need a separate chat to understand what happened, add the missing context before automating more steps. The quality of the handoff matters more than the number of messages the workflow can send.

A practical workflow specification

• Trigger and eligibility: what starts this workflow, and which records are excluded?
• Owner and due time: who acts and when is the action expected?
• Completion and stop rules: what evidence ends or changes the sequence?
• Exception handling: who resolves missing data, delivery failures or an overdue task?

How Figaro and Cyrano help without competing sequences

Figaro prepares the follow-up list and message in the supported inquiry workflow. The team approves the applicable contact and remains responsible for price, commitments and deal status. For a human call, Cyrano proposes the recap, learned facts and next action/date, which the person confirms.

The implementation must make those actions agree with the current quote and contact rules. Do not infer a universal automatic suppression engine merely because both agents can access customer context.

Read Figaro follow-up preparation.

Read Cyrano’s confirmation rules.

Make stopping as reliable as starting

An automation that starts correctly can still damage the experience if it continues after a reply. The workflow needs to know what changes eligibility. Replies in connected channels can trigger a stop; other conversations may require a manual update.

A booking should end incompatible booking invitations. A declined quote should not continue receiving “ready to move forward?” messages without a deliberate reason. An opt-out needs an appropriate suppression path. Review these transitions before increasing the number of automated steps.

Test the exceptions with the team

1. Run a suitable new inquiry through assignment and the first action.
2. Record a reply before the next scheduled step and verify that pending work changes.
3. Create a duplicate inquiry and check that it does not start duplicate communication.
4. Record a booking, a decline and a manual takeover.
5. Simulate a failed action and confirm who sees and resolves it.

Use controlled test records and the provider’s appropriate testing method. Do not create real sales inquiries just to prove that a button works. The acceptance evidence should cover the entire process the team intends to operate.

Review progress, not just sending activity

Count how many suitable inquiries received a meaningful response, how many next actions became overdue and what happened at later stages. Sent, delivered, replied, booked and attended are separate events.

If a workflow produces many messages and few useful conversations, revisit fit, context and timing. Growth Control’s implementation connects these records and responsibilities so the team can improve the process rather than manage a disconnected sequence tool.

Worked example: the callback replaces a generic reminder

A workflow may receive a delayed reply after a reminder has already been prepared. Before a customer-facing action proceeds, the implementation needs a defined check against the latest relevant opportunity state. An earlier draft can be grammatically correct and still be wrong for the conversation now taking place.

In a fictional Stretch Tent example, Figaro has prepared a quote nudge. A human call then establishes that the customer will provide a new site photo before the owner reviews a revised layout. Cyrano proposes that note and next action for confirmation. The approved operator update becomes the basis for the next contact; the old nudge must not proceed simply because it was drafted first.

These are acceptance requirements for the configured workflow. They are not a claim that every agent installation already has one shared automatic sequencing engine.

Choose the template for the actual quote state.

Keep the daily CRM view useful.

Use an exception queue that describes a decision

An exception should tell its owner what cannot safely proceed and what evidence is needed. “Error” or “follow up” gives little help. A useful entry might say that a quote reminder was paused because the event date changed, and the owner must review availability before a replacement quote is prepared.

• Reference the customer and the specific opportunity/quote.
• State the blocked action and why the current rule cannot decide it.
• Keep the source message or event reference available for review.
• Name the responsible person and the next expected decision.
• Record resolution and whether the previous draft or task remains valid.

Review exceptions alongside the ordinary daily follow-up list. If they remain unowned, automation has merely moved lost work into a different queue. Measure resolution and overdue actions instead of celebrating the number of reminders generated.

Questions and answers