Skip to content

Automated follow-up that keeps the next step clear.

A new inquiry, an upcoming appointment and a completed service need different messages. Ember builds the selected follow-up around those moments so customers know what happens next and your team knows what still needs attention.

Jamie ParkerWillow Salon · SMS example

Your appointment is tomorrow at 2 PM. Reply here if the team needs to know about a change.

I need a different time.

Avery · Front deskReminder paused. Team review needed.
Fictional message journey · No messages sentExplore the message journey

EVENT → MESSAGE → NEXT STEP

Start with a reason to send the message.

Useful follow-up has a clear trigger and purpose. We decide which event starts the process, what the customer needs to know and when a person should respond. A reminder, a missed-call response and a reactivation campaign are different scopes.

Example message journeys · Willow Salon is fictional · No messages are sent.

See what changes with the event.

ConversationsWillow Salon · Customer follow-up
Demo
JP
Jamie ParkerWillow Salon · SMS example

Monday · fictional conversation

Jamie Parker

Hi, I wanted to ask about a haircut this week.

10:04 AM
Willow Salon

Thanks for getting in touch. The team will review your request and help with the next step.

10:05 AM
Sending is disabled in this preview
JP
Jamie ParkerWillow Salon · SMS example

Monday · fictional conversation

Willow Salon

Your appointment is tomorrow at 2 PM. Reply here if the team needs to know about a change.

9:00 AM
Jamie Parker

I need a different time.

9:12 AM
Willow Salon · Team

Thanks, Jamie. The front desk will help you find another time.

9:14 AM
Sending is disabled in this preview
JP
Jamie ParkerWillow Salon · SMS example

Monday · fictional conversation

Willow Salon

Could you send the details the team requested?

11:00 AM
Jamie Parker

I’ve sent over those details. Thank you!

11:08 AM
Willow Salon · Team

Thanks, Jamie. We have the information we need for review.

11:10 AM
Sending is disabled in this preview

Appointment approaching example shown.

Timing matters, and so does stopping.

The setup needs clear timing, recipient eligibility and stop rules. A reply, cancellation, completed next step or changed preference may mean the original sequence should pause or end.

We define those paths rather than letting every customer receive the same messages indefinitely.

Agree the entry and the exit.

What starts it?
Use an agreed event, such as a new inquiry or an approaching appointment, to start the selected message. Confirm which record shows that event has actually happened.
Who is eligible?
Define which customers belong in this journey and which should be excluded. Use the agreed communication preferences and the information needed to identify the intended recipient.
When does it happen?
Set the timing around the reason for contact: a reminder before an appointment needs a different schedule from an inquiry check-in. Agree any repeat interval and limit.
What changes the sequence?
Define how a reply, cancellation, completed outcome or changed preference affects the sequence. The original message should not keep repeating after its purpose has ended.
See what changes when the next step is completed Click hereClose preview

The original reason to follow up has ended.

Stop the original sequence when the agreed outcome is recorded. The team defines whether any different communication is appropriate after that point.

This is an illustrative stop rule, with no delivery receipt, customer record or message sent.

A reply needs someone to own it.

Automation can handle a repeatable message; your team still owns the conversation that follows. We agree where replies appear, who reviews them and how exceptions are handled.

  1. Customer event

    Start from an event the customer recognizes, such as an inquiry they made or an appointment already arranged. The message should have a useful, understandable purpose.

  2. Selected message

    Use the channel, timing and wording approved for that journey. Tell the customer what the message relates to and what response or next step is useful.

  3. Reply or stop condition

    Check the agreed conditions before a later message. A reply, completed request or changed appointment may require a different path rather than another copy of the original reminder.

  4. Responsible person

    Give replies and exceptions a named owner. That person needs enough context to answer the question, review the request or correct the underlying appointment information.

Everyday follow-up and a new campaign have different needs.

Appointment reminders and post-service communication can be part of the agreed operating setup. Database reactivation or a new promotional campaign needs its own audience, offer, permissions, cadence and response plan. When an estimate has been sent but the customer has not decided, an agreed check-in can invite a question or decision. Your team keeps control of pricing and scope.

Additional campaigns and ongoing management are scoped separately. A contact list alone does not establish that everyone should receive a new message. A reply, acceptance, rejection or changed status should update or stop the sequence and give the conversation a named owner. The selected setup needs the records and sending rules to support that path.

Agree the message and the responsibilities around it.

Start with one inquiry or appointment journey. The selected scope should be understandable before a message is sent.

Event and purpose
Identify the recorded event and the message it calls for. Bring the current customer journey so we can distinguish a useful reminder from unrelated outreach.
Selected channel and timing
Select the communication channel, message wording and timing for this journey. Agree any repeats and the point after which another reminder would no longer be useful.
Recipient eligibility
Define the intended recipients, communication preferences and exclusions. Identify what information determines eligibility before the selected sequence starts.
Reply and exception owner
Name who receives replies and how they find the relevant inquiry or appointment. Agree a fallback when the usual person cannot deal with the response.
Pause and stop conditions
Name the outcomes and record changes that pause or end the original sequence. Check how a reply or changed appointment affects messages that would otherwise follow.
Review responsibility
Assign responsibility for checking message accuracy and reviewing later changes to the process. Additional campaigns and ongoing management need their own agreed scope.

Define the selected scope before it runs.

Explore all FAQs
Which messages can be automated?

The selected scope can cover repeatable communication around inquiries, appointments or completed services. The actual channels, messages and timing are agreed for your business.

What happens when a customer replies?

The setup names who receives the reply and whether it should pause or end the original sequence. A person may need to answer a question, review an estimate or arrange a different appointment. The reply path and the rules for changing later messages are agreed before that follow-up runs.

Can this include past customers?

An agreed rebooking reminder after a completed service is different from a campaign to restart conversations with past customers. Each needs a clear purpose, eligible audience and timing. A reply, opt-out or new booking should change or stop the relevant reminders. A reactivation campaign also needs its own offer and response plan and is scoped separately.

Map the follow-up your customers actually need.

Bring one inquiry or appointment journey. We will look at useful messages and the responsibilities around them.

Book a demo