Blog · Sampark
Stop retyping the visit request. One email should reach every desk.
At most large sites, a single visit becomes five copies of the same email. We think the fix is not a new form. It is reading the email once.
Consider a routine visit to a plant or a mine. A host emails the admin team: two guests, arriving Tuesday evening, staying two nights, need a pickup from the airport, a room in the guest house, access to the process area on Wednesday. That one email now has to reach rooms, travel, transport, safety and the gate. At many sites, each of those desks copies the details by hand into its own register, sheet or system.
Five copies, five chances to be wrong
Retyping is slow, but slowness is not the worst part. Each copy is an opportunity for a different error: a date entered a day off, a guest’s name spelt two ways, the pickup booked for the wrong terminal. When the details disagree, nobody knows which copy is right, and the guest finds out at the gate or the guest house counter.
Worse, the copies drift. If the visit moves by a day, the host emails again, and the change has to be noticed and retyped five more times. The desk that misses it is usually the one that finds out last, which at most sites is Security.
Why “make them fill a form” rarely works
The usual answer is a mandatory request form. In practice, hosts are senior people with little patience for forms, visits are often arranged by people outside the site, and urgent requests arrive by email or WhatsApp regardless of policy. The form becomes one more thing an admin assistant fills in on the host’s behalf, from the email. The retyping has moved, not gone.
We think software should take requests however people already send them: email, form or WhatsApp.
Read it once, approve it in parts
In Sampark, the request is read once. AI pulls out the guests, dates, rooms, travel, transport, access and host, and a person checks what it extracted. From then on, there is one request, and each desk approves its own part of it: rooms, travel, transport, safety and gate. Nobody retypes a thing, and every hand-off is on the record.
| Desk | Its part of the one request |
|---|---|
| Rooms | Stay request and a live board by block |
| Travel | Approval in one place, ticket PDF uploaded, e-ticket on WhatsApp |
| Transport | Pickup opens automatically when travel is approved |
| Gate | Guest on the digital expect list with a QR before arrival |
| Housekeeping | Arrival alert 15–20 minutes out; checkout opens the turnover |
Why a person still checks
We do not think AI extraction should go straight to the gate unchecked. Names, dates and access areas matter for safety and security, and an email can be ambiguous: “arriving Tuesday” sent late on a Monday night means something different from the same words sent a week earlier. A quick check by someone who knows the site, at the one point where the request enters, is far cheaper than five desks each interpreting it on their own.
The same principle applies after approval. If one desk cannot meet its part, for example no room is free in the requested block, that should show up on the shared request where the host and the other desks can see it, not in a separate reply thread that only the guest house reads.
What changes for the people involved
- Hosts keep emailing; they do not learn a new tool.
- Desks see the same details, so disagreements become rare and visible.
- A change to the visit is made once and reaches everyone.
- The head of admin can see every visit, approval and hand-off from the control tower, around the clock.
For how this plays out at individual desks, read the travel desk workflow for plants and mining sites and guest house management for industrial townships. More in the Sampark guides.
Questions
Why not just make hosts fill a visit request form?
Hosts and outside visitors keep using email and WhatsApp, so someone ends up filling the form from the email. Reading the email once avoids the retyping altogether.
Does AI send the extracted request straight to the desks?
In Sampark a person checks what the AI pulled out of the email, then each desk approves its own part of the same request.
What happens when a visit changes?
The change is made to the one request, so every desk sees the same updated details instead of five copies drifting apart.
See it on your own data. Sampark — Every desk and guest, one spine. Book a 30-minute working session with an engineer.