A contact is the person behind repeat bookings, identified by a stable email, with their meeting history. It is a documented requirement on the contacts page. Keep notes short and purposeful; the privacy policy explains retention.
Before you start
- The participant's email address.
- A reason for any note you add.
- The right event type for the next invitation.
How to complete this task
- Search by the participant's stable email address.
- Review future and past meetings before adding context.
- Record only useful, appropriate notes with a clear retention purpose.
- Use the correct event type when inviting the contact again.
Finish by opening the public link in a signed-out browser: a saved setting is not proof that the guest path works.
Troubleshooting
The problems people report most often with this task, and the cause behind each one.
The same person appears twice.
Match on a stable email address. A personal address and a work address are two records unless you merge them deliberately.
Meeting history is missing.
History follows the address used at booking. If someone booked with a different address, the earlier meetings live on that record.
What should not be stored in a note?
Anything you would not show the contact. Keep notes to scheduling-relevant facts with a stated retention purpose.
Related Meetin.gs help
Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.
