Partner Journey¶
Traveln partnerships usually move through a practical sequence: align on the traveler experience, select an integration product, connect authentication, validate the journey, and grow into more surfaces.
Define the audience, entry points, target destinations, and commercial moments the Traveln journey should support.
Choose Hosted Widgets for speed, Headless SDK for deeper product control, or both for different surfaces.
Use Traveln SSO so the experience can recognize users without exposing partner secrets in browser code.
Validate the hosted or SDK journey against the selected tenant, approved origins, and expected destination flows.
Expand from planning into trips, bookings, accommodation search, OpenChat, and additional partner surfaces.
Launch Checklist¶
| Area | Public launch question |
|---|---|
| Product fit | Which traveler journey should Traveln improve first? |
| Integration product | Is speed or custom product control more important for the first surface? |
| Authentication | Which partner backend endpoint will issue Traveln SSO tokens? |
| Brand and language | Which locale, domain, theme, and copy should the traveler see? |
| Allowed origins | Which partner web origins should be allowed to load Traveln config or embed flows? |
| Success path | Which destination should the traveler reach after planning or clicking a launcher? |
Recommended Expansion Path¶
Start with a narrow, high-intent entry point. After validation, expand to additional calls to action, authenticated account areas, saved trips, and SDK-owned embedded flows.