Submit pilgrim files to Nusuk without lifting a finger

Nusuk Masar is the official Saudi portal through which licensed agencies declare their pilgrims and groups to obtain Umrah visas. Each pilgrim is created there with passport and personal details, attached to a group and a programme, then tracked until issuance. For the agency it means one entry per pilgrim, on an external portal, whose statuses must then be copied back into internal tracking — that back-and-forth is what OmraDesk removes.

With OmraDesk, the agent stays logged in to the portal in their browser, as today, and an extension executes the operations from the files: pilgrim creation (passport scan, personal data, declarations), group creation, pilgrim assignment, programme attachment, then status polling. The agent chooses the files and launches; they keep the decision to send to the consulate and fix the errors returned. Their Nusuk credentials are never stored by OmraDesk.

Identity as printed on the passport, passport number and dates, nationality, date of birth, sex, address and contact details, the required declarations, a compliant photo, then the group and the stay programme. In OmraDesk these details are already in the file — mostly read from the passport — and checked before sending: passport validity, name consistency, photo in the right format. Whatever is missing blocks the file before the portal, not after.

That is the point of the integration: the OmraDesk pilgrim file is the source, the extension fills the portal from it, and statuses flow back into the file. A pilgrim is created once, a group is created once, and a lock prevents submitting the same file twice. Corrections are made in OmraDesk, then propagated. Time spent becomes checking time, not typing time.

The Nusuk hub shows, by departure, every pilgrim with their portal status and last update; automatic polling refreshes statuses, and a drift check flags a file whose state on the portal no longer matches OmraDesk. Errors (rejected document, missing field, duplicate) surface in a queue to handle with their cause. A log keeps every transition and every group creation.

Pilgrim creation in four steps (passport scan, passport data, personal information, declarations), group creation, assigning one or several pilgrims to a group, programme attachment, polling the status of the group and of each pilgrim, and deleting a pilgrim created by mistake. Deliberately manual: installing and pairing the extension, logging in to the portal, sending to the consulate and handling the errors the portal returns.