Missed calls on a security desk at 03:00

Already on an alarm, and the phone still ringing

The keyholder has not reached the panel yet. The Aspropyrgos warehouse is still talking on the radio. Across the desk the other person has a truck in the lane and a barrier that will not lift. The published number rings. You cannot drop the radio. The colleague cannot leave the gate. There is no third pair of hands.

You let it go. A few seconds later the number is gone.

This happens in the hours the gate sign says covered. The listing says 24 hours. The card in the building manager’s drawer says covered. The person calling already has another firm on the same card. They wanted an answer. They hang up and dial that number.

You know which panels went to the radio and which gates are on the board. The number you usually do not have is how many people tried to reach you this night and could not. That number is in the provider’s log. Pull it. Mark 03:00 to 06:00. Mark the two shift-change hours.

Those hours are the ones you believe you are covered and busy. One of you waiting for a keyholder. The other talking a porter through a keypad. The number on the van is ringing. Nobody is free for a missing relief, and nobody is free for a new block that wanted a look this week.

Who hangs up

Three things happen when nobody picks up. They do not cost the same.

Someone whose site is already on the board will often leave a message. They want a fob added. They want the basement key noted. They will still be there in the morning. These are the voices you hear when you open the voicemail, so these are the voices that shape what you think the problem is.

A porter whose relief has not arrived will not leave a message. A manager who wants a quote for a new block will not. A stranger who asked what time the van passes, and heard a busy tone, will not. They hang up. The provider’s log has a short ring. Your voicemail has nothing.

Someone who already tried twice after last month’s storm of panels, or whose neighbour told them you never pick up at 03:00, never rings again. That one is not in the log either.

The people who hang up are usually calling about a first alarm on a site you do not yet cover, a missing body, or a route. Those are three different jobs. What they needed first was an answer. The route, if any, is what you never say. The dispatch, if any, is what you say when you can see the radio.

Why the voicemail hides the new file

On a night you get two jobs on the same phone. When you open the voicemail you hear the wrong one.

The existing site has a contract in the house and a reason to persist. They leave a message, or they come in for the fob anyway. The person with a new block, and the porter who has been on the gate since ten, have neither. They cannot quote a contract number they have never been given. They cannot wait, because the event that made them call has a clock on it. The relief was due at ten. The manager is sitting with two cards.

So you finish the radio, you open the voicemail, and you hear an access list. You do not hear the Marousi block. You do not hear the stranger who asked for a pass time. Those people never spoke into the box.

The calls also arrive together. Shift change is not one missed call an hour. It is five in twenty minutes, and both of you are already on a line. A second person on the desk takes the first two. The third still hears a busy tone.

A caller rings about a missing relief and also wants to know when the van passes. That is a flagged note and a refusal. If the note says only “Giorgos, question”, both wait, and the route half is the one that will go to another ear.

Movement inside, a vehicle through the arm, a key that did not come back, a missing relief: those cannot wait in the morning list. They also cannot be finished by an assistant inventing a pass time to keep the caller on the line. Take the request. Flag a phone. Say the desk will look at the radio.

Storm nights, 06:00, and a manager afternoon

These are not the same overflow. If you teach the assistant one generic “busy night” label, it will treat a person at a dark gate like a fob collection.

A storm is panels. By two in the morning, people have started ringing. You are already on the radio about the first three. The pad is already a list of sites. An alarm in that hour is a note. A new-site call in the same hour is a look or a callback. If the assistant parks the person who wants a new contract behind the tenth false alarm, that person rings the next firm.

Shift change is a smaller version of the same hour. Porters report that the relief is late. Managers who looked at a block on Sunday ring about a night porter. Tag them separately. The missing relief is the site and the clock-on. The new porter is a look at the building. Mix them and you sit down at seven with someone who only needed a note, while the person who needed a quote has already called the next name on the listing.

A manager afternoon is two blocks walking out with your card. They ring from the lobby. They will not leave a message. They will try the next card in the same envelope. Shorten the ring-time before forwarding on those afternoons. The third caller should not hear a busy tone.

August needs its own dates. Some of you leave one person on the desk. The published number still rings. Set the closure dates. Do not let the assistant book a site look into a week when the office is dark.

Alarm is a note. A visit is a visit.

The first question on the overflow is not when they are free. The first question is alarm or visit.

Alarm. Something is already sounding. A warehouse, a block entrance, a shop shutter. The assistant asks for the site, then whether anyone is still inside, then a name and a number. It writes that down. It does not open a route. If they want a keyholder called, that is yours, from the file. If someone is inside and they can hear movement, it stops the intake and puts the caller through to a phone you actually hold.

Visit. They want a new site look, a key collection, an access list change, a time to swap a shift on paper. The assistant asks which of those they mean, then looks at the diary. It does not invent a monthly figure from a description of a lobby. It does not read the roster. If you have closed new work this month, it says so on the first call, from the line you typed in.

A ten-minute key collection is not a site look. An access-list change is not a quote sitting. Mark them as different visits, or the overflow will fill Thursday with people who only needed a fob, and the person who needed an hour at the gate will be given ten minutes at the door.

People remember the site. They do not remember the contract number. Ask for the site first. If they offer the number, take that too. One identifier is enough to put the note on the right file. None is still a note, not a guess.

Calls that cannot wait until you come off the radio

Four calls on this phone do not belong in a digest you read after the keyholder has arrived.

