Pilgrim experience
The personthe whole operationexists for.
The traveller usually has the least visibility of anyone in the transaction. Rhlah gives them a surface of their own, built from the same records the operator works in.
- Travellers assigned
- Documents complete
- Payment schedule met
- Supplier confirmations
- Transport assigned
Capabilities
What this engine doesand what it does not.
Each capability below carries its real status. Anything marked planned is modelled in the platform and not yet operating.
Journey view
Where they are in the plan, what happens next, and when.
Documents
What is complete, what is outstanding, and what is expiring.
Payments
What is paid and what is scheduled, from the same ledger finance reads.
Itinerary
The religious and logistical shape of the trip, day by day.
Messages
One thread with the people organising the journey.
Guide & driver surfaces
Field task lists for the people delivering the journey on the ground.
Offline use
Working without connectivity in the Haram. Not built.
Push notifications
Device notifications for journey events. Requires a provider that is not yet connected.
Connected by design
Nothing here works alone.
This engine is authoritative for its own domain and reads everything else from the engine that owns it.
Bookings
The pilgrim sees their own booking, never a copy of it.
Journey
Operational state drives what the traveller is shown.
Documents
Requirements are the same ones operations chases.
Communication
Their messages are the operator's conversation record.
Ready to run your business differently?
See how Rhlah can fit your Hajj & Umrah operation.