Shared Responsibility Model
Clear breakdown of client and Ripe responsibilities for successful partnership implementation and ongoing operations
Onboarding & Setup
Your role in launching our partnership for success
Website Implementation
Integration and optimization of booking paths
Community Partnerships
Local connections and affiliate integrations
Ongoing Success
Continuous collaboration and optimization
Onboarding & Setup
This phase is our launching pad for greatness! We want to be sure to provide your team with the tools to drive your destination and businesses forward. In order to make this work seamlessly, we need to have an open exchange of information.
Your responsibilities:
- Communicate your expectations for this partnership, the deliverables you expect and the timeline expected for success
- Provide the information needed in a timely manner so we can hit your targets. Ripe will provide you with an easy to use template that includes all of the information we need
Website Implementation
Prominent placement of booking path(s) and "why book here" communication. Website implementation is an ongoing art that requires vigilance and creativity.
Your responsibilities:
- Client provides the subdomain
- Make sure website implementation team is ready to turn on the booking engine within 2-4 weeks of delivery
- Provide easy to see and strong call to action including a landing page with clearly stated "Why Book Here"
- Easy to locate Booking Button or Date Picker
- Use "Deeplinks" to guide travelers to the most effective search path based on their site behavior
- Connect your Main site GA4 account to their Ripe Sub-Domain GA4 account for reporting purposes
- Allow us access you website development team to troubleshoot search if issues arise during implementation or new feature releases
- The Client (DMO) owns the Sub-domain. Any traffic that comes to the sub-domain is their traffic and is additive to their main site traffic. This is important to maintain security/PCI compliance as we pass payment details to lodging suppliers
Community Partnerships
Like events and microsite affiliates. The most successful clients have integrated our booking engine in many ways within the community.
Your responsibilities:
- Connect our booking engine to overnight demand drivers, both on the DMO site AND on the event site
- Highlight local attractions through value added promotions
- Connect us with local hotels and lodging partners to help them connect is the most productive and cost effective way possible
Marketing & Promotion
Promotion of the service. Drive traffic to your booking engine. Use the tried and true messaging to drive business to your site and make sure that the call to action includes a lodging push.
Your responsibilities:
- Provide engaging promotions and/or Value Adds to give travelers a reason to book on your site
- Procure Value adds and provide deposit if Ripe is to operate fulfillment
Ongoing Success Management
Attend meetings and work with Client Success Manager. Stay connected with your Client Success Managers for the latest opportunities and best practices.
Your responsibilities:
- Regularly scheduled meetings to discuss progress and innovation
Lodging Supply Management
Introductions and communication needs. Keep your lodging partners happy and engaged.
Your responsibilities:
- Provide lodging supplier contact details
- Arrange for a lodging supplier webinar so Ripe can present our offerings to your lodging stakeholders and help them to understand how to best work with us and optimize their listing
- Assist in hotel communications if they become unresponsive for service needs or commission payments
User Access & Account Security
Clients are responsible for managing and securing all user-level access to their Ripe account.
Your responsibilities:
- Assign user access based on role and least-privilege principles
- Regularly review and update user permissions
- Immediately revoke access when roles change or relationships end
- Oversee third-party users (developers, agencies, partners) and ensure compliance with Ripe’s Terms of Service
- Use named user accounts and avoid shared logins
Updated about 10 hours ago