Someone is inside and they can hear movement, or they say a vehicle went through the arm. That is a transfer. You give the assistant a short list: movement, arm broken, vehicle through. It collects a name and a number while it is connecting. It does not tell them to chase. It does not give a route.

A relief has not arrived. The assistant takes the site and the clock-on. It does not say who was rostered. It does not invent an arrival. Flag a phone.

A key did not come back. Flag it. Do not describe how the basement is covered tonight so they will stay on the line.

A stranger asks what time the van passes. Take a name and a number. Refuse the map. Do not fill the waiting with “they usually come after two”.

Everything else can wait for the transcript: a first look at a shop, a fob for next week, an access list the manager asked for on Friday.

What the assistant must do on the overflow

Answer. Nobody picked up. That is the loss. A person who would have hung up now has someone on the line.

Every answered call should already know the split: alarm or visit; site name; ordinary note or same-day flag. A loss that used to be invisible becomes a list you can work when you come off the radio.

It does not confirm a route. “What time does the van pass?”, “is Giorgos on tonight?”, “which gate does the patrol use?”, “can I wait at the usual place?” are written down and refused. The desk looks at the radio. The roster stays in the cabinet.

Alarm or visit, first. If every name lands in one column you have a heap, not a callback list. A caller who is both — a missing relief and a pass-time question — still gets a note and a refusal. Those are two conversations for you, even if they arrived as one call.

It books a time to collect a key, or a first look you can actually keep, or it writes the request down. It checks the diary before it offers a time. It never offers a site look in an hour you have closed for the radio. It confirms by SMS, in the language of the call — 70+ languages.

It does not invent a monthly figure, read a roster, or name who holds a key. If a caller asks for a round figure from a lobby, the assistant records the question and says the desk will call back.

Movement, missing relief, missing key, route-from-a-stranger remain a flag to a phone. The assistant collects a name and a number. It does not fill the waiting with a pass time.

What you set first

1. Pull the call log first. Unanswered calls per hour and per night, a month back, with 03:00–06:00 and shift-change marked. If you skip this you will never know whether anything improved.
2. Forward on no-answer, not always. A short ring in a quiet week. Shorter at 06:00, so overflow is caught while you stay on the radio. A call you pick up never leaves the desk. See pricing.
3. What you cover, and whether you are taking new sites this month. A firm that is closed to houses should say so on the first call, not after a booked look.
4. Require the alarm-or-visit question on every new call, then the site name.
5. Tag the categories you care about — alarm, gate, shift, key, new site, route-refused — so the weekly summary is a decision aid rather than a pile.
6. Route movement, missing relief, missing key and a route question to a phone, not into an email digest that gets read after the keyholder has arrived.
7. Enter the two kinds of visit. A look that needs you at the gate, and a short time to collect a key or change an access list.
8. Re-pull the call log after four weeks and compare unanswered calls, not “calls the assistant handled”.

A quiet Tuesday afternoon is not the test

A Tuesday at 15:00 is useful for checking that the greeting is right and that the assistant asks alarm or visit. It will not tell you whether you are still losing the new block at 03:12.

Nights, and the two shift-change hours, are where the new-file leak hides, because that is when you believe you are covered. Set the forwarding rule so both windows are covered. Then look at them as two columns. If quiet afternoons go to zero unanswered and nights do not, you have a ring-time problem on the burst, not a greeting problem.

After the published day still exists. People ring from a gate at 03:12. Managers send porters out after ten. Measure those calls as their own column.

Do not put a patrol sheet in the notes. It will read the sheet out.

How to read the provider’s log

Do this once, on paper, before you change the forwarding rule. Pull one night and read it against the pad. Count three things.

Count the unanswered rings between 22:00 and 06:00, when one of you is on an alarm and the other is at a gate.

Count the messages that came from people you already know. Those are the fobs and the access lists. They will still be there in the morning. They are the only missed calls you can name without the log, because they left a voice.

Count the numbers that appear once, for a few seconds, and never again. You cannot tell from the log what they wanted, because nobody answered. A missing relief, a new block, a stranger asking for a pass time: all of those look the same when they hang up. The next night, if the assistant took the overflow, those lines have a transcript and either an alarm note, a visit, or a refused route.

The log will also show a number that rang four times in six minutes. That is usually someone still at a gate, or a manager in a lobby, or a key that did not come back. Send it to a phone.

After you have those three counts, look at the forwarding delay at 06:00. A short ring is right when you can pick up. It is too long at shift change, when the fourth caller is already gone.

What changes after it answers

A person who would have hung up now has an alarm note with a site, or a look on a morning that is free, or your phone ringing because someone can hear movement.

It does not decide whether the van is nearby. It does not name Giorgos. It does not invent a monthly figure to be helpful. Alarm and visit are labels on the note, so the right person sees them. They are not a route.

It does not replace the callback. An existing porter who asked whether a fob is on the list still needs you. The difference is that you now call back a number written down at 03:12, instead of discovering at 07:00 that someone rang and said “security”.

Finish a new-site request first. Treat an alarm as a note plus, if they want, a time to collect a key. A time to collect a key is ten minutes at the cabinet. A site look is you, the gate, and an hour.

The value of a new site is yours to put in. The worked example above is arithmetic on stated assumptions. A firm that lives on warehouses and a firm that lives on blocks are not the same business. Put your own figure in.

Whoever takes the first alarm often keeps the site. That is why a missed 03:00 call is not only a missed note.