Integrations Dos and Don’ts
Last updated: October 6, 2022
The Integrations team is a sub-department of the Onboarding Department. We are a service that ensures proper placement and functionality of the FareHarbor booking software on client-owned websites.
We do our best to make sure every website we work on follows best practices and is optimized for conversions. Regardless, there are many common client requests that are beyond the scope of what the Integrations Team is responsible for. This document outlines the services we are able to provide vs those that we are not. Please use this document to vet out client requests before sending them to the integration team.
What we do
- Add or remove floating book buttons
- Add or remove static book buttons
- Add or remove embedded grids or embedded calendars.
- Add the FareHarbor Lightframe script.
- Removing contact forms or “Call To Book” text.
- Create clickable Book Banners at top of screen
- Only banners related to booking.
- Translate integration for sites in multiple languages
- While button text needs to be translated by an integrator. The Lightframe text will automatically choose a language based on the language settings in the customer’s browser.
- Please inform the client that forcing translations on booking links isn’t necessary, and only submit a request if they insist.
- Full reintegrations on client sites.
- We need to have all the information on where book buttons should go. Please get this info from the client before submitting to us.
- Remove old/external booking software
- Adjust location or presentation of book buttons
- Add book now links to existing content (like images, buttons, navigation, etc)*
- We are not able to integrate on other software, like Peek embeds or Godaddy products. These must be removed from the site.
- Relink existing integration of our software to new flows / items etc
- Update button verbiage (book now, rent now, get tickets etc.)
- Adding custom conversion pixels to the FareHarbor Dashboard
- Creating Mock integrations for our sales department to support the closing of higher tiered clients.
- Integrating ASN links on site
- links must be generated with correct tags by the channel support agent.
- Please provide the links and specific information on where they should be integrated.
- Add general Google Analytics tags to website
- This will be completed if the request comes from the AM. For any support requests through Zendesk, please ask them to have their web developer add them or loop in their AM.
What we don’t do
- Any work on Fareharbor Sites
- Sites requests always go to sites team.
- Check the bottom of the site for “Powered by FareHarbor”. This indicates a FareHarbor Site
- Add / remove / edit general site content – this is the responsibility of the clients web developer and includes:
- Site text and images
- Creating new pages
- Pricing updates
- FAQ information
- Social media integrations
- Integrating on client’s Facebook or Instagram
- Domain Migration – Moving a website onto or away from a certain URL
- Site formatting unrelated to integration
- Setting up redirects
- Fix broken site elements unrelated to integration
- Replicate an FH site setup
- This is a proprietary template that we are not able to recreate
- Integrate software other than Fareharbor on a site.
- Set up API connections. This should go to the connectivity team.
- Make calls to clients or email clients directly
- Due to team size, Integrations is a non client facing department. We can advise you on how to respond to the client.
- All client communication requests/escalations should go through account management.
- Edit book flows.
Why we won’t service certain requests
The main reason we cannot complete certain requests has to do with precedent. It is important for us to maintain strong boundaries when completing requests. If we were to complete site updates unrelated to integration for clients, it would set the precedent for that client that they can send their web development requests to us. If we complete small content requests, it will be harder to say no to larger requests. We are a small team and do not have the resources to provide general web development services to clients. There is no plan for this to change, and if a client wants our help with their websites, they must have a FareHarbor website.
We have a whole department for FareHarbor managed sites. If a client is interested in having us manage their site and site content, they may have the option to get on a FareHarbor site. Reach out to the clients AM if that is the case. If they want to continue managing their own site, the above list is what we are able to offer.
Escalations and Integration Questions
For client questions that are not actionable requests, please post in our Integrations room using the Support – Question workflow. Please do not forward these in Zendesk.
For escalated requests that must be completed quickly, follow the process to send in Zendesk and post in our Integrations room using the Submit an Escalation workflow.
Support Zendesk Process
Prior to submitting an integration request, please make sure to review the process for submitting an integration request outlined in the Support Triaging help page.
Login must be added to Keeper and verified before sending to integrations.
Integrators do not look through Close, read client emails, or move between tickets to get ticket details. You must completely fill out the macro and provide all request information in the integrators ticket. If there isn’t enough information provided, we will send it back to you for more details.