Tock partners with Tripleseat to offer a real-time, one-way integration that brings Tripleseat Events into Tock as reservations. To learn more, visit Tripleseat Events Integration Overview.
FAQ
How does the integration work?
Tripleseat Events with a Tentative or Definite status are brought into Tock as reservations under the dedicated Tripleseat Events Reservation Experience (TPLST), which is auto-created on Tock at the time of integration connection.
Any subsequent edits to the Tripleseat booking will pull into Tock and update the associated reservation.
What Tripleseat event information is included in the auto-created Tock reservation?
- Event date
- Event timing
- The Tock reservation will match Tripleseat Event start time, unless a setup time is included in the event. In this case, the Tock reservation will start at the setup time.
- The Tock reservation end time will match Tripleseat Event end time, unless a teardown time is included in the event. In this case, the Tock reservation will end at the conclusion of the teardown time.
- Event contact name as Tock guest name
- If a guest with a matching email address already exists in Tock, the auto-created reservation will be associated with that guest.
- If there is no matching guest, a new Tock guest profile will be created.
- Event guest count as Tock party size
- As a Tock visit note:
- Event name
- Event status
- Event room(s)
- Event start
- Event end
- Setup start
- Teardown end
How do Tock reservation table assignments for Tripleseat events work?
- As part of the integration configuration settings, Tripleseat rooms can be mapped to Tock tables. All unarchived Tock tables will be included in the mapping list options. Mapping is not tied to a specific Availability Planning Schedule.
- If a regular reservation is already assigned to a mapped table matching the assigned room on a Tripleseat event, the event reservation will still be assigned to that table, causing an overbooking.
- The set integration contact will receive an email notification, and the overbooking will be visually displayed on the Dashboard Timeline. We recommend manually reassigning the regular reservation to an alternate table.
- All Tripleseat event reservations are automatically pinned to their assigned tables, meaning that a Schedule republish will not reshuffle these bookings. Regular reservations may be manually moved to alternate tables if they are assigned to the same tables as an event booking.
- Mapping can be updated at any time, and will go into effect immediately for all new Tripleseat events coming into Tock. Existing future reservations will not auto-update Tock table assignments, unless Tripleseat events are reimported to Tock via the integration. From the Dashboard Integrations page, select the integration, then click "import future events."
- If one or more mapped tables no longer exist in Tock, the Tripleseat event assignment will be affected as follows:
- If some of the mapped tables for the room exist on Tock, a reservation is assigned to those tables.
- If none of the mapped tables for the room exist, or the room was never mapped on Tock, the reservation is placed in the Unassigned section of the Timeline.
- For Blueprint Reservation management, Tripleseat events will create new slots in the timeline.
- Events will be auto-assigned to tables in service based on the Dashboard floor plan and the optional table mapping that is configured when setting up the integration.
What happens if the Tripleseat event is marked as “Lost”?
The associated Tock reservation will be canceled. Once canceled in Tock, changing the event back to Tentative or Definite will not update the associated reservation.
If the event is reinstated, we recommend creating a new event in Tripleseat to see that linked booking created within Tock.
What happens if a Tripleseat event is created outside normal service hours or far into the future?
- If a Tripleseat event is booked before or after the date’s set service start or end time, the associated reservation will still be created and displayed on the Tock Dashboard. The assigned table based on integration room mapping will also be reflected on the booking.
- If a Tripleseat event is booked far into the future, on a date where no Tock inventory or tables yet exist, an unassigned booking will be created. Manual table assignment or integration resync will be necessary once Tock tables have been created on that date. Resync function coming soon.
How can a Tripleseat event reservation within Tock be edited?
- Tripleseat event reservations in Tock can be edited in the following ways:
- Add or update notes (guest, visit, etc.).
- Switch the toggle to include or exclude a booking from pacing.
- Update table assignment, party status and all seating actions
- Updating guest information, reschedule and cancel actions should be made within Tripleseat rather than Tock.
- No guest communication or payments are automated for or can be manually triggered from the Tock Dashboard for Tripleseat event bookings.
How does pacing work for Tock Tripleseat event reservations?
- By default, all Tripleseat event reservations within Tock will be included in pacing, which could impact online reservation availability. However, an incoming Tripleseat event booking will never be denied due to set pacing restrictions.
- If a Tripleseat event includes setup time, pacing will be impacted at the setup time, rather than the event start time.
- To update an individual event booking, navigate to either the Timeline or Service tab on the Tock Dashboard, then switch the toggle to include or exclude the booking from pacing.
How can Tock private dining requests be brought into Tripleseat as a lead?
Activate Tock’s separate Tripleseat Leads integration. View this article to learn more.
Learn More
To learn more, view these articles: