> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/integrations-overview/sevenrooms-setup.md). # SevenRooms — Operator Manual > **Walkthrough (Peoplevine × SevenRooms):** [Watch here](https://www.loom.com/share/1f31bae7dad9436fb1a805510899be15) ### Before you begin (Prerequisites) * **Peoplevine permissions**: You must be an **Administrator** or **Supervisor** to configure integration settings in the Control Panel. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md). * **SevenRooms account** with API access enabled. * **Venue group level credentials** from your SevenRooms account manager: Client ID, Client Secret, Default Venue ID, and Venue Group ID. These must be venue group level — venue level credentials will not work. * **SevenRooms webhooks configured** — required for two-way sync. Submit the webhook request form at [peoplevine.com/sevenrooms/webhooks](https://www.peoplevine.com/sevenrooms/webhooks) and configure webhooks for **Reservation** and **Client** entities. Point webhooks to the correct Peoplevine region endpoint: * Region 1 (US): `https://api.peoplevine.com/sevenrooms` * Region 2 (UK/EU): `https://api.peoplevine.co.uk/sevenrooms` > Without webhooks configured, only Peoplevine → SevenRooms sync is active. Reservations made in SevenRooms (phone, widget, walk-in) will NOT appear in Peoplevine. > For full setup instructions including SevenRooms-side configuration, access rules, and field mapping details, see [Connect SevenRooms and Peoplevine](https://docs.peoplevine.com/peoplevine-docs/peoplevine-connect) in Peoplevine Connect. *** ### Setup The steps below cover the Peoplevine Control Panel side only. For SevenRooms-side configuration (access rules, tag mapping, walk-in setup), see the Connect guide linked above. 1. Navigate to [**AUTOMATE > Integrated Platforms**](https://control.peoplevine.com/admin_authenticate.aspx). 2. Select **SevenRooms**. 3. Choose the environment: **Production** (live) or **Demo** (QA/testing). 4. In **Associate with Location**, select the Peoplevine directory location for this connection. 5. Enter the **Client ID** and **Client Secret** from your SevenRooms account manager. 6. Configure the integration options: | Option | What It Does | | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Send confirmation and cancellation emails through SevenRooms** | If enabled, review Peoplevine-triggered notifications to avoid sending duplicate emails to members | | **Only sync member reservations** | When ON, ignores non-member data from SevenRooms | | **Sync POS data/orders when a reservation is marked closed** | Requires a SevenRooms POS integration — ask SevenRooms Support | | **If a member doesn't have a reservation, add them as a walk-in** | When ON, checking in a member with no reservation in the next 2 hours creates a 1-person walk-in in SevenRooms. Requires SevenRooms walk-in configuration (see Walk-In section below) | | **Bypass settings and allow multiple simultaneous reservations** | Enables duplicate bookings even if SevenRooms blocks them | | **Sync profile photos** | Sends member profile photos to SevenRooms for front-of-house recognition | | **Automatically setup Dining Schedulers** | Creates schedulers in Peoplevine from SevenRooms dining areas | 7. Paste the **Default Venue ID** and **Venue Group ID**. 8. In **Extended Attributes to Sync with Contact Tags**, list additional attributes to sync. Defaults already supported: Dietary Restrictions, VIP client type, Client Type, Special Attention, Profession, Seating Preference, Champagne, Spirits, Water, Wine. 9. **Custom Groups to Sync (Indexed)**: up to 5. Titles must match SevenRooms exactly. 10. **Custom Fields to Sync (Non-Indexed)**: up to 10. Titles must match SevenRooms exactly. 11. Optional: **Do not sync Membership to Loyalty ID / Loyalty Tier** — use this when those fields are owned by another system. You can still pass membership data via custom attributes (`{@membership_tier@}`, `{@membership_id@}`). 12. Click **CONNECT**. > **Important — Global Tags required:** All new SevenRooms tag categories used with Peoplevine **must be created as Global Tags** in SevenRooms (Settings > Client Tags > set the category to **Global**). Local tags will not sync. The category name and values must match exactly between SevenRooms and Peoplevine. To trigger a tag onto an existing member: assign the tag/attribute on the Peoplevine CRM profile, then push the profile to SevenRooms (open the CRM profile and click **Sync** for SevenRooms). The tag appears on the SevenRooms profile after the sync runs. *** ### Day-to-Day: Front of House #### What hosts see in the SevenRooms guest card When a member syncs from Peoplevine to SevenRooms, the following data is available on the SevenRooms guest card: * Membership tier (via Loyalty Tier field) and Membership ID (via Loyalty ID field) * Profile photo (if "Sync profile photos" is enabled) * Synced attributes and tags: dietary restrictions, VIP client type, seating preference, and other configured attributes * F\&B Customer Notes (synced to Customer Notes on Booking in SevenRooms) #### Check-in behaviour When a member checks in via Peoplevine (check-in app or web): * **Has a reservation in the next 2 hours** → SevenRooms sets the reservation to **Partially Pre-Arrived** * **No reservation** → Peoplevine creates a **1-person walk-in reservation** in SevenRooms (if the walk-in option is enabled) **Walk-in prerequisites (all must be configured):** Peoplevine side: 1. Configure a **Business Location** representing the check-in area 2. Enable the walk-in option in the SevenRooms integration settings 3. Assign that Business Location to the target **Dining Scheduler** 4. Check-in app (iPad or web) must be set to the **same location** (Settings > General tab) SevenRooms side: * Blanket availability rule (open to close) * Pacing at 15 minutes * Enough ghost tables to assign walk-in members to * Availability set to **Peoplevine** * Must allow booking up to the current time #### Member booking via portal When dining schedulers are configured, members can see real-time availability and create or cancel reservations from the Member Portal. Reservations sync to SevenRooms in real time (requires webhooks). #### What staff should know * **Only Active members sync** to SevenRooms. Cancelled members show "Not a Member" in the Loyalty ID field. * **VIP syncs via CRM Attribute** — the VIP star icon on the Peoplevine profile does NOT sync. Only the VIP client type attribute syncs. See: [How to Map Form Fields to CRM Profile or Attribute Group](/products/control-panel-overview/forms-overview/map-form-fields.md) for attribute setup. * **Tags synced from SevenRooms persist** — tags like "it's been a while" are stored as attributes on the Peoplevine CRM profile. They do not auto-remove and must be manually cleared if no longer relevant. *** ### What Gets Synced | Data | Direction | Timing | | -------------------------------------------------------------- | ----------------------- | ----------------------------- | | Member profiles (name, email, phone, address, company, gender) | Peoplevine → SevenRooms | On creation + updates | | Membership status changes | Peoplevine → SevenRooms | Real-time | | Membership tier + ID | Peoplevine → SevenRooms | Via Loyalty ID/Tier fields | | Birthday (month and day only) | Peoplevine → SevenRooms | On sync | | Anniversary | Peoplevine → SevenRooms | On sync | | Profile photo | Peoplevine → SevenRooms | On sync (if enabled) | | Attributes (dietary, VIP, seating, etc.) | Peoplevine → SevenRooms | On sync | | F\&B Customer Notes | Peoplevine → SevenRooms | On sync | | Reservations | Both directions | Real-time (requires webhooks) | | Tags | SevenRooms → Peoplevine | Optional (two-way CRM sync) | | Check-in / arrival status | Peoplevine → SevenRooms | On check-in | **Member matching logic** — when syncing, Peoplevine checks if the member exists in SevenRooms in this order: 1. SevenRooms ID already on the Peoplevine profile 2. Loyalty ID matches Membership ID 3. Email address 4. Mobile number 5. External ID (`cus-{customer_no}`) If no match is found, Peoplevine creates a new record in SevenRooms and links it to the member. > **Duplicate emails in SevenRooms:** if several SevenRooms profiles share the same email address, matching by email uses the **first** one. Reservations made from the other duplicate profiles add additional SevenRooms IDs to the **same** member in Peoplevine. > **Marketing consent is not shared with SevenRooms.** Email and SMS marketing opt-in/opt-out is managed exclusively in Peoplevine and is no longer shared with external reservation systems. *** ### Troubleshooting **Members not appearing in SevenRooms:** Verify credentials are correct (all 4 fields: Client ID, Client Secret, Default Venue ID, Venue Group ID). Ensure you requested venue group level credentials, not venue level. Try disconnecting and reconnecting to trigger a fresh sync. **Reservations from SevenRooms not appearing in Peoplevine:** Webhooks are not configured. Submit the [webhook request form](https://www.peoplevine.com/sevenrooms/webhooks) and configure for Reservation and Client entities. See Prerequisites above. **Walk-in not created when member checks in:** 1. Verify check-in app location matches the Dining Scheduler's business location. 2. Check if SevenRooms is overbooked. 3. Verify there is enough capacity (ghost tables, pacing). 4. If the member has a reservation in the next 2 hours, the system sets it to Partially Pre-Arrived instead — this is expected behaviour, not a failure. **Check-in reporting shows blank location for "Arrived" scan type:** Known bug. Check-ins auto-created by the SevenRooms integration do not populate the location field. Manual check-in app scans (scan type "user") include location data. The `scan_notes` field will contain "Arrived for reservation via" for SevenRooms-generated check-ins. **Availability slots not appearing in Member Portal:** Ensure the Audience setting in the SevenRooms Access Rule is set to **Peoplevine** (not the Reservation Widget). **Member cannot modify an existing reservation in the portal:** The SevenRooms API only supports booking and cancellation — not modification. To change a reservation (e.g., add guests or change time), cancel the existing reservation and rebook. If the reservation has a price, any financial adjustment must be handled manually in Peoplevine: issue a partial refund for a lower price, or create a new charge for the difference if higher. **Can I charge a no-show or cancellation fee through the integration?** Not automatically. SevenRooms cannot trigger a no-show or cancellation fee charge into Peoplevine — it only processes payments through the payment processor natively integrated with SevenRooms. If your payment processing lives in Peoplevine, no-show and cancellation fees must be charged manually on the member's Peoplevine profile. To guarantee a no-show fee without manual collection, configure the reservation as a pre-paid booking in SevenRooms — the member is charged at the time of booking and refunded if they cancel within the policy window. If they don't show, the pre-booking charge stands as the fee. This requires SevenRooms itself to be set up to take payments. *** ### Best Practice * **Start with "Only sync members" ON** — get the integration working with your member base first. Turning it off pulls all SevenRooms guest data and will slow your CRM. *(Connect guide)* * **Coordinate email notifications early** — decide whether SevenRooms or Peoplevine sends reservation confirmations. Both systems sending creates duplicates. *(Connect guide)* * **Match scheduler cancellation settings exactly** — the Peoplevine scheduler's "Limit cancellations to *n* minute(s) before the appointment" must exactly match the SevenRooms shift setting for "Customer can modify/cancel" under Settings > Shifts > Edit Shift > Payment & Policy. *(Connect guide)* * **Test with a single member first** — sync one member and verify their data appears correctly in SevenRooms before syncing all. *(Connect guide)* * For multi-concept venues (main restaurant, rooftop bar, private dining), use the **Access Rules** feature in SevenRooms to restrict availability by membership tier. See the Connect guide for details. *(Connect guide)* * **If you need to enforce a no-show or cancellation fee**, configure the reservation as a pre-paid booking in SevenRooms rather than relying on a separate no-show fee. The fee does not flow from SevenRooms into Peoplevine — pre-payment is the only way to secure the charge without manual collection. *Last updated: 2026-05-24* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/integrations-overview/sevenrooms-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.