Timing: after training, not after the invitation
First practice: the code does not go out at the moment of the invitation, but once the person has passed the required trainings. Permits, the visit itself and the health declaration do not block sending, so the coordinator does not have to wait for all documents, but the training is a necessary condition.
As a result, a contractor who did not pass the training does not get the code, and security at the gate does not see unmet conditions that the team would have to explain on site. The coordinator can ask for the training in advance, through the link in the invitation.
Channel: e-mail, SMS or nothing
Second practice: match the channel to the person's data. When a person has an e-mail address, the code arrives by e-mail. When there is no address but there is a phone number, the code goes by SMS with a link. When there is no channel at all, nothing is sent, and the coordinator sees that this person needs a label issued at reception.
Invitations and QR codes can also be sent to people without an e-mail address, using a phone number or a registration number. This matters for temporary workers and contractors from smaller firms, who do not always have a company mailbox.
Message content: language, first name, date
Third practice: the message should speak to the person, not to the plant. The subject is in the recipient's language, including Polish and German, the first name stands in the greeting, the registration date is visible, and the code is 233 x 233 pixels with a link to the plant. That size is enough for a scan from the phone screen at the gate.
Fourth: the code is in the body of the message, not in an attachment, because attachments open more slowly on phones and often in another app. The contractor should be able to show the code with one move from the e-mail or SMS.
Once per person and retrying after an error
Fifth practice: make sure the code goes out once. The message with the code is sent once per person, and the guarantee comes from an atomic column in the database, not from the order of calls of three triggers. As a result the coordinator does not have to remember whether the invitation, the training and the visit registration will each send the same message three times.
Sixth: do not send it manually when delivery failed. A failed send releases the sending marker, and the queue retries, so the code does not get lost silently. Manual retrying bypasses the marker and may produce a duplicate that confuses the recipient.
- The code goes out after the required trainings are passed.
- Channel: e-mail first, SMS with a link second.
- The code in the body of the message, not in an attachment.
- Subject in the recipient's language, first name in the greeting.
- No manual retrying: the queue does it by itself.
Information for the contractor: what to say in the invitation
Seventh practice concerns the content of the invitation: write in one sentence that the code must be on the phone at the gate, that it works in the browser, and that the message should be saved so that it opens without signal. Also suggest that the screen should be brightened at the moment of the scan.
A coordinator who adds this sentence to the invitation template reduces the number of calls to reception. Details on signal in the hall are described in a separate page of this set.
Checklist
Video
Frequently asked questions
Can the code go out before training?
No. Sending starts after the required trainings are passed, and permits and the health declaration do not block it.
What about a person with neither e-mail nor phone?
Nothing is sent. A label with the code is issued to that person at reception.
Will the code arrive twice?
No. The atomic column in the database guarantees it, and a failed send releases the marker so the queue retries.
Let us set up code sending in your invitations
We will go through the whole invitation template and the sending order with your visit coordinator. Let's schedule a short call.
Let's talk