Overview

Below you will find detailed descriptions of the information we require and why. For any questions, please contact [email protected]. We value your feedback and partnership and are looking forward to supporting your integration.

Jump to

Staffing and Contact Information

This section allows us to know who to contact at your company regarding the integration, and who comprises our shared team.

• Product Lead Name, Email Address, (Phone Number optional)
• Engineering Lead Name, Email Address, (Phone Number optional)
• Marketing Lead Name, Email Address, (Phone Number optional)
• Sales Lead Name, Email Address, (Phone Number optional)
• Customer Support Lead Name, Email Address, (Phone Number optional)

Technical Review

Video demonstration of the integration

This demo should be 3-5 minutes long and clarify how the integration works. The primary audience is to help enable our GTM and Customer Support teams. While the primary purpose of this video will be for Hover's internal reference, please indicate whether or not this video is able to be used for customer facing purposes. If public, Hover may incorporate content in sales, support, and help center collateral.

List of all endpoints used within the integration

Developers should a comprehensive list of all endpoints used to build an integrations. The primary purpose is to give users and various Hover support resources an idea of the resources and products the integration interacts with.

Brand and Product Marketing Review

Public-facing collateral

Please submit any collateral or information you plan to share with customers about the integration (e.g. support articles, sales materials, setup instructions, landing pages). Hover's Integration Review team will review all collateral to ensure that any of the information accurately portrays Hover's brand and product functionality.

Integration prerequisites

If there are any prerequisites, access controls, required subscriptions, or other barriers to entry for anyone to install and/or use the integration, please provide a detailed list for the Hover Integration Review team.

Customer Support, Technical Support, and Product Feedback Review

Description of support organization structure and size

Hover needs to ensure that any external support organization is equipped to process questions and escalate technical problems to an internal product owner. This will be listed in our public help center.

Escalation paths for customer support and technical support with expected response times

We require a direct channel of communication from the Hover support team to a third party's support organization, as well as a direct line of communication to the technical product owner of the integration. Hover also requires a Service Level Agreement (SLA) for expected response time.

Escalation path for product feedback

We require a direct channel of communication between the Hover Partnership team and the product/engineering team(s) responsible for receiving integration feedback from mutual customers. Hover has no explicit requirements for expectations for applying customer feedback.

Access to a working demo account

Hover requires access to an instance of your software program for testing, troubleshooting, and demoing the integration when applicable.

Testing before Launch

Before an integration is released two conditions must be met

1. This Third Party Integration Information form is submitted, and all fields have been reviewed and accepted by Hover's Integration Review Board.
2. Your team has provided all necessary accounts for Hover to test end-to-end at least 10 days before desired launch.

Release and Launch Schedule

1. Anticipated release date
2. Notification of go live date two weeks in advance of initial release to customers
3. Notification that integration has been pushed live (on date of release to customers)

Submitting Your Required Information

Submit your Hover marketplace requirements here.