Coachful
CoachfulHelp

Client booking confirmations: customizing the email

By Coachful3 min readUpdated Oct 19, 2026

Find the correct booking email controls, check sending-domain requirements and distinguish call, event and intake confirmations.

In the full workspace, open Manage → Branding (this opens Customize), then Communications. In Simple Mode start at Settings → Branding → Communications. The three panes are Sending, Notification emails and Notification settings. Compact screens shorten the last two to Emails and Notifications.

Choose the email that matches the booking

  • Scheduled or proposed calls: in Notification emails, use the template selector and choose Call Confirmed under Calls & Scheduling. This notification is used when a call is booked directly or a proposed time is accepted.
  • Public session-type and intake bookings: these use a separate branded booking-confirmation email. Editing Call Confirmed does not change that email. Open the relevant session type from Sessions, or the discovery-call configuration from Sell → Discovery calls. The session description is included in the booking email. The Confirmation message field is shown after booking; keep essential emailed preparation information in the description.
  • Events: Event booking confirmation is a separate template available for the supported GDPR event-booking flow. It is not a generic template for every group or intake call.

Before editing a notification template

A verified email sending domain is required for Call Confirmed and most notification templates. Set this up in Communications → Sending. Email subscription confirmation, Call Cancelled and Intake Cancelled have separate exceptions. If Call Confirmed is missing or editing is blocked, check the sending-domain status and your workspace permissions.

Edit, preview and save

  1. Choose the relevant available template.
  2. Edit the subject and email content, and choose a shared signature if needed.
  3. Preserve the date, time, timezone and meeting/action links. These are important details to keep when editing.
  4. Use Preview email and, if needed, Send test email. A test sends a real email to your account.
  5. Save your changes. Previously sent emails do not change.

Sender name and reply-to address are shared controls in Sending. The notification editor does not have separate top-body, bottom-body or preheader fields. Its selector is organized by notification, not three 1:1, Group and Intake tabs.

Use supported variables

Select variables offered for that notification. For scheduling emails these include {{firstName}}, {{eventTitle}}, {{eventDate}}, {{eventTime}}, {{meetingLink}}, {{ctaLabel}} and {{ctaUrl}}. For example: Your call is confirmed, {{firstName}}: {{eventDate}}.

Use the exact spelling. Dotted client/session variables and pipe-style fallback expressions are not supported. The first-name token has a built-in fallback of “there”. Not every notification supplies every variable.

Reminders are separate

Use Communications → Notification settings for delivery switches and reminder timing. The first workspace reminder can be 24 or 48 hours before, and the second 1 or 3 hours before. A session's Reminders controls its channel overrides separately.

If the steps do not match what you see, contact support@coachful.co with the workspace URL, the action you tried and a screenshot without passwords or codes. Do not post client information in a public channel.

Frequently asked questions

Where are booking email templates?
Manage → Branding (Customize) → Communications → Notification emails. In Simple Mode start at Settings. Compact screens label the pane Emails.
Why is Call Confirmed missing?
Most notification templates require a verified sending domain. Check Communications → Sending and your workspace permissions.
Does Call Confirmed change public intake booking emails?
No. Public session-type/intake bookings use a separate branded email builder. The booking description is included in that email.
Can I use {{client.first_name}}?
Use {{firstName}} instead. Use only exact variables supported by the selected template; dotted tokens and pipe fallback expressions are unsupported.
Was this article helpful?