Meeting No-Show Risk
Calculates no-show probability using confirmation status, contact history, and invite timing. Flags high-risk meetings.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Data fetch
meeting
?
▼
Process (12 steps)
validate_meeting
guard
Stop if meeting result properties is missing
days_since_invite
date_diff
Calculate days between meeting result properties invite sent date and now
contact
?
validate_contact
guard
Stop if contact result properties is missing
meeting_count_denom
math
Calculate: max({{step.contact.result.properties.past_meeting_count}}, 1)
base_no_show_rate
math
Calculate: ({{step.contact.result.properties.past_no_show_count}} / {{step.meeting_count_denom}}) * 100
confirmation_penalty
math
Calculate: (1 - {{step.meeting.result.properties.confirmation_email_replied}}) * 20
invite_delay_penalty
math
Calculate: max(0, {{step.days_since_invite}} - 3) * 5
raw_probability
math
Calculate: {{step.base_no_show_rate}} + {{step.confirmation_penalty}} + {{step.invite_delay_penalty}}
no_show_probability
math
Calculate: min(100, max(0, {{step.raw_probability}}))
historical_no_show_rate
math
Calculate: {{step.contact.result.properties.past_no_show_count}} / {{step.meeting_count_denom}}
risk_checklist
to_checklist
Format results as an actionable checklist
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
hubspot
setting
=
probability warn threshold
number
=
30
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.