Skip to main content
Intempt
Coming soon

Meeting reminders before a call

Reminds the other side before a booked meeting at 48 hours, 24 hours and 2 hours, and shows what that does to your show rate.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

5 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Write the two reminder emails

    Coming soon

    Blu builds a step

  2. 2

    Write the two hour text

    Coming soon

    Blu builds a step

  3. 3

    Remind at 48, 24 and 2 hours

    Coming soon

    Blu builds a step

  4. 4

    Tell the host, link the deal

    Coming soon

    Blu builds a step

  5. 5

    See what reminders are worth

    Coming soon

    Blu builds a step

About this recipe

When to use it

One confirmation email at booking time doesn't stop no-shows - most of them happen because the meeting slipped someone's mind days later. This fires a ladder of reminders timed to when people actually forget.

What it delivers

When a B2B meeting books, fires a reminder ladder - 48hr email, 24hr email, 2hr SMS - to maximize show-rate, plus a host notification on booking and a coverage dashboard. Distinct from the scheduling-link setup itself.

How you prompt this

Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.

Tell Blu Agent what you want

“Reminds the other side before a booked meeting at 48 hours, 24 hours and 2 hours, and shows what that does to your show rate.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.

Outputs

    How the recipe runs

    Blu follows the steps in order and shows you each one before anything goes live.

    1. 01Write the two reminder emailsGenerate 2 reminder email touches for upcoming B2B meetings. 48hr-before reminder: full agenda recap, attendee list, add-to-calendar links (iCal + Google + Outlook), location/conferencing details, and a reschedule link. 24hr-before reminder: lighter: just the meeting time, conferencing link, and a low-friction reschedule button. Send-from: the meeting host. Tone: professional, confirming.
    2. 02Write the two hour textGenerate a 2-hour-before SMS reminder. Format: under 160 chars. Include meeting time, conferencing link (shortened), and a reply-RESCHEDULE option. Example: 'Reminder: your call with [Host Name] starts in 2 hours. Join: [link]. Reply RESCHEDULE to move it.' Only fires if user has SMS opt-in. Use the result of "Write the two reminder emails".
    3. 03Remind at 48, 24 and 2 hoursBuild a 3-touch journey triggered by Meeting scheduled, with all touches timed relative to meeting_start_time. Touch 1: 48hr email reminder (skip if meeting is sooner than 48hr at scheduling time). Touch 2: 24hr email reminder. Touch 3: 2hr SMS reminder (only if user has SMS opt-in). Exit conditions: meeting_completed, meeting_cancelled, or user opted out. If meeting is rescheduled, recompute all touch times from the new meeting_start_time. Use the result of "Write the two reminder emails", "Write the two hour text".
    4. 04Tell the host, link the dealCreate a workflow firing on Meeting scheduled. Step sequence: (1) post host notification to Slack with meeting details and a link to the user record; (2) link the meeting to the open deal if one exists for the user's account; (3) trigger the reminder journey. On meeting_cancelled, send the host a notification and exit the journey for that user. Use the result of "Write the two reminder emails", "Remind at 48, 24 and 2 hours".
    5. 05See what reminders are worthCompose a dashboard tracking meeting show-rate: overall show-rate by reminder cadence completeness (how many of the 3 reminders were delivered before the meeting), email reminder open/click rates, SMS reminder reply rate, and reschedule rate. Break down by meeting type and rep. Compare show-rate for meetings with vs. without the full reminder ladder (this is the proof-of-value chart). Use the result of "Write the two reminder emails", "Write the two hour text", "Remind at 48, 24 and 2 hours", "Tell the host, link the deal".

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /booking-confirmation-flow in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Sid Chaudhary

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Return rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe