HR & RECRUITING

Repeat No-Show Escalation and Withdrawal Policy

Tracks no-show counts per candidate across Zoom interviews; offers a reschedule on the first miss, escalates to the hiring manager on the second.

CategoryHR & Recruiting
Enginesim
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerZoom interview ends with no-showZoomZoom
  • ActionIncrement candidate no-show countPostgreSQLPostgres
  • LogicBranch on strike count
  • ActionSend reschedule or withdrawal emailGmailGmail
  • OutputEscalate or close card in ClickUpClickUpClickUp

What it does

Applies a fair, consistent policy to repeat no-shows. It counts how many times each candidate has missed a scheduled Zoom interview and takes a different action at each strike: reschedule, escalate, or close the loop with a withdrawal notice.

When to use it

Use this when you need a defensible, uniform rule for handling repeat missed interviews instead of ad-hoc recruiter judgment. It protects interviewer time while still giving candidates a documented second chance.

How it works

  1. 1A Zoom meeting-ended webhook confirms a candidate no-show for the interview.
  2. 2The flow increments the candidate's no-show count stored in Postgres and reads the running total.
  3. 3A branch routes on the count: first miss, second miss, or third-plus.
  4. 4First miss sends a standard reschedule offer email with open slots.
  5. 5Second miss emails the offer and pings the hiring manager in ClickUp to review whether to continue.
  6. 6Third miss sends a courteous withdrawal-from-process email and closes the candidate's ClickUp card with a documented reason.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect GmailRead, draft, send, label.
  4. 4
    Connect ClickUpDocs + tasks + chats in one workspace.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.