A roofing confirmation text should identify the business, the visit purpose, the appointment window and how the customer can correct or change the booking.
Confirm the appointment you actually booked
Use “inspection” or “assessment” when that is the booked service. Calling every visit a repair can create an expectation that the work will be finished immediately. Include the day, date, arrival window and a recognisable business name. Where the customer has several properties, include the relevant address or a suitable identifying detail. Send the message only after the appointment is confirmed in the working calendar. A beautifully written text cannot rescue a booking that was never saved or was assigned to the wrong person.
Template for an inspection
Example: “Hi [name], [business] has booked your roof inspection for [day, date], [arrival window], at [address]. This visit is to assess the reported issue. Please reply if the address or access details need correcting. To rearrange, contact [approved contact].” Replace every placeholder and verify that replies reach someone. If inspection fees apply, include the approved amount or a clear link to the agreed terms. Do not invent a fee or repeat an old price from a template. Keep the wording appropriate for your actual service.
Template when access needs confirmation
Example: “Your proposed roofing visit is [day, date, window]. We still need confirmation that [access contact] can let us in. Please contact [business contact] by [agreed deadline] so we can confirm the booking.” This is a provisional message, not a confirmed appointment. Keep the status visibly different in your records. Do not send both versions at the same time. If confirmation never arrives, follow your agreed release or callback process rather than leaving a technician expecting access that nobody arranged.
Template for a changed appointment
Example: “Update from [business]: your roof inspection has moved from [old date/window] to [new date/window], as agreed with [contact]. Please reply if this does not match your understanding.” A change message should supersede the earlier appointment rather than merely add another date. Update the calendar first and record who agreed to the change. When weather affects a visit, communicate the confirmed change or callback plan honestly. Do not promise a new slot until availability has been checked. Ask a colleague to read the message as if they had never seen the original.
Test timing, replies and safety wording
Run a test booking, a reschedule and a cancellation. Check the displayed date, customer number and business identity. Confirm that a customer reply or failed delivery has an owner. Delivery is different from proof that someone read a message; Twilio documents distinct messaging states. Avoid instructions to climb onto roofs or prepare unsafe access. Review the KEDO roofing workflow with your real appointment rules and ask which confirmation and reply handling are available in your configuration. Keep an approved template register showing the owner and last review date. When a booking rule changes, update the register and the live message together so an old draft cannot quietly reintroduce obsolete terms.
Sources and editorial notes
The workflow and examples are KEDO Labs editorial recommendations, not a promise of product functionality or professional advice. Sources checked October 8, 2026.
See the workflow
Hear the call. See the booking.
Watch KEDO handle a service enquiry, then review the current setup fee and monthly price before you pay.
Reading in Google?
Make KEDO a preferred source
Add KEDO Labs as a preferred source in Google and our guides are more likely to appear with a 'preferred' badge in Top Stories, and can carry a badge in AI Mode and AI Overviews.