dailypoint, the guest data and CRM platform used by more than 1,500 hotels, will route new connections to hotel systems through Hapi instead of building each one itself. The two companies announced the partnership on November 12. For hotel groups that run dailypoint, the change adds a second vendor to the path their guest data takes from the property management system, point of sale and booking tools into the CRM.
What dailypoint announced
According to dailypoint’s announcement, it will use Hapi as a centralized integration layer that complements its existing integrations. Through Hapi Connectivity and Hapi’s certified SevenRooms integration, dailypoint gains real-time guest data from additional hotel systems, and the companies name point of sale, spa, and sales and catering platforms as possible next connections. The stated goal is to cut the engineering work of building and maintaining each connection so dailypoint’s team can spend that time on product.
dailypoint founder and CEO Dr. Michael Toedt said the partnership “gives us a way to expand connectivity and bring hotels online faster, while continuing to develop new capabilities that help our customers make better use of their guest data.” Hapi CEO Jeff Bzdawka said “the hotel technology industry has spent years building the same integrations over and over again,” and that “connectivity should be something technology providers can build on, not something they have to keep rebuilding.”
Advertisement
The release states the scale of both businesses. dailypoint says it collects guest data from more than 200 systems, including PMS, POS, booking engines, Wi-Fi and marketing platforms, and is the preferred CRM partner of The Leading Hotels of the World. Hapi says it serves more than 15,000 hotels, including IHG Hotels & Resorts, Wyndham Hotels & Resorts, Hyatt, Sonesta and Rosewood, and offers read and write access across PMS, CRM and POS systems through a single connection.
The count the release leaves open
The published release gives the number of additional hotel systems dailypoint can now reach as “XX”, a placeholder rather than a figure. It also does not list which systems dailypoint will reach through Hapi beyond SevenRooms, or the timing for the POS, spa and catering connections it mentions. A hotel deciding whether this partnership changes anything for its own stack needs that list, and dailypoint’s account team is the place to get it in writing.
Hapi’s pattern with other vendors
dailypoint is the latest hotel technology vendor to hand part of its integration work to Hapi. When Stayntouch connected its cloud PMS to Hapi, the companies said hoteliers and technology providers could reach Stayntouch and more than 100 other providers by writing to a single Hapi API. In September, Hapi and Upgrade announced an automation for Upgrade’s Flex Pay buy now, pay later product, which Hapi said was already deployed across thousands of hotels and moves payment information between the reservation system, PMS and reconciliation workflows without custom integrations.
dailypoint has been widening its own reach at the same time. In June it added Model Context Protocol support and a Zapier integration, which it said connects its platform to more than 9,000 apps and lets hotel teams query guest data from AI assistants such as ChatGPT, Claude and Gemini. Toedt said then that connections which once took “months or even years of interface development can now be done by our customers within minutes.”
Put together, the CRM now has three kinds of connection to a hotel’s systems: the integrations dailypoint built and maintains itself, connections that run through Hapi, and customer-built links through Zapier or MCP. Each has a different owner when something breaks.
Why middleware matters to the buyer
A guest profile is only as current as its slowest feed. If a reservation, a restaurant check or a loyalty status update stops arriving, the CRM still sends the pre-arrival email, the upsell offer or the VIP alert, built on stale data. With a direct integration, the CRM vendor owns that failure. With a middleware layer, the hotel may have three parties to call: the source system, Hapi and dailypoint. Neither release describes how support is split between dailypoint and Hapi when a feed fails.
The data protection position changes too. dailypoint describes its central profile as GDPR and CCPA compliant. A hotel group in the UK or EU that adds a connection through Hapi is adding a party that handles guest personal data on the way in, which its data protection team will want named in the processor list. Guest data rules are already shifting under hotels from other directions, as when Booking.com stopped sending guest phone numbers to hotel systems.
The vendor side of the argument is cost. Bzdawka’s point is that every CRM, messaging and upsell vendor building its own PMS connections spends engineering on the same work. If dailypoint spends less on connectors, the release says, it spends more on features its customers use. Operators can test that claim at renewal by asking what shipped.
What it means for operators
Three groups of buyers should pay attention. CRM and loyalty leads at hotel groups running dailypoint now have a route to systems dailypoint did not connect to before, starting with SevenRooms restaurant and reservation data. IT and integration managers inherit a second vendor in the data path. Independent hotels in the Leading Hotels of the World network, where dailypoint is the preferred CRM partner, may find that systems they were told were unsupported become available through Hapi.
Groups that already use Hapi, which the release says serves IHG, Wyndham and Hyatt among others, should ask whether a dailypoint connection through Hapi uses their existing Hapi feeds or a separate one. That decides whether the same reservation reaches the CRM once or twice, and who is billed for it. Groups standardizing vendors across a portfolio, such as members of Preferred Hotels & Resorts after its Mews alliance deal, face the same question with every system that offers both a direct and a Hapi route.
What to ask before the next renewal
Ask dailypoint for the list of systems it reaches through Hapi today, with dates for the POS, spa and sales and catering connections the release names. Ask which of your current connections, if any, will move from a direct integration to Hapi, and whether you can keep the direct one.
Ask for the support terms in writing: who you call when a feed stops, the response time, and how a missing reservation or check is reconciled. Ask whether the Hapi connection is read only or also writes back to your PMS or POS, since Hapi offers both.
Ask who pays for the Hapi layer and whether the cost appears in your dailypoint contract. Then have your data protection lead add Hapi to the processor record for any connection that runs through it.
Source: dailypoint
