RELATIONSHIP CONTEXT
Scheduling contacts requirements guide
Scheduling contacts. See the people you meet, their upcoming and past events, and the context needed for the next conversation.
REQUIREMENTS GUIDE · NOT A LIVE-FEATURE CLAIM. This page explains scheduling contacts requirements. Confirm production availability before depending on this capability.RELATIONSHIP CONTEXT
Workflow requirements: Meeting history
Meeting history
Contact notes
Reusable invitations
Short answer: See the people you meet, their upcoming and past events, and the context needed for the next conversation. This page explains scheduling contacts requirements. Confirm production availability before depending on this capability.
Requirements for meeting history
| Status today | REQUIREMENTS GUIDE · NOT A LIVE-FEATURE CLAIM |
|---|---|
| Main job | See the people you meet, their upcoming and past events, and the context needed for the next conversation. |
| Requirements | Meeting history |
| Contact notes | |
| Reusable invitations | |
| Try it now | The working core: booking pages and group polls. |
How relationship context works for organizers and guests
The organizer needs meeting history. The guest needs a result that stays clear after the meeting is confirmed or changed. Judge the public outcome, not just the settings screen.
The key relationship context decision
- Decision to make. Keep enough relationship context to prepare for the next conversation without turning the scheduler into an uncontrolled customer database.
- Example. A consultant sees a client's last review, the next confirmed call, and a short agreed preparation note before sending another invitation.
- Failure to prevent. Duplicate contact identities fragment meeting history, while copied private notes expose information that the scheduling task does not need.
- Evidence to keep. One contact timeline shows upcoming, completed, moved, and cancelled meetings with clear ownership and a documented correction or deletion path.
RELATED CAPABILITIES
All scheduling featuresWhat to evaluate after relationship context
Questions about relationship context
Direct answers about what works today and what remains a documented requirement.
What is a scheduling contact?
The person behind repeat bookings, identified by a stable email address, together with their meeting history and any notes you record.
Why does the same person appear twice?
They booked with two different addresses. Match on a stable address and merge deliberately: matching by name is unreliable.
What should I write in a contact note?
Scheduling-relevant facts only: preferred times, access needs, agreed follow-up. Write nothing you would not be comfortable showing the contact.
How long should meeting history be kept?
As long as it serves a stated purpose, then delete it. Retention without a purpose is a liability rather than an asset.
Test relationship context in a real workflow
This page documents requirements. The working core to test now is a booking page or group poll.
Set it up step by step
The Help Center covers the exact task, how to verify it, and the failures specific to it: scheduling contacts and meeting history.
See it inside a real workflow
These teams rely on this capability, and each page maps the workflow, the metric that moves, and the mistake to avoid: Customer success scheduling software for every customer touchpoint.
Connect it to your stack
The connections most relevant here are Intercom. Each documents the data exchanged, the setup checks, and the limits — see the full integration directory for the rest.
For the wider picture, the scheduling overview shows where this fits, the Help Center explains specific tasks, and the free account guide explains what organizers can save and manage.
Evaluate relationship context with free scheduling
Create, save, share, and manage meetings with a free account and no credit card.
