Internal customer notes

A free-text field per customer that only your team sees and is never sent to the end customer.

What they're for

The automatic timeline (reservations, marketing events) doesn't capture human context. Internal notes do:

• "VIP - seat at table 12 if free."
• "Allergic to tree nuts. Always alert the kitchen."
• "Speaks French only, translate the menu."
• "Birthday is February 14th."
• "Journalist - careful with the experience."

Where they appear

In the customer's individual card, below the identities block, before reservations:

+- 📝 Internal notes ------------------+
|  VIP, allergic to tree nuts.         |
|  Always asks for table 12 if free.   |
|                                       |
|  Team-only. 78/2000                   |
|                          [Save]       |
+--------------------------------------+

Features

• Up to 2000 characters.
• Private: never sent to the customer, in emails, or in confirmations.
• Permissions: any workspace member (owner, admin, staff) can read and edit.
• Audit: changes are recorded with timestamp and author.
• Persistence: saved when you click "Save". The button is disabled if there are no changes.

Typical use case

A customer calls to reserve and mentions they're allergic to shellfish. The host:

1. Creates the reservation.
2. Opens the customer card.
3. Adds in notes: "Shellfish allergy - always alert the kitchen".
4. Saves.

Next reservation, any team member sees the note when opening the card and can act accordingly (alert the kitchen, suggest safe dishes, etc.).

Best practices

• Be specific: "Allergic to tree nuts" > "Has allergies".
• Tag with prefixes: [VIP], [Allergy], [Preferences] for quick scanning.
• Delete stale info: if something changes (no longer gluten-free since October), update.
• Don't store unnecessary sensitive data: notes are private but follow GDPR's minimization principle.
• Review before service: in peak hours, opening a VIP's card gives context that improves the experience.