Onboarding Dashboard Checks

Pre-Training

• Steps for OB Builder (All Tiers)
  • Complete the Dashboard Specialist Self-Check (Custom Activity) at least 2+ hours prior to initial training of the dashboard.

Post-Training (Tier 2+)

• A Dashboard Checks Requested (Custom Activity) will be submitted by the OB Trainer along with an integration workflow in the #checks_dash Slack channel
  • *A check requested may potentially appear for a dashboard that is lower than a Tier 2. Everything is still the same process that follows below.
• Steps for OB Builders:
  • Another Builder who is a part of the @noram-checks Slack tag and not the original OB 02 for the lead being checked, will claim the dashboard check via the Slack thread in #checks-dash (or occasionally #checks_fhs) within 24-hours of it being posted
    • Things you should be checking for:
      • NORAM Checklist
    • Once the check is complete, submit the Dashboard Checks Completed (Custom Activity)
      • Task the OB 02 on the lead with “Checks Notes” if any are applicable
  • Notify and tag the OB 02 Builder for that lead in the corresponding thread in #checks_dash
    • (Example) “@builder checks are completed, notes are in Close/this thread. Some important issues that I found were [insert issues]
    • The OB 02 for that lead has 24 hours from the thread being posted in #checks-dash to complete any outstanding issues
      • Once they are completed, please communicate in the corresponding Slack thread in #checks_dash
• What if I selected “No – This dash has significant updates or missing information?”
  • Please address issues in the Slack channel or thread

Pre-Training

• Complete the Dashboard Specialist Self-Check (Close Custom Activity) at least 2+ hours prior to initial training of the dashboard, using our Self QC Checklist.
• Post “Dashboard Specialist Self Check competed” on the company slack channel.

Post-Training (Tier 1+, T0s for specific setups)

A Dashboard Checks Requested (Custom Activity) will be submitted by the OB Trainer.

• All the requests will populate on the OB Checks Queue, and should be claimed by a team member before EOD. To claim, create the Dashboard Checks Completed (for New Client) (Close Custom Activity), and update a field of the form to save the activity in draft.
• All dashboard checks should be completed by EOD on the next day, using the Dashboard QC Checklist.
• After checks are completed, the builder checking the dashboard should post in the company channel for better visibility.
  • If there are no escalations/emergencies from the checks: @trainer @builder Checks are completed, notes are in Close
  • If “No – This dash has significant updates or missing information” was selected on the custom activity: @trainer @builder Checks are completed, notes are in Close. One important thing to look at asap: [insert issue]
• The original dashboard builder should address the checks and make the necessary updates within 24 hours, and post in the slack channel & Close for visibility.

Pre-Training

• Steps for OB Trainer (All Tiers)
  • The Onboard Specialist Self-Checks Completed custom activity should be completed by all Trainers for all Tiers at least 2 hours prior to the training date/time.
  • Trainer will review the following listed within the custom activity:
    • Front End Test Bookings Made: You will complete and test out the booking process from a customers view to ensure no issues come up.
    • Calendars & Flows Reviewed: Double check that there are some calendars are built out and the views are relevant. Additionally, review Booking Flows so that there is at least a default built out.
    • Markdown Correct: Trainers are to quickly sweep to item listings to make sure nothing is sticking out and/or markdown is incorrect.
    • Is This Dashboard Ready to Go Live: Based on notes in the lead and slack channel, do you believe the dashboard is ready to go live
  • Communicate in lead Slack Channel once you have completed your checks.
  • If anything is unclear and/or concerning during the checks process, please communicate with the appropriate teams within the lead slack channel.

Post-Training

• For any Tier 2+ in NORAM & Tier 1+ in EUROPE, Trainers are required to submit a Dashboard Checks Requested (for New Client) custom activity once the dashboard is ready to Go Live.
  • Trainer will need to be specific since it is an open ended text input field labeled Does Anything Need Specific Attention?
  • Trainers can request for the whole dashboard to be reviewed, however if there are advanced features enabled such as price schedules, seat maps, complex resource setup, etc. note those for Builders to review.
• For any Tier 0’s & 1’s in NORAM, Trainer can request a dashboard checks, however they have to meet one of the following criteria:
  • 5+ Updates have been completed since initial Training Date
  • 3+ Weeks since Training Date
  • 10+ Items on Dashboard
• For any Tier 0’s in EUROPE, there is no criteria, however there has to be a reason behind this request like complex setup or number of items. Trainer must still be very specific on what they would like Builder to check.
• Once both the Client and Trainer have agreed on a set Go Live date, you are clear to submit to Integrations and/or send off codes for the client to integrate.
  • Please note, if you are submitting for integrations or sending off codes, you are aware that the dashboard is in good standing.
• When the custom activity has been submitted you are clear to call the dashboard Live. Builder will have 24 hours to complete the checks.
• Additionally, use your best judgment before submitting to integrations or calling something Live knowingly that something isn’t right.

Integration checks are being split up between the Integrator who completed the integration and the onboarding specialist who submitted the integration. The integrator will use a proprietary tool to sweep the site, ensuring that no booking software other than Fareharbor is on the site. The trainer will then go in and manually check the site for presentation issues, call to book text, or other best practice opportunities.

• Steps for Integrator

  • Once the initial integration is completed, enter the site into FareHarbor’s proprietary site sweeping tool ton confirm:
    • The correct dashboard is present on the site
    • No other dashboard or 3rd party software is present on the site.
  • If the tool leads to errors, use screaming frog instead.
  • Post the site to #checks_dash, leaving notes for the trainer about where the site was integrated and any limitations to the integration.

• Steps for Trainer

  • Open the website in an incognito tab.
  • Using the notes from integrator and the integration checklist as reference, sweep through the main pages of the site, looking for any incorrect links or opportunities to better follow best practice
  • Areas on the site to check:
    • Home page
    • Header
    • Footer
    • Item Pages
    • Calendar Page
    • Contact Page
  • Other pages irrelevant to booking can be ignored as the integrator has already confirmed old software is not hidden on the site.
  • Make sure to check the site on mobile as well.
  • Once the site has been swept, fill out the integration checklist as a comment in the #checks_dash thread.

Integration Checklist:

• CTA  button  above  the  fold, stands out
• Does  website  lightframe?
• Booking links lead to correct items
• Mobile  integration
• Phone numbers / Call to book text removed (if able):
• Integrated  on  all  languages  (if applicable):