Customer, Agent, Supplier, And Widget Workflows
TripNova separates public self-service flows from admin workflows while keeping the underlying quote, booking, document, and communication records synchronized.
Customer Portal
Customers can view bookings, quote activity, refunds, documents, travel wallet entries, and offline-ready travel information when their session or access token is valid. Keep portal URLs behind HTTPS.
Agent Portal
Agents can review assigned leads, quotes, and commission-related information depending on enabled permissions. Agent login codes should expire and should not be reused across public demos.
Supplier Portal
Suppliers can review confirmation requests, allotments, invoice uploads, contracts, and message threads. Supplier records should be scoped to the agency and protected by portal access checks.
Embeddable Widgets
Package search, booking button, and lead capture widgets use generated embed tokens. Rotate a token if it is exposed on a site that no longer belongs to the buyer.
Travel Wallet
The wallet collects passes, checklists, emergency contacts, documents, and offline items for a booking. Sync wallet data after major booking changes so customer-facing details remain current.
Portal Verification
- Use separate customer, agent, and supplier test accounts.
- Verify each account sees only its agency, booking, assignment, commission, or supplier records.
- Test quote acceptance, document download, message submission, and wallet refresh on mobile.
- Open a direct URL from another test account and confirm access is denied.
- Expire a login code or token and verify it cannot be reused.
Do not test a public demo with live payment keys, real traveler documents, or unrestricted outbound messaging.