How Hajj works from Türkiye
Where other markets need convincing that instrumented group management is worth having, the Turkish market tends to arrive with the question already answered and a list of requirements attached. Data handling, auditability and clear escalation policy get scrutinised properly here. That is welcome. It is the same scrutiny we would want applied to anything a family is trusting with a parent.
The Turkish contingent also skews toward organised, well-briefed groups with strong leader structures already in place. The value is less in creating oversight where there was none and more in replacing a manual process that is already being executed diligently, at real cost in staff attention, with one that runs continuously.
Risks for a Turkish group
A high existing standard
Group management is already organised and well-staffed. The gain is continuous coverage, not basic oversight.
Serious data governance expectations
Retention, residency and access scoping get properly examined. All three are configurable under Fleet and Authority.
Single working language
Turkish across the contingent simplifies console and family app deployment.
Older, well-prepared pilgrims
Preparation reduces disorientation risk but does nothing about heat physiology or falls.
Questions from operators in Türkiye
- Where is location data stored, and for how long?
- Retention windows are set by you under the Fleet and Authority tiers, and data residency is configurable under Authority. Default retention is the pilgrimage plus 90 days, after which location history is deleted.
- Can this integrate with systems we already run?
- The Authority tier includes API access for manifest integration. Fleet includes manifest import and audit export.
- Is the console available in Turkish?
- Yes, for both the console and the family app.
Apply to the Hajj 1448 / 2027 pilot
A small number of operators for the first season, at cost, with direct access to the engineering team.