Design-partner-stage product
Revoloyalty records voluntary membership, who invited whom, and enrollment benefits. It is testing whether coordinating that relationship with PMS-owned booking outcomes solves a frequent, costly problem for property managers.
These PMS products may already manage guest records, repeat bookings, coupons, booking sources, and reservation financials across direct, Airbnb, and Vrbo channels. The names above do not represent native Revoloyalty integrations.
Current versus proposed
Create branded membership cards, benefit catalogs, and referral links. This records participation, not PMS-verified bookings or revenue.
Reconcile selected membership or referral activity with operator-approved PMS evidence to test whether the connection is useful.
A future connection could use PMS booking and financial events to qualify referrals and calculate program results without replacing PMS functions.
The standalone workflow available today
Set up a branded membership card and describe program benefits.
Place the join link in a permitted first-party direct-guest touchpoint.
The guest chooses to scan, opt in, and join from the web—no app.
The member views benefits or shares a referral link inside Revoloyalty.
During a pilot, compare that activity with PMS records; Revoloyalty does not yet automate this step.
The boundary matters
The PMS may already identify the guest, code, completed booking, and value. Revoloyalty is testing whether operators still struggle to maintain the named advocate, referred member, two-sided benefit, cancellations, redemptions, and program economics. That pain and willingness to pay are not yet proven.
Your stack
PMS + channels
Membership + referrals
Revoloyalty
Clear boundaries
No. Your PMS continues to manage guest and reservation records, discounts, completed bookings, and financial reporting.
Probably. Many PMS products already track repeat guests, coupons, booking sources, and reservation value. Revoloyalty is testing only the remaining advocate, relationship, and reward-lifecycle coordination gap.
Not through a production PMS connection. Standalone reporting covers Revoloyalty participation. Booking verification, financial attribution, and incremental-lift reporting remain design-partner-stage work.
No. Your PMS or channel manager continues to manage listings and availability.
No. Consenting guests join and use their membership card in the browser through a permitted first-party link or QR placement.
Yes, but only to test voluntary enrollment, member participation, benefits, and member-to-member registration sharing. Do not treat that activity as a completed booking or revenue.
Yes for a meaningful revenue pilot. The initial customer profile is a professional operator with a transactional direct-booking path and lawful first-party access to guests.
No. Enrollment source and permission must be established separately; OTA-provided contact data must not be treated as a marketing list.
Help shape what connects next
Help determine whether managing guest advocates and reward obligations is a repeated, costly gap—or whether your existing stack already solves it well enough.