Who these recommendations are for
The recommendations are addressed to the head of maintenance, the person responsible for security and the system administrator who sets up employee profiles. They apply to plants where service technicians from external companies appear often, and some visits are quotes, inspections and measurements without any work on the installation.
The basis is one: every visit has a host who is an internal employee, and at the first entry of a guest on the day of the visit the dispatcher calls that person once, without retries. The recommendations follow from how this one call is spread across the working week of the plant.
Recommendation 1: the host is the person who arranged the visit
The host should be the person who invited the service technician and knows why he is coming. The dispatcher should not decide who looks after a guest. A call to a person without context ends with the question "and who is that?", and the host becomes an intermediary instead of a host.
Reason: an informational call only makes sense when the recipient understands the situation without asking questions.
Planning and call-grouping parameters
Recommendation 2: do not enter the head of maintenance as the default host
If one person handles all visits, that person's phone rings for every service technician. When further guests of the same host arrive within 3 minutes, the system combines them into one group call, but this eases the problem only when arrivals are close in time. Share the role across the team: a planner, a shift foreman, a purchasing coordinator.
Reason: the load on one person grows linearly with the number of service technicians, and a group call helps only with entries within a short window.
Recommendation 3: check the host phone numbers before the start
When a host has no phone number, the system sends one warning email instead of a call. The email is a safety net, not the intended channel: the dispatcher counts on a conversation, and the manager may not read the email for an hour. Before go-live, check in the profiles whether the people who will act as hosts have their numbers filled in.
Reason: the warning email tells you that a call was not possible, but it does not replace contact in person.
Recommendation 4: plan recurring visits in advance
A visit can be planned for many days in one entry, up to 34 days and no further than 377 days from today; a day with an existing visit is skipped. For a service technician who is to come over a month, the host plans the whole series once, instead of setting it up every day at the gate.
Reason: a same-day visit set by security should remain an exception, and planning in advance moves the decision to the person who knows who is entering and why.
Recommendation 5: a backup host during holidays
A visit has one host. When that person is on holiday, the call goes nowhere. For a planned series, choose a host who will be present for the whole period, or split the series between two people.
Reason: the entry event happens once, and the lack of a host only becomes visible when the service technician stands at the gate.
Recommendation 6: a visit only for people without work
A visit removes only the permit requirement for one day, without a time of day. It fits a talk, a quote and measurements. If a service technician is to do anything on the installation, a permit is needed. The host who enters the visit takes responsibility for making sure no work takes place.
Reason: training, qualifications and an active account still decide who is let in, so this distinction is the only control at this point.
Recommendation 7: name a path for a host who does not answer
The dispatcher calls once and does not retry. So establish in the plant who welcomes the guest when the host is unavailable: reception, the shift foreman or the coordinator. The system does not settle this question, and the answer must be known to security before the first service technician arrives.
Reason: the lack of retries is sensible, but it requires an organisational rule on the plant side.
How to start: three steps for the first week
Step one: a list of potential hosts. List the people who actually invite service technicians and check their profiles: whether the account is active, whether the phone number is filled in, whether they know they will be hosts. This is usually 5 to 12 people, not the whole plant.
Step two: a dry run. Plan a visit for tomorrow for a test account, assign one of the hosts and check whether the dispatcher calls and the host understands the message. If the call reaches someone who does not expect it, correct the entry before the first real service technician.
Step three: a substitution rule. Write down who takes over the guest when the host does not answer. The dispatcher calls once, so the rule must be known to security in advance. After two weeks, review how many service technicians came on a same-day visit and how many on a planned visit: the ratio shows whether the hosts plan ahead.
Video
Frequently asked questions
Can the host be an employee of an external company?
No. The host is an internal employee of the plant.
What if a service technician arrives on a day with no planned visit?
Security can set a same-day visit, but only when the single missing item is the permit and the person belongs to an external company.
How many calls will a host get with three service technicians?
If they arrive within 3 minutes, the system combines them into one group call. With longer gaps, each first arrival triggers a separate call.
Does the host have to approve the entry?
No. The call informs that the guest is on site; the entry depends on training, qualifications and the account.
Let's talk about one-time entries at your plant
We will show the path of a guest, a courier and a service technician on sample data and agree what the plant needs to prepare. Book a short presentation.
Let's talk