OpenTable Onboarding Overview

Updated

Prepare

  1. OpenTable integrates directly into Tabit PAD, so need to confirm that customer is not using TG or any other Table Management app (Resy, Sevenrooms, etc.)
  2. Ensure that all tables in OpenTable are aligned with tables on the PAD (Tabit maps)
    1. If site previously was setup with TG, MUST ensure that the TG map has all the table aligned to the OT maps (multiple maps at bottom Right corner of OT app)
    2. NOTE! Any new tables added to OpenTable (post deployment) will need to align to ROS and be added to OFC/PADs
  3. Gather OpenTable credentials from manager to ensure that we can review their ability to access the Integration menu within OT
    1. Ensure that manager also has valid login credentials to Tabit Office (and pls test them), as the onboarding will ask them to login to Tabit and associate the OT site/instance (referred to as RID: Restaurant ID) to the relevant Tabit site

 

Onboard/Enable

  1. Login to the OpenTable app a. Onboarding can be performed from either OT tablet app or web interface (https://guestcenter.opentable.com/)
    1. Confirm you have all valid credentials – as per above
  2. Navigate to Integrations menu in OT
  3. Select Tabit, and follow prompts
  4. Enter Tabit Office login credentials
  5. Associate sites between the 2 systems (Tabit sites listed on the Left, and OT instance on Right)
    1. Note that pending user accessibility in Tabit, they may display several sites including HQ site

  6. You’re all set!

     

Train

  1. Once the systems are integrated, any party that is sat from OT will appear on PAD (Purple table)
    1. Any notes/tags captured in OT will also appear on the PAD
  2. Tabit updates OT with course and tables status, so Hostess can see these updates automatically
    1. Courses/statuses: Appetizers, Entrees/Mains, Desserts, and Paid
    2. Hostess can also drill down to ticket level details of any table/order 
      (Note: This features updates well on OT Tablet app – with only minimal delays, but is inconsistent if/when using web browser)
  3. As we currently CANNOT update OT with closed check indication, the Hostess will still need to mark tables as status = “Finished”
  4. Important to train server to close check/orders as soon as customer walks away, so that the table is available for the next party to be sat
    1. While there is no limitation on Hostess being able to sit the next party (if table is available) it will not sync to the PAD in a timely fashion (as the PAD already has an open order on that table)
    2. We do “save” this indication for up to 30 min, and update the Table with the new party details once they close the previous check, but that will not indicate to server that new party has been sat with the relevant details
    3. If/when such conflict occurs any merging of tables will not occur in retrospect
      1. example: OT sat a party at tables 30+31+32. Normally if all tables are available, they will be merged on PAD automatically, but if PAD has a check open on table 32, only tables 30+31 will be merged.
      2. Server can still service the party as needed; they will simply not see table 32 merged on the PAD
  5. Remember: Regardless of any issues that may arise or failures to sync seated party and course data, the server can ALWAYS continue to operate the PAD without any restrictions whatsoever

Related articles