How to Invite Past Customers to Book Their Next Visit

Start with the next useful visit.

You finish a customer's appointment, thank them and move on. Weeks later, they may be ready to return, but nobody has invited them. A useful invitation names the service, offers a clear next step and reaches someone who actually wants to hear from you.

Start with one small group of suitable past customers and one email. The free return-visit message pack gives you three invitation alternatives, one optional reminder and two replies. The steps below show how to select the audience, prepare a real message and schedule one send in HighLevel, a system for managing customer records and communication.

This is an original documented walkthrough with a fictional salon example. No customer account, inbox or live integration was tested, and no bookings, savings or customer results are claimed.

1. Decide who would find the invitation useful.

Pick one service and a reason to invite someone back. A salon might review customers who previously agreed an approximate return interval. A cleaning business might invite previous one-off customers to ask about another clean. A plumbing repair should not be treated as a recurring appointment unless another visit genuinely makes sense.

Write down the service, the timing rule and the next action. For the fictional Rosewood Salon, the example is: “Past haircut customers around six weeks after their last completed visit, with permission for these emails, who have no next appointment.” Six weeks is an illustrative business rule, not a universal service recommendation.

Keep this separate from reminders for an appointment already booked. If that is your task, use the existing appointment reminder guide. An outstanding quote belongs in the quote-review process. Here, the customer has completed a service and may choose to return.

2. Make a small, permissioned shortlist.

Read the actual service and contact records. Leave out anyone already booked, already invited through another process, opted out, missing suitable permission or awaiting resolution of a service issue. Being in your address book is not, by itself, permission to receive a return-visit promotion. Check the rules and permissions that apply to your customers and channel.

In the fictional example, receptionist Omar reviews twelve customer records. Four already have appointments, two lack recorded marketing permission, one has opted out and one needs a service concern resolved. Four remain for final review. These are invented planning numbers, not campaign results.

Use a private invitation record with the customer record, last service, permission evidence, booking check, invitation status and reply owner. Statuses such as Ready, Scheduled, Sent, Replied, Booked and Closed help the team avoid selecting the same person twice. This is your operating record; the article does not claim HighLevel creates it automatically.

HighLevel's Do Not Disturb settings can apply to individual channels. Check email restrictions and applicable preference choices. Leave suppression in place; do not clear it to make a recipient count larger.

3. Prepare the sender, reply owner and costs.

You need access to the correct business workspace, its contacts and email-sending controls. Ask the account administrator to confirm those permissions and the approved sending service. Use a recognisable sender and a mailbox the team actually monitors. For an LC Email sending domain, the administrator can review Settings → Email Services → Dedicated Domain and IP and the official domain setup instructions. Have the administrator resolve an unverified sender before release.

The subscription and email usage are separate costs. HighLevel's LC Email documentation, checked November 10, 2026, lists USD0.675 per 1,000 emails, with separate verification charges and billable incoming/forwarded activity. Agency rebilling or another provider can affect your actual bill. Check the account's balance and current sending allowance; a new sending setup can have lower limits. Use the monthly cost estimator for broader planning, then verify current charges in the account.

Nadia, Rosewood's owner, approves the message and audience. Omar watches for replies each staffed day; Leena covers when he is away. Their message gives the actual staffed hours. An invitation should not create a promise of a reply while nobody is available.

4. Choose one invitation and test the complete email.

Use message 2 in the message pack for the salon example. It asks whether the customer wants another haircut and links to the actual booking page. It contains no invented discount, reserved appointment or claim that the customer urgently needs the service. Omar replaces the salon, receptionist, hours, address and link once for this small haircut audience. The greeting is simply “Hello,” so no name field is needed.

The three invitation messages are alternatives. Sending all three to the same person would make no sense. The cleaning version asks for a reply because the business needs to check scope and price before confirming a visit.

