InnerWeb
Skip to main content

Guest host at the plant: seven recommendations

The guest host is an active internal employee whom the system calls at the guest's first entry. Whom you name and what you tell them decides whether the call is answered and whether the guest gets stuck at the gatehouse. Seven recommendations for the manager of the department receiving guests.

1 call
at the guest's first entry
Source: system function documentation
89
maximum number of entries on the host list
Source: system function documentation

Who these recommendations are for

For managers of departments that regularly receive guests: suppliers, service engineers, auditors, candidates and business travellers. The stage we describe is maintenance: the system works, and the question is how to make the host role more than a formality.

Every planned visit has a host, that is an active internal employee of the plant. The system calls that person once, at the guest's first entry on the day of the visit. If the call is not answered, the guest waits at the gatehouse and the guard has nobody to ask.

Seven recommendations

The recommendations below follow from how the system handles a visit: who the host is, when the call comes and what the conversation contains.

1. Name the host personally, not the department

The host is a specific active employee, not an anonymous department. The inviter should select themselves or a person who will actually collect the guest. The host list in the planning window contains employees who have already invited someone, usually the inviters appear at the top, and the logged-in employee is always on the list.

2. Make sure the phone number is in the profile

The call from the dispatcher goes to the number in the profile. If the host has no number, he receives a single email asking him to complete the profile, but nothing will ring until then. Before you activate invitations, check that the key hosts have their numbers filled in.

3. Tell the host what they will hear

The call states the guest, the company, the entry point and the purpose of the visit. The host does not need to press or confirm anything. He should go out for the guest or name who will do it. A two-sentence briefing for the team is enough.

4. Arrange cover for holidays

When a host is on holiday and the visit was planned earlier, nobody answers the call. The inviter should change the host before the day of the visit or name a colleague from the department.

5. Do not use the host as a way around the rules

The host does not exempt the guest from training, qualifications or an active account. A planned visit removes only the requirement for a work permit.

6. Limit the number of people listed as hosts

The shorter the list, the easier it is to know who answers the calls. The planning window allows up to 89 entries on the list, but in practice most visits are handled by a dozen or so people.

7. Talk about groups

Further guests of the same host within 3 minutes are gathered into one group call. The host who receives a business delegation should know that there will be one call, not five.

Planning limits for visits

Planning limits for visitsHorizontal bar chart of limits: 377 days ahead, 34 days at once, 89 host list entries, group window of 3 minutes.0100200300400numberDays aheadDays ahead: 377 number377Days at onceDays at once: 34 number34Host list entriesHost list entries: 89 number89Group window minutesGroup window minutes: 3 number3
Source: Planned visits function documentation

Most common mistakes in staffing the host role

The first mistake is naming as host a person who does not work on site: a sales representative on the road or a manager on sick leave. The call goes out, but nobody answers, and the guest waits. The second mistake is choosing the host on the basis of who happens to be at the top of the list, rather than who actually invited the guest.

The third mistake concerns changes in the team. When an employee leaves, the visits planned for the future no longer have a sensible host. Before leaving, it is worth reviewing the planned visits and reassigning them to a successor. The fourth mistake is a lack of communication with guests: a person who does not know that someone will come to collect them wanders around the site looking for the way.

The fifth mistake is organisational: the manager assumes that the guard is responsible for the guest. The guard controls entry and the gate verdict, while the host is responsible for the guest's stay on site. The difference is worth writing into a short instruction for the department.

How to tell that a host is well prepared

A simple test: ask several hosts when the dispatcher calls and what they should do after answering. If the answer is that they do not know, there is no point rolling out further tools before the role has been discussed at the department's briefing.

Checklist

Video

Frequently asked questions

Can the host be a person from an external company?

No. The host is an active internal employee of the plant.

What if the host has no phone number?

The host receives a single email asking for the profile to be completed. The call does not go out, which is why numbers should be filled in before the start.

Does the host have to confirm the call?

The call provides information: who, from which company, through which entry and for what purpose. The call is for notification, not for approving entry.

Let's set the host role at your plant

At the demonstration we will show what the host hears in the call from the dispatcher and how to complete the profiles.

Let's talk