New to Attio?Get 10% off when you sign up through Craftt.Try Attio free →

Lifecycle & follow-up · Insurance

Event follow-up sequencing

Routes every event registrant, no-show, and attendee into the right follow-up track and drafts the touchpoints.

On registration-status change (per event edition)LiveClaude CoWorkAttio

The problem

Built for the same a motor-insurance TPA managing a network of insurers and repair workshops, which runs a recurring insurance event series.

After each edition, Marketing walked the participant list by hand to follow up. It was slow, inconsistent, and easy to drop people.

What it does

The agent reads each participant's registration status and attendance, then routes them into one of seven follow-up tracks.

For each person it drafts the touchpoint message in their preferred channel, for Marketing to review and send.

Under the hood

Data flow

  • Behaves like an on-status-change trigger: stable entries are skipped, and a status edit since the last run is what produces a fresh draft.
  • Runs entirely inside Attio with no external connectors.
  • Drafts are rewritten from each person's record rather than templated.

Outputs

  • Routing into a track: Confirm & reminder, Nudge to confirm, Register reminder, Keep warm, Waitlist update, Post-event nurture, or No-show re-engage.
  • Touchpoint draft(s) per preferred channel (email, WhatsApp, or phone script) on the person record.
  • A Follow-up track value and Follow-up draft status set to Draft ready, so Marketing filters the list instead of reading every row.

Guardrails

  • Never sends anything: drafts only.
  • Never overwrites registration or attendance; it reads those and writes only the track, draft status, and a note.
  • Idempotent: skips people already routed for their current track.

What changed

  • Marketing follow-up moves off the manual treadmill.
  • Every participant lands in a track with a draft ready, filterable in a single view.

Runs on the customer’s own Claude subscription. No separate model API key, no extra infrastructure. Where an automation uses LinkedIn (APIFY) or firmographic (Lusha) lookups, those run on the customer’s own credits.