Use these six templates for confirmations, reminders, time changes, skipped visits, late arrivals and outstanding invoices. Replace the bracketed fields and connect each message to the correct appointment or payment event.
The following are original service-message drafts, not legal advice or vendor-specific merge-field syntax. Use your provider's supported consent, opt-out and sender-registration process. Do not paste the brackets into a live automation without replacing them with the correct fields.
1. Confirmed appointment
Hello [first name]. Your clean with [business] is confirmed for [date], with arrival between [window start] and [window end]. The booked service is [short scope]. For changes, use [monitored contact route].
Trigger: the business has actually confirmed the visit. Do not send: merely because a customer submitted an unapproved request. Replace or cancel: when that visit is moved or canceled.
This is not the right template for a company that has received only a quote request. Use “we received your request” and explain the next step instead of promising a slot.
2. Prior-day reminder
Hello [first name]. A reminder of your [business] clean on [date], with arrival between [window start] and [window end]. Please arrange the access agreed for your visit. For a change, contact [monitored route].
Trigger: the appointment remains active at the configured reminder time. Suppress: canceled visits, duplicate reminder ownership and inappropriate recipients. Keep actual property-access credentials in the controlled operational record, not a general notification.
Do not substitute an exact time for an arrival window merely because the software template has one time field.
3. A time change confirmed by the office
Hello [first name]. Your clean has moved from [old date/window] to [new date/window], as agreed. The service is [unchanged scope or approved change]. Please use [monitored route] if this does not match your understanding.
Trigger: the new appointment is committed in the operating schedule. Required system action: suppress the old reminder and create the new one if appropriate. Do not send: a definitive changed-time message while the business is still proposing alternatives.
A single changed appointment should not imply the whole recurring series has moved unless that is what was agreed.
4. One recurring visit skipped
Hello [first name]. Your clean on [skipped date] is canceled as agreed. Your next planned clean is [next confirmed date/window]. The remaining schedule is unchanged unless we have discussed otherwise.
Trigger: one occurrence has been skipped and the next date is verified. Do not add: a promise about refunds or charges unless it follows the actual service agreement. Suppress: service and arrival messages for the canceled occurrence.
A recurring date and a fixed-period payment agreement may produce different billing outcomes. The invoicing guide keeps that distinction explicit.
5. Running late
Hello [first name]. This is [business]. Today's arrival is now expected between [revised window start] and [revised window end]. We apologize for the change. Please use [monitored route] if access arrangements need to change.
Trigger: an authorized person has approved a revised, credible window. Avoid: repeatedly sending machine-generated precise arrival promises without a dependable operational basis.
The office should decide whether the customer needs a revised window, a call or another arrangement. A notification cannot itself resolve an inaccessible property.
6. Outstanding invoice reminder
Hello [first name]. Our records show invoice [reference] for [agreed service/date] has an outstanding balance of [amount]. You can review it at [approved invoice link]. Please contact [monitored route] if you have already paid or need a correction.
Trigger: the current ledger or approved operational source still shows the amount due. Suppress: a settled balance, a disputed amount awaiting review or an outdated invoice version. This draft is not a debt-collection or legal-compliance template.
Never ask the customer to send card details by replying to a message. Use the provider's supported payment route.
When to send, replace or cancel a message
| Event | Send or replace | Suppress |
|---|---|---|
| Request received, not approved | Request acknowledgment | Confirmed-appointment wording |
| Appointment confirmed | Confirmation; schedule reminder | Duplicate confirmation from another system |
| Appointment moved | New confirmation/reminder | Old date's reminder and arrival message |
| Single occurrence canceled | Appropriate cancellation message | That occurrence's service/payment reminder where inapplicable |
| Whole series ended | Agreed end-of-service message | Future visit reminders from the series |
| Invoice settled | Receipt if appropriate | Outstanding-balance reminder |
Download the notification event map and message drafts. These are ready-to-edit content, not a claim that any product is configured automatically by downloading them.
Check the plan’s message features and charges
BookingKoala documents SMS through a connected Twilio account. ZenMaid documents message-credit purchases. Housecall Pro describes reminder setup. Maidily distinguishes two-way messaging and its number requirement. These are different setup and budgeting models. BookingKoala SMS notifications overview ZenMaid: How much does it cost? Housecall Pro SMS job reminders Maidily pricing and plan matrix
Use the notification volume planner to estimate sends. Count customer and worker recipients separately, then apply the provider's billing-unit and message-segmentation rules. A draft below an assumed character limit can expand after customer names, URLs and dates are inserted.
The goal is fewer incorrect messages, not more automation. Keep one source of truth for the current visit, one owner for each trigger and a monitored route for the customer's reply.