Skip to main content
Intempt
Coming soon

Meeting no show recovery

Assumes a diary clash rather than disinterest and offers an easy reschedule three times over a week, then hands the prospect to nurture.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

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

  1. 1

    Find who missed a meeting

    Coming soon

    Blu builds a step

  2. 2

    Write three reschedule notes

    Coming soon

    Blu builds a step

  3. 3

    Send at 1 hour, 2 days, 5 days

    Coming soon

    Blu builds a step

  4. 4

    Watch the no show rate

    Coming soon

    Blu builds a step

About this recipe

When to use it

Most no-shows aren't lost deals, they're calendar conflicts. This runs a 3-touch recovery over a week assuming exactly that, offering an easy reschedule before giving up on the meeting.

What it delivers

When a prospect doesn't attend a scheduled meeting, fires a 3-touch recovery sequence over 7 days assuming a scheduling conflict, offering an easy reschedule, then dropping into nurture if still unresponsive.

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

“Assumes a diary clash rather than disinterest and offers an easy reschedule three times over a week, then hands the prospect to nurture.”

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. 01Find who missed a meetingBuild a segment 'Recent no-shows - last 7 days' capturing users with a meeting_completed event in the last 7 days where the attendance attribute = false (or attended_minutes < 2). Excludes users who have already rescheduled within 24 hours of the original meeting.
    2. 02Write three reschedule notesGenerate 3-touch recovery email content. Touch 1 (1 hour after no-show): assumes scheduling conflict; warm tone; offers easy reschedule with new booking link; no guilt. Touch 2 (48 hours later, if unresponsive): brief reminder that the booking link is still available; references the original meeting context. Touch 3 (5 days later): final outreach with value-content (case study or playbook PDF relevant to their stage) plus the booking link as a soft re-engage. Send-from: the original meeting host. Use the result of "Find who missed a meeting".
    3. 03Send at 1 hour, 2 days, 5 daysBuild a 3-touch journey wired to the no-show segment: send touch 1 at 1 hour after no-show, touch 2 at 48 hours after no-show (skip if user has rescheduled), touch 3 at 5 days after no-show (skip if user has rescheduled or replied). After touch 3 with no engagement: move user into the standard nurture journey (handoff). Exit conditions: Meeting scheduled (rescheduled), email_replied, or user opted out. Use the result of "Find who missed a meeting", "Write three reschedule notes".
    4. 04Watch the no show rateCompose a dashboard tracking no-show recovery health: overall no-show rate (% of scheduled meetings that no-show, trend over time), reschedule conversion rate (% of no-shows that book a new meeting via the recovery journey), time-to-reschedule distribution, and per-touch open/click/reschedule rates. Break down by meeting type and rep. Flag if no-show rate is rising more than 5 percentage points week-over-week (process or scheduling-link problem signal). Use the result of "Find who missed a meeting", "Write three reschedule notes", "Send at 1 hour, 2 days, 5 days".

    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 /no-show-recovery 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