{"id":123,"date":"2026-11-03T08:56:33","date_gmt":"2026-11-03T08:56:33","guid":{"rendered":"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/reminders-workflows\/"},"modified":"2026-11-03T08:56:33","modified_gmt":"2026-11-03T08:56:33","slug":"reminders-workflows","status":"publish","type":"page","link":"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/reminders-workflows\/","title":{"rendered":"Reminders &amp; Workflows"},"content":{"rendered":"\n<!--\n  ============================================================================\n  PAGE: Reminders & Workflows\n  SLUG: reminders-workflows\n  URL:  https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/reminders-workflows\n  ============================================================================\n-->\n<style>\n.kb-page{\n  --coral:#EE6055; --mint:#3DE8B7; --ink:#1A1A1A; --paper:#FAFAF7; --pen:#5F5E5A;\n  --yellow:#F8E170; --blue:#365eff; --line:#ececec;\n  font-family:-apple-system,BlinkMacSystemFont,\"Segoe UI\",Roboto,Helvetica,Arial,sans-serif;\n  color:var(--ink); line-height:1.62; max-width:820px; margin:0 auto; padding:0 20px 72px; box-sizing:border-box;\n}\n.kb-page *{box-sizing:border-box;}\n.kb-page a{color:var(--blue); text-decoration:none;}\n.kb-page a:hover{text-decoration:underline;}\n.kb-page .kb-crumb{font-size:13px; color:var(--pen); padding:26px 0 0; display:flex; gap:8px; flex-wrap:wrap; align-items:center;}\n.kb-page .kb-crumb a{color:var(--pen);}\n.kb-page .kb-crumb a:hover{color:var(--coral);}\n.kb-page .kb-crumb span{opacity:.5;}\n.kb-page .kb-head{padding:18px 0 6px;}\n.kb-page .kb-eyebrow{display:inline-block; font-size:12px; font-weight:700; letter-spacing:.1em; text-transform:uppercase;\n  color:var(--coral); background:rgba(238,96,85,.1); padding:5px 12px; border-radius:999px; margin-bottom:14px;}\n.kb-page h1{font-size:clamp(26px,4vw,36px); line-height:1.15; margin:0 0 12px; font-weight:800; letter-spacing:-.02em;}\n.kb-page .kb-lead{font-size:17px; color:var(--pen); margin:0 0 8px;}\n.kb-page .kb-acc{margin-top:26px; border-top:1px solid var(--line);}\n.kb-page .kb-item{border-bottom:1px solid var(--line);}\n.kb-page .kb-q{width:100%; text-align:left; background:none; border:0; cursor:pointer; font:inherit; color:var(--ink);\n  display:flex; gap:14px; align-items:flex-start; padding:20px 4px; font-size:17px; font-weight:650;}\n.kb-page .kb-q:hover{color:var(--coral);}\n.kb-page .kb-q .kb-qi{flex:none; width:22px; height:22px; margin-top:1px; transition:transform .2s; color:var(--coral);}\n.kb-page .kb-item.open .kb-q .kb-qi{transform:rotate(45deg);}\n.kb-page .kb-q .kb-qt{flex:1;}\n.kb-page .kb-a{max-height:0; overflow:hidden; transition:max-height .3s ease;}\n.kb-page .kb-a-inner{padding:0 4px 22px 36px; font-size:15.5px; color:#33322f;}\n.kb-page .kb-a-inner p{margin:0 0 13px;}\n.kb-page .kb-a-inner ul,.kb-page .kb-a-inner ol{margin:0 0 13px; padding-left:20px;}\n.kb-page .kb-a-inner li{margin:0 0 7px;}\n.kb-page .kb-a-inner strong{color:var(--ink);}\n.kb-page .kb-a-inner h3{font-size:16px; font-weight:700; margin:20px 0 10px; color:var(--ink);}\n.kb-page .kb-a-inner code{background:var(--paper); padding:2px 6px; border-radius:4px; font-size:14px; font-family:\"SF Mono\",\"Menlo\",Consolas,monospace;}\n.kb-page .kb-a-inner blockquote{margin:0 0 13px; padding:12px 16px; background:var(--paper); border-left:3px solid var(--line); border-radius:0 8px 8px 0; color:var(--pen);}\n.kb-page .kb-a-inner .kb-tip{background:var(--paper); border-left:3px solid var(--mint); border-radius:8px; padding:12px 16px; margin:0 0 13px; font-size:14.5px;}\n.kb-page .kb-a-inner .kb-note{background:#fff8e6; border-left:3px solid var(--yellow); border-radius:8px; padding:12px 16px; margin:0 0 13px; font-size:14.5px;}\n.kb-page .kb-related{margin-top:40px; background:var(--paper); border:1px solid var(--line); border-radius:16px; padding:22px 24px;}\n.kb-page .kb-related h2{font-size:15px; text-transform:uppercase; letter-spacing:.08em; color:var(--pen); margin:0 0 14px;}\n.kb-page .kb-related ul{list-style:none; margin:0; padding:0; display:grid; gap:10px;}\n.kb-page .kb-related a{display:flex; gap:8px; align-items:center; font-weight:600; font-size:15px;}\n.kb-page .kb-cta{margin-top:34px; background:var(--ink); color:#fff; border-radius:20px; padding:32px 28px; text-align:center;}\n.kb-page .kb-cta h3{margin:0 0 8px; font-size:21px; font-weight:800;}\n.kb-page .kb-cta p{margin:0 0 20px; color:#cfcfcf; font-size:15px;}\n.kb-page .kb-cta-btns{display:flex; gap:12px; justify-content:center; flex-wrap:wrap;}\n.kb-page .kb-btn{display:inline-flex; align-items:center; gap:8px; padding:13px 24px; border-radius:999px; font-weight:700; font-size:14px;}\n.kb-page .kb-btn svg{width:18px;height:18px;}\n.kb-page .kb-btn-coral{background:var(--coral); color:#fff;}\n.kb-page .kb-btn-coral:hover{background:#e2483b; text-decoration:none;}\n.kb-page .kb-btn-ghost{background:transparent; color:#fff; border:1.5px solid rgba(255,255,255,.3);}\n.kb-page .kb-btn-ghost:hover{border-color:#fff; text-decoration:none;}\n.kb-page .kb-back{display:inline-flex; align-items:center; gap:7px; margin-top:30px; font-weight:600; font-size:14px; color:var(--pen);}\n.kb-page .kb-back:hover{color:var(--coral);}\n.kb-page .kb-a-inner .kb-table-wrap{overflow-x:auto; margin:0 0 15px;}\n.kb-page .kb-a-inner .kb-table{width:100%; border-collapse:collapse; font-size:14px; border:1px solid var(--line);}\n.kb-page .kb-a-inner .kb-table th{background:var(--paper); font-weight:700; text-align:left; padding:10px 12px; border-bottom:1px solid var(--line);}\n.kb-page .kb-a-inner .kb-table td{padding:9px 12px; border-bottom:1px solid var(--line); vertical-align:top;}\n.kb-page .kb-a-inner .kb-table tr:last-child td{border-bottom:none;}\n.kb-page .kb-a-inner .kb-warn{background:#fff2f0; border-left:3px solid var(--coral); border-radius:8px; padding:12px 16px; margin:0 0 13px; font-size:14.5px;}\n\n.kb-page .kb-fig{margin:14px 0 18px;}\n.kb-page .kb-fig img{display:block; width:100%; height:auto; border:1px solid var(--line); border-radius:12px; box-shadow:0 6px 24px rgba(0,0,0,.08);}\n.kb-page .kb-fig figcaption{font-size:13px; color:var(--pen); margin-top:8px; text-align:center;}\n.kb-page .kb-demo{margin:22px 0 18px;}\n.kb-page .kb-demo-tag{display:inline-block; background:var(--coral); color:#fff; font-weight:700; font-size:12px; letter-spacing:.06em; text-transform:uppercase; padding:4px 10px; border-radius:999px; margin-bottom:8px;}\n<\/style>\n<section class=\"kb-page\" id=\"reminders-workflows\">\n<nav aria-label=\"Breadcrumb\" class=\"kb-crumb\">\n<a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/\">Help Center<\/a><span>\/<\/span>\n    Reminders &amp; Workflows\n  <\/nav>\n<header class=\"kb-head\">\n<span class=\"kb-eyebrow\">Automation<\/span>\n<h1>Reminders &amp; Workflows<\/h1>\n<p class=\"kb-lead\">Automate the emails that go out before and after each meeting: confirmations, reminders, follow-ups.<\/p>\n<\/header>\n<div class=\"kb-acc\">\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">What Are Reminder Workflows And Why Are They Important?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>A reminder workflow is an automation attached to your bookings: when something happens (a booking is made, a time approaches, a meeting ends), it sends an email or calls a webhook. Reminders cut no-shows; follow-ups turn meetings into next steps.<\/p>\n<h3>1. What A Workflow Is Made Of<\/h3>\n<ul><li><strong>A trigger.<\/strong> Before the event, after the event, when an event is booked, cancelled, or rescheduled, or when you mark what happened after a meeting (met, no-show, I missed it, or decided to reschedule).<\/li><li><strong>Timing.<\/strong> How long before or after (minutes, hours, or days) for the before\/after triggers. The others fire immediately.<\/li><li><strong>Actions.<\/strong> One or more of: email the invitee, email yourself, email another address, or call a webhook.<\/li><li><strong>Scope.<\/strong> All event types, or specific ones.<\/li><li><strong>An on\/off toggle.<\/strong><\/li><\/ul>\n<h3>2. The Default Workflows<\/h3>\n<p>Every new account starts with six workflows, all enabled: a 24-hour reminder, a 1-hour reminder, and four post-meeting follow-ups, one for each outcome (met, no-show, I missed it, decided to reschedule). Booking confirmations, cancellation and reschedule notices, and the post-meeting &#8220;How did it go?&#8221; check-in are sent by bookme itself, not by a workflow; the templates gallery also offers optional confirmation, host-notification, cancellation, reschedule, and webhook workflows if you want an extra, custom-worded message.<\/p>\n<h3>3. Why Workflows Matter<\/h3>\n<ul><li><strong>Lower no-shows.<\/strong> A 24-hour and a 1-hour reminder are the difference between a 20 percent and a 5 percent no-show rate for most hosts.<\/li><li><strong>Faster follow-up.<\/strong> Follow-ups sent within minutes of a meeting get replies; follow-ups sent two days later do not.<\/li><li><strong>Less manual work.<\/strong> No more remembering to email people; the system does it.<\/li><li><strong>Cleaner CRM data.<\/strong> A webhook to your CRM sends bookings straight into your pipeline.<\/li><\/ul>\n<div class=\"kb-tip\"><strong>Tip:<\/strong> If you are new to bookme, start with the default workflows. Add custom ones only when you have a specific need the defaults do not cover.<\/div>\n<h3>4. Where They Live<\/h3>\n<p>Click <strong>Reminder Workflows<\/strong> in the sidebar. Each workflow is a card with its trigger, timing, actions, scope, and toggle.<\/p>\n<h3>5. Merge Variables<\/h3>\n<p>Workflow emails support merge variables that pull from the booking record. The most useful are:<\/p>\n<ul><li><code>{{invitee_name}}<\/code>, full name of the invitee.<\/li><li><code>{{host_name}}<\/code>, your display name.<\/li><li><code>{{event_name}}<\/code>, <a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/event-types\">event type<\/a> title.<\/li><li><code>{{meeting_time}}<\/code>, meeting time in the recipient&#8217;s zone.<\/li><li><code>{{meeting_link}}<\/code>, direct join URL.<\/li><li><code>{{booking_link}}<\/code>, link to book again.<\/li><li><code>{{host_meeting_notes}}<\/code>, your notes from the Met-with-notes flow.<\/li><\/ul>\n<p>Plus host contact variables (<code>{{host_phone}}<\/code>, <code>{{host_whatsapp}}<\/code>, <code>{{host_linkedin}}<\/code>, etc.) for sign-offs.<\/p>\n<h3>6. When To Turn Off A Workflow<\/h3>\n<p>Workflows can be turned off without deletion. Useful when:<\/p>\n<ul><li>You are testing a new template and want to pause the old one.<\/li><li>An event type does not need reminders (e.g. internal team checks).<\/li><li>You are temporarily on vacation and do not want post-meeting emails.<\/li><\/ul><!--dmfig--><figure class=\"kb-fig\"><img decoding=\"async\" src=\"https:\/\/bookme.brandid.app\/blog\/wp-content\/uploads\/2026\/11\/bookme-kb-bm-workflows.jpg\" alt=\"Email Workflows with the default post-meeting follow-ups.\" loading=\"lazy\" width=\"1511\" height=\"812\"><figcaption>Email Workflows with the default post-meeting follow-ups.<\/figcaption><\/figure><!--\/dmfig--><!--dmfig--><figure class=\"kb-fig\"><img decoding=\"async\" src=\"https:\/\/bookme.brandid.app\/blog\/wp-content\/uploads\/2026\/11\/bookme-kb-bm-new-workflow.jpg\" alt=\"New Email Workflow: choose when it runs and the timing.\" loading=\"lazy\" width=\"1511\" height=\"812\"><figcaption>New Email Workflow: choose when it runs and the timing.<\/figcaption><\/figure><!--\/dmfig--><\/div><\/div>\n<\/div>\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">How To Create A Reminder Workflow For Your Event Type?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>Create a workflow from a template in one click, or build one from scratch with your own trigger, timing, actions, and scope.<\/p>\n<h3>1. From A Template<\/h3>\n<p>On <strong>Reminder Workflows<\/strong>, open the templates gallery and pick one: 24-hour reminder, 1-hour reminder, the four post-meeting follow-ups, booking confirmation, new booking notification (host), cancellation notification, reschedule notification, or webhook on new booking. The workflow is created, enabled, and applied to all event types; edit it afterwards.<\/p>\n<h3>2. From Scratch<\/h3>\n<p>Click <strong>New workflow<\/strong> and fill in:<\/p>\n<ul><li><strong>Name.<\/strong><\/li><li><strong>Trigger<\/strong> and, for before\/after, the <strong>timing<\/strong> (for example 2 hours before).<\/li><li>For the &#8220;attendance marked&#8221; trigger, the <strong>outcome<\/strong> it applies to.<\/li><li><strong>Event types.<\/strong> Leave empty for all, or pick specific ones.<\/li><li><strong>Actions.<\/strong> Add one or more. For an email action write the subject and body (merge variables allowed); for &#8220;email another address&#8221; add the address; for a webhook add the URL and method.<\/li><li><strong>Enabled.<\/strong><\/li><\/ul>\n<p>Save. There is no limit on email reminder workflows.<\/p>\n<h3>3. When It Fires<\/h3>\n<ul><li><strong>Before\/after event<\/strong> workflows are scheduled when the booking is made and rescheduled automatically when the booking moves. A reminder that would already be in the past is skipped.<\/li><li><strong>Booked \/ cancelled \/ rescheduled<\/strong> workflows fire at once.<\/li><li><strong>Attendance marked<\/strong> workflows fire when you (or a co-host) choose an outcome, from the check-in email or the Meetings page, once per booking.<\/li><\/ul>\n<h3>4. Testing<\/h3>\n<p>Book your own event, wait for the timing, and check your inbox. For a quick test set a &#8220;1 minute before&#8221; reminder on a test event and book a slot a few minutes ahead.<\/p>\n<div class=\"kb-tip\"><strong>Tip:<\/strong> Scope reminders per event. A 24-hour reminder makes sense for a paid workshop; a 10-minute one is enough for an internal check-in.<\/div><\/div><\/div>\n<\/div>\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">What Are The Default Workflows Every New Account Gets?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>New accounts start with six workflows, all enabled and applied to every event type. Edit, scope, or switch them off as you like.<\/p>\n<h3>1. 24-Hour Reminder<\/h3>\n<p>Before the event, 24 hours. Emails the invitee with the event name, time in their time zone, and a Join Meeting button.<\/p>\n<h3>2. 1-Hour Reminder<\/h3>\n<p>Before the event, 1 hour. Emails the invitee and also emails you, with the invitee&#8217;s name and email and the join link.<\/p>\n<h3>3. Post-Meeting Follow-Up: Met<\/h3>\n<p>After you mark a meeting as <strong>Met<\/strong>. Thanks the invitee and can include the notes you typed when marking it (through <code>{{host_meeting_notes}}<\/code>).<\/p>\n<h3>4. Post-Meeting Follow-Up: No-Show<\/h3>\n<p>After you mark <strong>No-show<\/strong>. A gentle &#8220;we missed each other&#8221; message with your booking link to try again.<\/p>\n<h3>5. Post-Meeting Follow-Up: I Missed It<\/h3>\n<p>After you mark <strong>I missed it<\/strong>. An apology with your booking link.<\/p>\n<h3>6. Post-Meeting Follow-Up: Decided To Reschedule<\/h3>\n<p>After you mark <strong>Decided to reschedule<\/strong> (or use &#8220;They need a new time&#8221; on an upcoming booking). Tells the invitee the old slot is released and gives them the reschedule link.<\/p>\n<h3>7. What Is Not A Workflow<\/h3>\n<p>Booking confirmations, the host&#8217;s new-booking notification, cancellation and reschedule notices, and the &#8220;How did it go?&#8221; check-in are always sent by bookme. Optional workflow templates exist for confirmation, host notification, cancellation, reschedule, and a webhook on new booking if you want additional custom messages.<\/p>\n<h3>8. Accounts Created Earlier<\/h3>\n<p>Older accounts that only have the four follow-ups still receive the built-in 24-hour and 1-hour reminders automatically. As soon as you create any &#8220;before event&#8221; workflow, your workflows take over reminders entirely.<\/p>\n<h3>9. Toggling The Defaults Off<\/h3>\n<p>You can turn off any default workflow without deleting it. Open the workflow and toggle it off.<\/p>\n<div class=\"kb-tip\"><strong>Tip:<\/strong> Even if you do not customize the defaults, leave them on. A 24-hour and a 1-hour reminder are the difference between a 20 percent and a 5 percent no-show rate for most hosts.<\/div>\n<h3>10. Customizing The Defaults<\/h3>\n<p>Open any default workflow and edit its subject, body, timing, or scope. Common customizations:<\/p>\n<ul><li>Replace the generic reminder body with your brand voice.<\/li><li>Add your contact channels ({{host_whatsapp}}, {{host_linkedin}}) to the sign-off.<\/li><li>Add a personal touch to the post-meeting follow-ups.<\/li><\/ul><\/div><\/div>\n<\/div>\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">How To Edit The Subject And Body Of A Reminder Email?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>The subject and body of every workflow email are fully editable. You can rewrite them, add merge variables, and preview before saving.<\/p>\n<h3>1. Open The Workflow Editor<\/h3>\n<p>Reminder Workflows in sidebar, then click the workflow you want to edit.<\/p>\n<h3>2. Edit The Subject<\/h3>\n<p>The subject field is plain text plus merge variables. Click <code>{{ var }}<\/code> to insert a variable.<\/p>\n<p>Examples:<\/p>\n<ul><li>&#8220;Reminder: <code>{{event_name}}<\/code> tomorrow.&#8221;<\/li><li>&#8220;See you in 1 hour, <code>{{invitee_name}}<\/code>.&#8221;<\/li><li>&#8220;Looking forward to chatting today at <code>{{meeting_time}}<\/code>.&#8221;<\/li><\/ul>\n<p>Keep subjects under 50 characters where possible.<\/p>\n<h3>3. Edit The Body<\/h3>\n<p>The body is plain text with merge variables. Newlines preserve as paragraph breaks in the rendered email.<\/p>\n<p>bookme renders the body inside a branded HTML wrapper with your logo, brand color, and a &#8220;Join Meeting&#8221; button (for before-event workflows with meeting links).<\/p>\n<h3>4. The Merge-Variable Picker<\/h3>\n<p>Click <code>{{ var }}<\/code> to see every available variable for this trigger. Each one is listed with a description. Click to insert at the cursor position.<\/p>\n<h3>5. Preview Live<\/h3>\n<p>The right side of the editor shows a real-time preview of the rendered email using sample data. As you type or insert variables, the preview updates.<\/p>\n<h3>6. Testing With A Real Booking<\/h3>\n<p>Book your own event and wait for the timing to see the email land in your inbox exactly as an invitee would. For a quick test, set a &#8220;1 minute before&#8221; reminder on a test event and book a slot a few minutes ahead.<\/p>\n<p>For the post-meeting follow-ups, you do not need to wait: in a booking&#8217;s details on Meetings, choosing an outcome shows you the exact follow-up email that saving will send.<\/p>\n<h3>7. Markdown Support<\/h3>\n<p>The body field supports a subset of Markdown:<\/p>\n<ul><li><strong>Bold<\/strong> with <code><strong>text<\/strong><\/code><\/li><li><em>Italic<\/em> with <code><em>text<\/em><\/code><\/li><li>Bullet lists with <code>- item<\/code><\/li><li>Links with <code>[label](https:\/\/example.com)<\/code><\/li><\/ul>\n<p>Use sparingly. Heavy formatting can break in some email clients.<\/p>\n<h3>8. Saving<\/h3>\n<p>Click <strong>Save<\/strong> at the top. Changes apply to all future emails fired by this workflow. Bookings that already had this workflow fire (past emails sent) keep their original content.<\/p><\/div><\/div>\n<\/div>\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">What Merge Variables Are Available (Like {{invitee_name}}, {{meeting_link}})?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>Merge variables are placeholders that get replaced with real booking data when the email is sent. bookme exposes a comprehensive set for every workflow.<\/p>\n<h3>1. Identity<\/h3>\n<ul><li><code>{{invitee_name}}<\/code>, Full name of the invitee.<\/li><li><code>{{invitee_email}}<\/code>, Email of the invitee.<\/li><li><code>{{host_name}}<\/code>, Your display name.<\/li><\/ul>\n<h3>2. Host Contact Channels (From Settings &gt; Profile)<\/h3>\n<ul><li><code>{{host_email}}<\/code>, Your login email. Useful for sign-offs.<\/li><li><code>{{host_whatsapp}}<\/code>, Your WhatsApp number (if set).<\/li><li><code>{{host_telegram}}<\/code>, Your Telegram handle (if set).<\/li><li><code>{{host_linkedin}}<\/code>, Your LinkedIn URL (if set).<\/li><li><code>{{host_phone}}<\/code>, Your phone number (if set).<\/li><li><code>{{host_website}}<\/code>, Your website URL (if set).<\/li><\/ul>\n<p>Empty fields render as empty strings, not the literal <code>{{host_whatsapp}}<\/code>.<\/p>\n<h3>3. Event And Meeting<\/h3>\n<ul><li><code>{{event_name}}<\/code>, <a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/event-types\">Event type<\/a> title (e.g. &#8220;30-Min Intro Call&#8221;).<\/li><li><code>{{meeting_title}}<\/code>, Alias of <code>{{event_name}}<\/code>, used in follow-up templates.<\/li><li><code>{{date_time}}<\/code>, Meeting time in the recipient&#8217;s zone.<\/li><li><code>{{meeting_time}}<\/code>, Alias of <code>{{date_time}}<\/code>.<\/li><li><code>{{date_time_invitee}}<\/code>, Time forced to the invitee&#8217;s zone.<\/li><li><code>{{date_time_host}}<\/code>, Time forced to your zone.<\/li><li><code>{{duration}}<\/code>, Meeting duration in minutes.<\/li><li><code>{{location}}<\/code>, Meeting location or type label (e.g. &#8220;Zoom&#8221; or address).<\/li><li><code>{{meeting_link}}<\/code>, Direct join URL.<\/li><li><code>{{meeting_link_section}}<\/code>, Pre-styled meeting link block with a &#8220;Join meeting&#8221; button.<\/li><\/ul>\n<h3>4. Post-Meeting Notes<\/h3>\n<ul><li><code>{{host_meeting_notes}}<\/code>, Your notes from the Met-with-notes flow. Empty if you have not entered notes.<\/li><\/ul>\n<h3>5. Booking Actions<\/h3>\n<ul><li><code>{{booking_link}}<\/code>, Link to book again with you.<\/li><li><code>{{cta_url}}<\/code>, Alias of <code>{{booking_link}}<\/code>.<\/li><li><code>{{reschedule_link}}<\/code>, Link to reschedule this booking.<\/li><li><code>{{cancel_link}}<\/code>, Link to cancel this booking.<\/li><\/ul>\n<h3>6. Intake Form<\/h3>\n<ul><li><code>{{intake_answers_section}}<\/code>, The full set of intake-form answers, formatted as a clean block with labels.<\/li><\/ul>\n<p>You can also reference individual intake questions by their slug:<\/p>\n<ul><li><code>{{intake.company}}<\/code>, Answer to a question with slug &#8220;company.&#8221;<\/li><li><code>{{intake.budget}}<\/code>, Answer to a question with slug &#8220;budget.&#8221;<\/li><\/ul>\n<h3>7. Cancellation<\/h3>\n<ul><li><code>{{cancellation_reason_section}}<\/code>, Pre-formatted cancellation reason block (empty if no reason given).<\/li><\/ul>\n<h3>8. Insertion<\/h3>\n<p>Type <code>{{ var }}<\/code> in any field, or use the variable picker button next to the field, to insert.<\/p>\n<div class=\"kb-tip\"><strong>Tip:<\/strong> If you are not sure whether a variable will have data (e.g. <code>{{host_whatsapp}}<\/code> only if you set a number), book a test event and check the email. Empty variables render as empty strings, so the email still looks good with or without the data.<\/div><\/div><\/div>\n<\/div>\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">How To Add A &#8220;Join Meeting&#8221; Button To Your Reminder Emails?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>For &#8220;before event&#8221; workflows that send to the invitee or host, bookme automatically renders a styled &#8220;Join Meeting&#8221; button when the meeting has a video link. You can also include or exclude it manually.<\/p>\n<h3>1. The Automatic Button<\/h3>\n<p>Any workflow with trigger <strong>Before the event<\/strong> that sends to invitee or host and references the meeting will auto-render a mint-colored &#8220;Join Meeting&#8221; pill button at the bottom of the email body.<\/p>\n<p>The button appears whenever the booking has a meeting URL (Zoom, Google Meet, <a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/conferencing\">brandID Meet<\/a>). For in-person or phone-only events, the button is skipped automatically.<\/p>\n<h3>2. Manually Insert The Button<\/h3>\n<p>You can also place the button anywhere in the body using the <code>{{meeting_link_section}}<\/code> merge variable. It renders as the same styled pill button.<\/p>\n<p>Example body: &#8220;` Hi {{invitee_name}},<\/p>\n<p>Looking forward to chatting with you in 1 hour about {{event_name}}.<\/p>\n<p>{{meeting_link_section}}<\/p>\n<p>If something comes up, you can reschedule here: {{reschedule_link}}.<\/p>\n<p>See you soon, {{host_name}} &#8220;`<\/p>\n<h3>3. Just The Raw URL<\/h3>\n<p>If you want only the raw URL without the button styling, use <code>{{meeting_link}}<\/code> instead:<\/p>\n<p>&#8220;Join here: <code>{{meeting_link}}<\/code>&#8220;<\/p>\n<p>This is useful for fallback environments (very old email clients) where the styled button might not render perfectly.<\/p>\n<h3>4. Why The Button Matters<\/h3>\n<p>A clearly-clickable button raises join rates noticeably compared to a plain text URL. Invitees scanning their inbox can click without parsing.<\/p>\n<div class=\"kb-tip\"><strong>Tip:<\/strong> Include the button on BOTH the 24-hour reminder and the 1-hour reminder. The 1-hour reminder is the one most invitees actually open.<\/div>\n<h3>5. Customizing The Button Label<\/h3>\n<p>The default label is &#8220;Join Meeting.&#8221; To change it (e.g. to &#8220;Join Zoom Call&#8221; or &#8220;Open Video Room&#8221;), bookme uses the format of <code>{{meeting_link_section}}<\/code>. There is no direct label override; use a custom button by writing plain HTML in the body if you need a different label.<\/p>\n<h3>6. For In-Person Events<\/h3>\n<p>Before-event reminders for in-person events do not get a Join Meeting button. Instead, include the address in the body:<\/p>\n<p>&#8220;We&#8217;re meeting at 247 Main Street, Suite 200. The buzzer is on the left.&#8221;<\/p>\n<h3>7. Host Emails<\/h3>\n<p>In an email to yourself, the button uses your host link when the tool has one (the Zoom start link, the brandID Meet moderator link).<\/p>\n<h3>8. Late-Created Links<\/h3>\n<p>Video links are sometimes created a few seconds after the booking. Reminder emails read the current link when they are sent, so the button is always up to date.<\/p><\/div><\/div>\n<\/div>\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">How To Send A Post-Meeting Follow-Up Based On Whether You Met, Missed, Or No-Showed?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>bookme&#8217;s post-meeting check-in email asks you to mark how the meeting went, then fires the right follow-up based on your answer. You can fully customize each variation.<\/p>\n<h3>1. The Check-In Flow<\/h3>\n<p>Five minutes after each meeting ends, every attending host gets a &#8220;How did your meeting go?&#8221; email with four buttons. The first host to answer sets the outcome:<\/p>\n<ul><li><strong>Met.<\/strong> You attended and the meeting happened.<\/li><li><strong>Decided to reschedule.<\/strong> Meeting needs to move.<\/li><li><strong>I missed.<\/strong> You missed it on your end.<\/li><li><strong>No-show.<\/strong> The invitee did not show.<\/li><\/ul>\n<p>Clicking any one triggers the corresponding follow-up workflow.<\/p>\n<h3>2. The Four Follow-Up Templates<\/h3>\n<p>Each click triggers one of the four default follow-up emails to the invitee:<\/p>\n<ul><li><strong>Met click:<\/strong> Thank-you email with your notes (<code>{{host_meeting_notes}}<\/code>) and a &#8220;Book another time&#8221; CTA.<\/li><li><strong>Decided to reschedule click:<\/strong> Email with the reschedule link.<\/li><li><strong>I missed click:<\/strong> Apology email with the booking link for a fresh slot.<\/li><li><strong>No-show click:<\/strong> &#8220;We missed you&#8221; email with the booking link.<\/li><\/ul>\n<p>Only workflows belonging to the host who answered fire, not every host on the booking, and each booking is classified once.<\/p>\n<h3>3. Customize Each Template<\/h3>\n<p>Open Reminder Workflows, find the four templates (<code>followup_attended<\/code>, <code>followup_no_show<\/code>, <code>followup_host_missed<\/code>, <code>followup_rescheduled<\/code>). Edit subject and body independently.<\/p>\n<h3>4. Example Customization: Met Follow-Up<\/h3>\n<p>The default Met template includes <code>{{host_meeting_notes}}<\/code>. If you do not use the Met-with-notes flow, replace the body with something simpler:<\/p>\n<p>&#8220;` Hi {{invitee_name}},<\/p>\n<p>Great chatting with you today. Let me know if there is anything else I can help with.<\/p>\n<p>If you want to schedule another time, my calendar is here: {{booking_link}}<\/p>\n<p>Best, {{host_name}} &#8220;`<\/p>\n<h3>5. Example Customization: No-Show Follow-Up<\/h3>\n<p>The default tone is friendly but firm. Some hosts want a sharper version:<\/p>\n<p>&#8220;` Hi {{invitee_name}},<\/p>\n<p>Looks like we missed each other at {{meeting_time}}. No worries, things come up.<\/p>\n<p>If you would like to reschedule, here is my calendar: {{booking_link}}<\/p>\n<p>Regards, {{host_name}} &#8220;`<\/p>\n<h3>6. Skipping Specific Follow-Ups<\/h3>\n<p>You can disable any individual follow-up. Turn off the workflow but leave the others on. Useful when, for example, you do not want any follow-up after a &#8220;Decided to reschedule&#8221; click (because you handle reschedules manually).<\/p>\n<h3>7. Adding A Met-With-Notes Step<\/h3>\n<p>The Met outcome is special: before it saves, it opens an outcome window where you can type a short note about the meeting. That note appears as <code>{{host_meeting_notes}}<\/code> in the follow-up email when you choose to include it. See the next article for details.<\/p>\n<h3>8. On The Meetings Page<\/h3>\n<p>The same four outcomes are on the <strong>Just ended<\/strong> band at the top of Meetings and inside each ended booking&#8217;s details. Either one opens an outcome window before anything is saved: what the outcome does, a box for your note about the meeting, a live preview of the exact follow-up email, and an <strong>Email them now<\/strong> switch to send it or not. Click <strong>Save and email<\/strong> (or <strong>Save<\/strong>, with the switch off) to confirm; <strong>Escape<\/strong> or <strong>Cancel<\/strong> closes the window without saving anything.<\/p>\n<h3>9. Statuses Afterwards<\/h3>\n<p>Met and I missed it mark the booking completed; No-show marks it no-show; Decided to reschedule keeps it confirmed and waiting for a new time. The old slot is released and the calendar entries are removed until the invitee picks a new time.<\/p>\n<h3>10. Changing Your Answer<\/h3>\n<p>Clearing a marked outcome on the booking lets you choose again, though the email already sent is not recalled. On the Meetings page you can also switch <strong>Email them now<\/strong> off before saving: the outcome and your note are still saved and the invitee gets nothing, though emails to yourself and any webhooks on the workflow still run.<\/p><\/div><\/div>\n<\/div>\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">How To Use The Met-With-Notes Flow To Personalize Follow-Up Emails?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>When you mark a meeting <strong>Met<\/strong>, bookme opens an outcome window before anything is saved, with a place to type a note about the meeting. Tick <strong>Add this note to the email<\/strong> and the <code>{{host_meeting_notes}}<\/code> variable puts that note into the thank-you email to the invitee; leave it unticked and the note stays private on the booking.<\/p>\n<h3>1. The Flow End-To-End<\/h3>\n<ol><li>The meeting ends.<\/li><li>You get the &#8220;How did your meeting with <code>{{invitee_name}}<\/code> go?&#8221; email, or you open Meetings and find the booking in the <strong>Just ended<\/strong> band or its details.<\/li><li>You click <strong>Met.<\/strong><\/li><li>An outcome window opens (a page, if you clicked from the email), with a <strong>Note about this meeting<\/strong> box that is private by default.<\/li><li>You type a quick note, or leave it blank.<\/li><li>If the follow-up template has a place for notes (a <code>{{host_meeting_notes}}<\/code> variable), an <strong>Add this note to the email<\/strong> toggle appears, and the preview below it updates live to show the exact email with or without the note.<\/li><li>With <strong>Email them now<\/strong> left on, you click <strong>Save and email<\/strong>; with it switched off, you click <strong>Save<\/strong> to record the outcome without sending anything to the invitee.<\/li><li>If the note was added to the email, the invitee gets a thank-you email with it embedded inline. Either way, the note itself is kept on the booking.<\/li><\/ol>\n<h3>2. Why It Matters<\/h3>\n<p>A generic thank-you email gets skimmed. A thank-you with specific notes (&#8220;As promised, I&#8217;ll send the proposal by Friday, and the intro to Sarah next week&#8221;) feels human and reinforces the meeting outcome.<\/p>\n<p>You can also use the notes for:<\/p>\n<ul><li><strong>Action items.<\/strong> &#8220;Next steps: I&#8217;ll follow up with pricing options on Wednesday.&#8221;<\/li><li><strong>Resources.<\/strong> &#8220;Here&#8217;s the case study we discussed: [link]&#8221;<\/li><li><strong>Personal touches.<\/strong> &#8220;Loved hearing about your trip to Iceland; here&#8217;s that book I mentioned: [title]&#8221;<\/li><\/ul>\n<h3>3. The Default Met Template<\/h3>\n<p>The follow-up uses the <code>followup_attended<\/code> template by default:<\/p>\n<p>&#8220;` Hi {{invitee_name}},<\/p>\n<p>Thanks for the time today. Really enjoyed our conversation about &#8220;{{meeting_title}}&#8221;.<\/p>\n<p>{{host_meeting_notes}}<\/p>\n<p>If you would like to schedule another time, the link below will pull up my calendar. {{booking_link}}<\/p>\n<p>Regards, {{host_name}} &#8220;`<\/p>\n<p>If you do not type a note, <code>{{host_meeting_notes}}<\/code> renders as empty, and the email still flows naturally.<\/p>\n<h3>4. Customize The Notes Template<\/h3>\n<p>Edit the <code>followup_attended<\/code> workflow under Reminder Workflows. You can:<\/p>\n<ul><li>Move the notes block to a different spot.<\/li><li>Add a header above the notes (&#8220;Here&#8217;s a quick recap:&#8221;).<\/li><li>Skip the notes entirely if you do not want them on certain event types.<\/li><\/ul>\n<h3>5. Choosing Whether To Send, And Whether To Include The Note<\/h3>\n<p>The outcome window gives you two separate choices before you save:<\/p>\n<ul><li><strong>Add this note to the email.<\/strong> Only shown when the follow-up template has a place for notes (a <code>{{host_meeting_notes}}<\/code> variable). Ticked, your note appears in the email exactly as the preview shows it. Left unticked, the note stays private on the booking and the email goes out without it.<\/li><li><strong>Email them now.<\/strong> On by default. Switch it off to save the outcome and your note without emailing the invitee at all; emails to yourself and any webhooks on the workflow still run.<\/li><\/ul>\n<p>Click <strong>Save and email<\/strong> (or, with <strong>Email them now<\/strong> off, <strong>Save<\/strong>) to confirm. <strong>Escape<\/strong> or <strong>Cancel<\/strong> closes the window without saving anything, so nothing is recorded and you can come back to it later. <strong>Ctrl+Enter<\/strong> (<strong>Cmd+Enter<\/strong> on a Mac) saves from the keyboard.<\/p>\n<p>You can also close the tab or window without doing anything; the outcome remains unrecorded. From the check-in email, you can re-click Met any time before the email-action token expires (14 days).<\/p>\n<h3>6. Length Of Notes<\/h3>\n<p>Up to 2000 characters. Keep them short. Two or three sentences max is the sweet spot.<\/p>\n<div class=\"kb-tip\"><strong>Tip:<\/strong> Type the notes while the meeting is still fresh, within 5-10 minutes of finishing. After an hour you will already forget details that would have made the email feel personal.<\/div>\n<h3>7. Notes Are Saved Per Booking<\/h3>\n<p>The notes get attached to the booking record permanently. You can review them later from the booking detail panel on your dashboard.<\/p><\/div><\/div>\n<\/div>\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">How To Send A Webhook Or Trigger A Custom Action After A Booking?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>Webhooks let bookme send a JSON payload to any URL when a workflow fires. Use them to push bookings into your CRM, alert Slack, or trigger any other system.<\/p>\n<h3>1. Open Or Create A Workflow<\/h3>\n<p>Reminder Workflows page, then <strong>+ New Workflow<\/strong> or edit an existing one, or use the <strong>Webhook on new booking<\/strong> template.<\/p>\n<h3>2. Pick A Trigger<\/h3>\n<p>Any trigger works, including booked, cancelled, rescheduled, before or after an event, or an attendance-marked outcome. Common choices:<\/p>\n<ul><li><strong>When a booking is created.<\/strong> Fires immediately on booking. Best for CRM intake.<\/li><li><strong>After the event.<\/strong> Fires after the meeting. Best for &#8220;meeting complete&#8221; updates.<\/li><li><strong>When attendance is marked.<\/strong> Fires when you click Met \/ Missed \/ No-show. Best for pipeline state changes.<\/li><\/ul>\n<h3>3. Add A Webhook Action<\/h3>\n<p>In the <strong>Actions<\/strong> section, click <strong>+ Add action,<\/strong> then pick <strong>Webhook.<\/strong><\/p>\n<p>Enter:<\/p>\n<ul><li><strong>URL.<\/strong> The endpoint to send to (e.g. <code>https:\/\/hooks.zapier.com\/...<\/code> or <code>https:\/\/your-crm.com\/api\/bookings<\/code>). It must be a public http or https address with a real domain name; private addresses, localhost, and internal hostnames are refused when you save. bookme does not follow redirects, so point the webhook at its final URL.<\/li><li><strong>Method.<\/strong> POST (the default), PUT, or GET.<\/li><li><strong>(Optional) Secret.<\/strong> A signing secret bookme uses to sign the request so you can verify it came from bookme.<\/li><\/ul>\n<h3>4. What&#8217;s In The Payload<\/h3>\n<p>bookme sends a JSON body like:<\/p>\n<p>&#8220;<code>json { \"event\": \"booking.created\", \"booking\": { \"id\": \"abc123\", \"event_type\": \"30-Min Intro Call\", \"start_time\": \"2026-07-15T14:00:00Z\", \"end_time\": \"2026-07-15T14:30:00Z\", \"invitee_name\": \"Sarah Chen\", \"invitee_email\": \"sarah@example.com\", \"host_name\": \"James Li\", \"host_email\": \"james@brandid.app\", \"location\": \"Zoom\", \"meeting_link\": \"https:\/\/zoom.us\/j\/123\", \"intake_answers\": [ { \"label\": \"Company\", \"value\": \"Acme\" }, { \"label\": \"Budget\", \"value\": \"$50k\" } ] } } <\/code>&#8220;<\/p>\n<p>The exact schema depends on the trigger; see bookme&#8217;s developer docs for full reference.<\/p>\n<h3>5. Verifying The Signature<\/h3>\n<p>If you set a secret, bookme adds a header <code>X-Bookme-Signature<\/code> to the request. Compute HMAC-SHA256 of the request body with your secret; if it matches the header, the request is authentic.<\/p>\n<h3>6. Timeouts And Retries<\/h3>\n<p>The request times out after 10 seconds. A failed call (a network error, a timeout, or a non-2xx reply) is retried a few times with increasing delays, roughly:<\/p>\n<ul><li>5 minutes later.<\/li><li>30 minutes later.<\/li><li>4 hours later.<\/li><\/ul>\n<p>After three failed attempts, the webhook is given up. You see the failure in your workflow&#8217;s &#8220;Recent activity&#8221; log. Make your endpoint return 200 quickly and do slow work afterwards.<\/p>\n<h3>7. Common Integrations<\/h3>\n<ul><li><strong>Zapier, Make, or n8n:<\/strong> Use bookme as a trigger; build any downstream automation.<\/li><li><strong>CRM (HubSpot, Salesforce, Pipedrive):<\/strong> Push bookings as new contacts or deals.<\/li><li><strong>Slack:<\/strong> Post a message to a channel (wrap the payload with a small automation first, since Slack expects its own format).<\/li><li><strong>Custom database:<\/strong> Save to your own backend.<\/li><\/ul>\n<div class=\"kb-tip\"><strong>Tip:<\/strong> Scope the webhook workflow to the event types you want in your CRM, so internal or test events do not create records.<\/div><\/div><\/div>\n<\/div>\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">Can You Send SMS Reminders, Or Is It Email Only?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>Workflows send email and webhooks only. There is no SMS or WhatsApp sending in bookme today.<\/p>\n<h3>1. Reaching Phones Anyway<\/h3>\n<ul><li><strong>Calendar invitations.<\/strong> Bookings written to your Google Calendar invite the invitee, so their phone&#8217;s calendar app notifies them before the meeting.<\/li><li><strong>A webhook to an SMS service.<\/strong> Add a webhook action to your reminder workflow and point it at an automation (Zapier, Make, n8n) that sends a text through your own Twilio or similar account. Collect the phone number with a required question in your <a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/intake-forms-routing\">question form<\/a>.<\/li><li><strong>Your contact channels in email.<\/strong> <code>{{host_whatsapp}}<\/code> and <code>{{host_phone}}<\/code> let invitees reach you by phone or WhatsApp from any email.<\/li><\/ul>\n<h3>2. Why Email<\/h3>\n<p>Email reminders with a Join Meeting button work for every invitee without asking for a phone number or consent, and they carry the reschedule and cancel links.<\/p><\/div><\/div>\n<\/div>\n<div class=\"kb-item\">\n<button aria-expanded=\"false\" class=\"kb-q\"><svg class=\"kb-qi\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2.5\" viewbox=\"0 0 24 24\"><path d=\"M12 5v14M5 12h14\"><\/path><\/svg><span class=\"kb-qt\">How To Turn A Workflow On Or Off Without Deleting It?<\/span><\/button>\n<div class=\"kb-a\"><div class=\"kb-a-inner\"><p>Toggling a workflow off pauses it without deleting its configuration. Useful when testing, when on vacation, or when the workflow is no longer needed for a specific event.<\/p>\n<h3>1. Open The Reminder Workflows Page<\/h3>\n<p>Reminder Workflows in sidebar. Each workflow has a toggle at the top right of its card.<\/p>\n<h3>2. Toggle Off<\/h3>\n<p>Click the <strong>Active<\/strong> toggle. The workflow stops firing for any new booking.<\/p>\n<p>Bookings that already had this workflow&#8217;s job scheduled (e.g. a 1-hour reminder for a meeting later today) DO still fire. Toggling off only stops future scheduling, not in-flight jobs. Switching a workflow back on does not add reminders to bookings made while it was off. Cancelling or rescheduling a booking re-queues everything according to the workflows enabled at that moment.<\/p>\n<h3>3. Toggle Back On<\/h3>\n<p>Click the toggle again. The workflow resumes for new bookings.<\/p>\n<h3>4. Per-Event-Type Off<\/h3>\n<p>If you want a workflow to apply to most event types but not one specific event, do not toggle it off entirely. Instead:<\/p>\n<ul><li>Open the workflow.<\/li><li>Scope it to specific event types (the <strong>Event types<\/strong> dropdown).<\/li><li>Untick the one you want to skip.<\/li><\/ul>\n<h3>5. Bulk Pause All Workflows<\/h3>\n<p>For vacations or temporary breaks, you can bulk-pause all workflows. At the top of the Reminder Workflows page, click <strong>Pause all.<\/strong> All workflows pause.<\/p>\n<p>When you return, click <strong>Resume all.<\/strong><\/p>\n<div class=\"kb-tip\"><strong>Tip:<\/strong> Pause-all is especially useful for the post-meeting check-in. While on vacation, you do not want to get &#8220;How did your meeting go?&#8221; emails for meetings someone else covered.<\/div>\n<h3>6. Delete<\/h3>\n<p>Use <strong>Delete<\/strong> on the card to remove a workflow for good. Queued reminders for existing bookings are not affected.<\/p>\n<h3>7. Toggle History<\/h3>\n<p>bookme keeps a history of when each workflow was toggled on or off, visible in the <strong>Activity log<\/strong> at the bottom of the workflow editor. Useful for troubleshooting &#8220;why did this not fire?&#8221;<\/p><\/div><\/div>\n<\/div>\n<\/div>\n<div class=\"kb-related\">\n<h2>Related articles<\/h2>\n<ul>\n<li><a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/#how-to-guides\">How-To Guides \u2192<\/a><\/li>\n<li><a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/event-types\">Event Types \u2192<\/a><\/li>\n<li><a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/intake-forms-routing\">Intake Forms &amp; Routing \u2192<\/a><\/li>\n<li><a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/bookings-inbox\">Meetings \u2192<\/a><\/li>\n<li><a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/notifications-email\">Notifications &amp; Email Settings \u2192<\/a><\/li>\n<li><a href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/troubleshooting\">Troubleshooting \u2192<\/a><\/li>\n<\/ul>\n<\/div>\n<div class=\"kb-cta\">\n<h3>Still stuck? We&#8217;re happy to help.<\/h3>\n<p>Create your bookme account, see pricing, or reach out to support directly.<\/p>\n<div class=\"kb-cta-btns\">\n<a class=\"kb-btn kb-btn-coral\" href=\"https:\/\/bookme.brandid.app\/\">\n<svg fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" viewbox=\"0 0 24 24\"><path d=\"M5 12h14M12 5l7 7-7 7\"><\/path><\/svg>Create Free Account<\/a>\n<a class=\"kb-btn kb-btn-ghost\" href=\"https:\/\/bookme.brandid.app\/pricing\">\n<svg fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" viewbox=\"0 0 24 24\"><rect height=\"18\" rx=\"2\" width=\"18\" x=\"3\" y=\"4\"><\/rect><path d=\"M3 10h18\"><\/path><\/svg>See Pricing<\/a>\n<a class=\"kb-btn kb-btn-ghost\" href=\"mailto:support@brandid.app\">\n<svg fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" viewbox=\"0 0 24 24\"><path d=\"M21 15a2 2 0 0 1-2 2H7l-4 4V5a2 2 0 0 1 2-2h14a2 2 0 0 1 2 2z\"><\/path><\/svg>Contact Support<\/a>\n<\/div>\n<\/div>\n<a class=\"kb-back\" href=\"https:\/\/bookme.brandid.app\/blog\/index.php\/bookme-knowledge-base\/\"><svg fill=\"none\" height=\"16\" stroke=\"currentColor\" stroke-width=\"2\" viewbox=\"0 0 24 24\" width=\"16\"><path d=\"m15 18-6-6 6-6\"><\/path><\/svg>Back to Help Center<\/a>\n<\/section>\n<script>\ndocument.querySelectorAll('#reminders-workflows .kb-q').forEach(function(q){\n  q.addEventListener('click', function(){\n    var item = q.closest('.kb-item');\n    var a = item.querySelector('.kb-a');\n    var open = item.classList.toggle('open');\n    q.setAttribute('aria-expanded', open ? 'true' : 'false');\n    a.style.maxHeight = open ? a.scrollHeight + 'px' : '0';\n  });\n});\nwindow.addEventListener('resize', function(){\n  document.querySelectorAll('#reminders-workflows .kb-item.open .kb-a').forEach(function(a){ a.style.maxHeight = a.scrollHeight + 'px'; });\n});\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>Help Center\/ Reminders &amp; Workflows Automation Reminders &amp; Workflows Automate the emails that go out before and after each meeting: confirmations, reminders, follow-ups. What Are Reminder Workflows And Why Are They Important? A reminder workflow is an automation attached to your bookings: when something happens (a booking is made, a time approaches, a meeting ends), [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":44,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-123","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/bookme.brandid.app\/blog\/index.php\/wp-json\/wp\/v2\/pages\/123","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bookme.brandid.app\/blog\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/bookme.brandid.app\/blog\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/bookme.brandid.app\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bookme.brandid.app\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=123"}],"version-history":[{"count":0,"href":"https:\/\/bookme.brandid.app\/blog\/index.php\/wp-json\/wp\/v2\/pages\/123\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/bookme.brandid.app\/blog\/index.php\/wp-json\/wp\/v2\/pages\/44"}],"wp:attachment":[{"href":"https:\/\/bookme.brandid.app\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=123"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}