Keep a working unsubscribe option in every promotional email. For LC Email, check Sub-Account Settings → Business Profile → General and keep Include Unsubscribe Link enabled. The official footer instructions explain this control. The business address in the template must be real. Check the received message, including its footer, instead of assuming the editor preview proves it.

Use an inbox and sample contact you control. Open the booking link and confirm the business, service and available times. Reply to the test and confirm that the named staff member receives it. Check an unsubscribe on a separate test contact and ensure that contact is excluded from the real audience. Never use a customer's address for these tests.

5. Schedule one email after the owner approves it.

The following labels follow HighLevel's current bulk-email instructions. Account labels may differ when Contacts has been renamed.

1. Open Contacts → Smart Lists; select only the reviewed contacts.
2. Choose Send Email. Compare the selected, filtered-out and eligible recipient counts.
3. Set From Name, From Email and Subject. Use Quick Compose for the chosen wording.
4. Use Test Email ID → Send Test Mail; inspect the received message.
5. Open Review Campaign. After approval, choose Schedule the Send, verify the displayed date, time and timezone, then submit with Send Email.
6. Find the job under Contacts → Bulk Actions. Use Show Stats to inspect its outcome.

Record the exact approved audience, message, job reference and sending time. A recipient-count difference needs an explanation before approval. Automatic filtering helps with sending restrictions; it does not establish that a customer is due another visit or that you have the right permission.

This recipe schedules one reviewed job. It does not promise that later Smart List changes update an existing bulk send. Keep the lead time short and review any changed booking or contact choice before the batch runs. If you need continuous, automatically updated eligibility, that is a separate setup to design and test.

6. Handle replies before considering a reminder.

After sending, Omar checks the invitation record against real replies and bookings. “Thursday might work” needs a staff reply; it is not a confirmed appointment. He checks available options and uses message 5. Once the customer responds, that person leaves the reminder shortlist even if an appointment has not yet been agreed.

If the customer says “not now,” Omar uses message 6 and closes this invitation. If they ask to stop marketing, he honours that wider choice and records the applicable suppression. Do not reduce a clear opt-out to a temporary “not now” note. A complaint goes to Nadia and pauses further promotional contact while it is handled.

There is no reminder scheduled by default. If Nadia wants one optional reminder, she approves a new shortlist after Omar checks for replies, bookings, opt-outs, delivery failures and other invitations again. Message 4 is for that separate decision. An unopened-email report alone is not a reason to keep chasing someone.

The inbox ownership resource can help agree cover. Keep a promise in a message small enough for the actual team to meet.

7. Check failures and know how to stop.

Write down the outcome of the specific sending job. If the result is uncertain, hold any retry and inspect which recipients were processed. Check an individual contact's history when needed. Do not resubmit the whole audience because a screen timed out. The failure-recovery log supports that check.

For a pending job, inspect the controls offered on its Contacts → Bulk Actions entry; pause/cancel availability depends on type and status. Verify the resulting state. An already processed email cannot be recalled. If you cannot confirm a hold, ask the account administrator or support to resolve the pending send before making another attempt. Mark the invitation paused in your operating record and stop preparing follow-up batches.

Review delivered messages, real replies and confirmed bookings separately. A link click is not a booking, and a booking is not a completed paid visit. After the first small batch, decide whether the invitation was relevant, whether the team could handle replies and what should change. Keep any future repeat routine limited to a fresh, permissioned selection with a clear owner.

Common questions before you send.

Can I use my entire old customer list?

Review who should receive this specific invitation. Use the actual service timing, permission, contact choices, booking and duplicate checks. A saved address alone is not the selection rule.

Does this automatically stop when someone books?

This one-time bulk-email recipe does not implement a booking-aware stop system. Staff check before the job and again before any optional reminder. A continuously running process needs additional design and observed tests.

Do I need to buy software to use the messages?

The pack is ungated. You can adapt it for an existing approved business email service with the appropriate sender, permission and unsubscribe handling. The article's scheduling steps apply specifically to HighLevel.