Closed User Groups
History informs the decision. Current intent controls it.
For membership travel programs, loyalty programs, employee-benefit programs and other closed user groups.
Closed user groups know a lot about their members, and members expect to be known. But what a member booked before is not always what they want now. Past preferences are a hint. The trip in front of them is the instruction.
An example
What a traveler might say, and what Intentra is built to keep.
Reading history against current intent
Illustrative example and handoff, not output from a live partner deployment.
What Intentra could do here
A bounded application.
Treat member history as a hint and the current request as the instruction: keep the two apart, show which one drove a suggestion, and ask when they disagree.
Understand the present trip in the member’s own words, with history available as context only where the partner permits it.
What stays with you
Member identity, eligibility, benefits, inventory, pricing and transactions.
Current capability and design-partner work
One shared capability, five applications.
The shared capability is what works today. What this page describes for Closed User Groups is work we want to explore with design partners, not a proven product.
Working today
- Conversational traveler understanding in the controlled-access product
- Structured traveler and trip state
Proposed design-partner work
- Importing or combining permitted member history
- Applying eligibility or benefit rules
- Remembering preferences across sessions with the member’s consent
- Working with the partner’s approved inventory
FAQ
Common questions
Does Intentra use member history?
Does it know our benefits and rules?
Who holds member data?
Can it book or price a stay?
Design partners