Every email this appointment sent, and what happened to it

A per-appointment list of every message sent — confirmation, each reminder, no-show, cancellation — with delivered, opened and clicked timestamps.

What it is

Each send is tagged with the appointment and the step it belongs to, then matched against delivery events from the mail provider. Machine opens are excluded from the opened timestamp.

Also called: did they open it · email tracking · was the reminder delivered · email history

See it
Every email this appointment sent, and what happened to it
Apr
May
Jun
Jul
Marlin Hoover — Hobby Shop
Framing
Gideon Alt — 40×64 Shop
Concrete
Sutter Kline — Hobby Shop
Trim
Marlin Hoover — 40×64 Shop
Framing
Gideon Alt — 30×40 Garage
Concrete
Framing crewConcrete crewTrim crew
The appointment modal's trail: rows per step with delivered / opened / clicked times. platform/calendar/page.tsx. Sample data — no customer information appears here.
How it works
  1. 1Sends are logged with a source of appt:<id>:<step>; the trail queries that prefix.
  2. 2Provider message ids join the sends to their delivery events.
  3. 3The first genuine occurrence of each event type is reported per message.
Why we built it

The lifecycle header states the purpose: 'Every email is sent with a source of appt:<id>:<step> so opens/clicks (Mailgun events) can be read back per appointment.' Excluding machine opens keeps the signal honest.

The problem
  • No per-appointment record of outbound messages
  • Scanner opens counted as real reads
Sound familiar?
What you get
Evidence of what was sent and what was read
A no-show conversation grounded in facts

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →