How it works
From booking link to evidence record.
ComplianceVia MeetingProof runs every meeting through the same five steps. Guests see one scheduler. Hosts keep their tools. Your organization receives an outcome and an evidence record for every meeting. An outcome is the result MeetingProof assigns to a meeting. Held and Guest no-show are two examples. An evidence record is the finished account of one meeting: who joined, when, for how long and how each person was identified.
Step 1
Hosts keep their links. Guests see one scheduler.
A host is any staff member who takes meetings. A guest is the person who books. Each host keeps the booking tool they already use. MeetingProof reads each link's availability and merges the open times. Guests see one booking page for each meeting type. “Product demo” and “Academic advising” are two meeting types.
- Guests choose a time. MeetingProof assigns a host by rule. The default is round-robin: hosts take turns, fewest meetings first. Guests can pick a host instead.
- Before booking, MeetingProof rechecks the time on the host's link and calendar. If a time filled a moment ago, the guest sees the next open times instead.
- The booking page works as a hosted page or as an embed on your own site.
- Lead source (the origin of the booking) is captured from the page link automatically.
| Tool | Status |
|---|---|
| Cal.com | In development |
| Outlook calendar (Microsoft 365) | In development |
| Reclaim (selected organizations) | In development |
| Calendly | Planned |
| Microsoft Bookings | Planned |
| HubSpot | Planned |
| Google calendar (blocking time) | Planned |
Step 2
In developmentOne Zoom account. One source of attendance.
Every booking lands on your organization's Zoom account. The host's booking tool does not matter. MeetingProof writes the meeting straight onto the host's calendar. The time is blocked at once.
- Each attendee is registered with Zoom and receives a personal join link.
- Attendance is matched to each attendee's personal join link, not to a display name like “iPhone”.
- Colleagues added by the guest receive their own links and check in on their own.
Step 3
In developmentEvery join link opens a check-in page first.
The check-in page is the page every join link opens first. The page confirms the guest the way your organization requires. A fresh one-time email code is one option. MeetingProof records the check-in. Then the guest's personal Zoom link opens.
- A forwarded check-in link alone does not admit a stranger when your settings require a fresh code.
- The check-in counts as an attendance signal apart from Zoom.
- If a consent form changed after booking, the guest signs the new version here.
Step 4
Who joined, who left and when.
MeetingProof records each join and leave as Zoom reports them during the meeting. About an hour after the scheduled end, MeetingProof checks those events against Zoom's participant report. No outcome rests on a single signal.
Step 5
In developmentEvery meeting closes with an outcome.
MeetingProof assigns one of six outcomes and finalizes the evidence record. Later corrections are added as amendments. The original stays in place.
- Held
- Host and guest both present, overlapping 10 minutes or more.
- Too short
- Host and guest both present, overlapping less than 10 minutes.
- Guest no-show
- Host present. The guest never joined by the scheduled end.
- Host no-show
- Guest present at check-in or in Zoom. The host never joined.
- Rescheduled
- Moved before the start time.
- Cancelled
- Cancelled before the start time.
Sample record
What an evidence record holds.
Evidence record
Illustrative- Outcome
- Held
- Meeting
- Product demo · Tue 2:00–2:30 PM CT
- Organization
- Example Software Co.
- Host
- Rep A · joined 1:58 · left 2:31 · 33 min
- Guest
- J. Rivera, Northwind Analytics · checked in 1:59 (email code) · joined 2:00 · left 2:29 · 29 min
- Overlap
- 29 minutes
- Recording
- Off (organization setting)
- Zoom meeting
- 8•• ••• •412
- Finalized
- Tue 3:30 PM CT
- Record hash
- 3f9a…c21e
- Audit entries
- 14, chain intact
- Who joined and left, and when, for each person
- Time in the meeting and overlap with the host
- Check-in events and how each person was identified
- Consent records that apply to the meeting
- Zoom meeting identifiers and the raw event references
- A hash of the finished record, linked into the tamper-evident audit log (a later change breaks the chain and shows)
Evidence export as PDF and JSON for disputes. Planned
No-show loop
Reminders, nudges and rebooking on a schedule.
The no-show loop is the series of messages before and after each meeting. Every message runs on a timer. Nobody chases a guest by hand.
Email In developmentSMS reminders Planned
- At booking. A one-time email code stops typo and junk bookings.
- 24 hours before. Reminder with Confirm and Reschedule. Still unconfirmed 2 hours before the start? The host is alerted.
- 1 hour before. Reminder with the check-in link.
- 5 minutes after the start. No check-in yet? The guest receives a “We're waiting” email. The host receives an alert.
- 60 minutes after the end. The outcome is final.
- After a held meeting. Guest and host receive a short follow-up poll.
- After a guest no-show. The guest receives a link to pick a new time. The new meeting links back to the first.
- After a host no-show. The guest receives an apology and a rebook link. The organization's admin is flagged.
Controls
Your organization sets the rules.
- Show rate (the share of booked meetings that were held) by host, lead source and week. Each meeting's evidence is one click away. In development
- Privacy settings that cascade from organization to location to host to meeting. Details on the Trust page.
- Outcome export (CSV) and an outbound webhook for your CRM. An outbound webhook sends each outcome to another system automatically. In development
- Booking pages and emails on your own domain (for example, book.yourcompany.com). Planned