Product / Customer follow-up

Follow up without
starting from scratch.

Bring the customer’s previous messages, open work, and next step into the follow-up. Configure when LBOS prepares a draft, when it can send, and when your team reviews.

Discuss follow-up

Channels, connections, and available actions are confirmed for your setup.

Illustrative estimate follow-up · Fictional customer
Nothing is sent.
Estimate follow-upAwaiting reply
AL
Alex LeeKitchen tap replacement · Example estimate
Last customer message

“Thanks for the estimate. I’ll take a look this week.”

Suggested follow-upDraft · not sent

Hi Alex, have you had a chance to look over the estimate for replacing your kitchen tap? Let us know if you have any questions before deciding.

Reason: the estimate is still awaiting a response.
Your team reviews this messageCheck the details and whether a follow-up is still needed.

From open work to the next conversation

The reason comes
with the message.

A useful follow-up starts with what has already happened. Agree the trigger and the checks that make it appropriate to contact the customer.

  1. 01

    Start with a specific reason.

    An estimate is unanswered or a document is missing. Keep that open item and the customer’s last response together.

  2. 02

    Prepare the relevant message.

    Use the details of the work to prepare a follow-up. Check whether the customer has already replied and whether the chosen channel is permitted.

  3. 03

    Make the next action clear.

    Apply the agreed review and send rules. Keep replies, delivery status, and any issue with the same customer record.

Set up around your relationships

Agree when to follow up.
And when to stop.

Before enabling a workflow, we define its timing, customer permissions, review steps, and exceptions with your team.

Timing
What starts a follow-up, how often it can repeat, and when it ends.
Customer permission
Which channels can be used and how preferences or opt-outs are respected.
Team involvement
Which messages need review and who handles replies or delivery issues.

Before we connect it

What this means
for your business.

Which follow-ups can we start with?

Bring a recurring situation: an unanswered estimate, missing information, an appointment reminder, or an unpaid invoice. We confirm the records, channel, timing, and available actions needed for that workflow.

Can messages go out automatically?

That depends on the agreed workflow. We define which messages may be sent automatically, which need a person’s review, and when follow-up should stop. The illustration here ends at an unsent draft.

Can we use our existing email or messaging tools?

We assess the channels you use, connection access, and any custom integration work. Customer permissions, opt-outs, and channel requirements are included in the scope before messages are enabled.

What happens if a customer replies or delivery fails?

We define how replies stop or change the next follow-up, who handles exceptions, and how failed or unconfirmed delivery is checked. An unconfirmed send should not be treated as delivered or retried without checking.

Build on your LBOS setup

Which conversations need a follow-up?

Bring the recurring situation and the tools you use. We’ll agree the connections, message rules, and a practical first scope.

Discuss follow-upExplore the full platform