Inspection chase and key follow-up for elevator vans
Quick summary
- You are in a machine room. The inspection list and yesterday's empty cabin without a key still have to be chased.
- The list is a named building, a morning reminder, or a missing key. Not a second opinion on which buttons to press.
- Every call starts with the building or the name on the file. If they do not recognise them, the call stops.
- It does not give a reset. A missing key is a yes or no. What the red lamp means is a callback.
- If they ask which buttons to press, the assistant writes the question down and says the technician is at the controller.
- SMS does the first reminder. The voice call is for the building that still has no key the morning after a power cut.
TL;DR
You are in a machine room. Twelve inspection letters are still unanswered and yesterday's empty cabin still has no machine-room key. Nobody is going to spend the afternoon ringing. An assistant works the list you give it: building or name on the file, one purpose. It asks whether someone will be there with the key. It does not say which buttons to press, whether the lift is safe, or what a modernization will cost. If they ask, it writes the question down and says the technician is at the controller. It can book a morning if that morning is free. It will not ring a tenant's mobile about a shaft that is not on their file.
Key takeaways
- Build each list from your own files: building or name, the number on the file, and one purpose.
- Do not put a tenant mobile on a communal chase unless that number is the number on the file.
- Write the purpose as a reminder or a chase, not as a question about a reset.
- If the client asks which buttons to press, the assistant ends the call and flags the technician to call back.
- Check the book before you speak a morning. Do not read Thursday off last week's pad.
- Keep modernization prices and last year's neighbour off the script. The technician looks at the shaft.
The lists on the seat while you are in a cabinet
The controller is still open. Twelve inspection letters are still unanswered. Yesterday’s empty cabin still has no key. You are not going to spend the afternoon ringing.
That is the outbound problem on this van. Not a campaign. Not a hunt for new shafts. A list of buildings you already know, an address you have already written down, and nobody free to ring because both hands are on a cabinet.
The assistant works only the list you give it. One purpose each. Will someone be there with the key. Can we keep Thursday for the inspection. Was the log left out. It does not add “and while I have you, which buttons”.
Open with the building, or stop
The call says the van name, the building or the name on the file, and asks whether this is that person. If they do not recognise the block, the call ends. A tenant who picked up the manager’s phone does not get a briefing on a shaft. A neighbour who answered a house mobile does not get a lecture on the cabinet.
Communal files are the usual trap. The number on the file is the manager. A resident who is on the stairs will pick up anything. The assistant does not move the conversation onto their mobile unless that mobile is the number you entered.
One purpose, then the book
A key chase is a yes or no, then a morning if the book has one. An inspection reminder is a window you already wrote down, checked again before it is spoken. If Thursday has since filled with a release, the assistant does not read Thursday off last week’s pad. It checks, or it takes a callback.
If they ask which buttons to press, the chase is over. The question is written in their words. The technician calls back. A reminder that becomes a walkthrough has no one at the controller.
If they ask whether the lift is safe, or what a modernization costs, those are callbacks too. The assistant does not fill the silence with last year’s neighbour.
A power-cut week is not an inspection month
A power cut is cabins. The chase is yesterday’s building that still has no access, or a manager who said they would be there and were not. Shorten the list. Someone inside stays on a phone you hold. Do not let the assistant work a long inspection list while five cabins are waiting for a key.
Inspection season is letters. People still have a working lift. They forget. The chase is a morning and a key, not a rescue.
August, if you chase holiday-block inspections, needs its own dates. Do not ring a coastal block in a week you cannot reach the village.
What you put on the list
Building. Name. Number on the file. One purpose. Whether a morning is already in the book. Who should hold the machine-room key.
You do not put a reset diagram. You do not put a price. You do not put a tenant who once called about a door on a shaft chase.
Export the files. Tick them. The assistant does not invent a fourth name because the afternoon looks quiet.
What a good outbound call sounds like
Van name. Building. Are you the person on the file. Purpose in one sentence. Yes or no. A morning that exists, or a note. Stop if they ask for a reset. SMS of the reminder, not of a sequence.
There is no “press it until we arrive”. There is no quote. There is no tenant briefed about a machine room they cannot open.
If the assistant is efficient and still talks them through a reset so the file can move, you own that sequence. Put the person who still has no key on tomorrow’s morning, and put the button question on a callback with your name on it.
Rates live on the pricing section of the home page. They are not repeated here.
Who is not on the list
A lead who sent a photo of a cabin last spring is not a chase. That is inbound work if they ring again. Outbound here is buildings you already opened, letters you already sent, cabins you already took.
A spouse’s mobile, a shop downstairs, the café that holds keys for the block — only if that number is the number on the file. A helpful neighbour is how a shaft gets described to the wrong person, and how a reset request arrives from someone who does not own the cabinet.
Do not chase an inspection and a modernization on the same script. The purpose line has to name the visit, or the person who picks up will answer for the wrong morning.
After the call
You see the purpose, whether they will be there, the morning if one was booked, and any question that stopped the chase. You do not see a completed reset. You do not see a price. You do not see a lift declared safe from a sentence.
If half the inspection list still has no key after two weeks of calls, the problem is not the greeting. It is the number on the file, or a manager who is not the person who opens the machine room. Fix the list. Do not lengthen the script.
The value of a recovered morning is yours to put in. The worked example above is arithmetic on stated assumptions. A van that lives on releases and a van that lives on inspections are not the same week. Put your own figure in.
AI receptionist, in-house staff, or a call centre
| CITT | In-house | Call centre | |
|---|---|---|---|
| Key chase after a power-cut cabin | Yes, from your list | When someone has time | If you write a script |
| Inspection reminders | Yes | Yes | Sometimes |
| Starts with the building or the name | Yes | Yes | If you insist |
| Reads a reset to hurry the key | Never — the technician is at the controller | The technician does, at the cabinet | A risk if the script drifts |
| Answers whether the lift is safe | No — flags a technician | The technician does | Must not; sometimes does |
| Offers a morning the book does not have | No — checks the book, or takes a callback | If they check | Often from last week's pad |
| Rings a tenant about a communal shaft | No — only the number on the file | Only if you said so | A risk if the list was not read |
What unchased inspection letters cost one week
Worked from these assumptions — change any of them and the answer changes:
- Two people, 18 open inspection files in a given month, each waiting on a morning or a key.
- This example treats 7 of those 18 as still unanswered two weeks after the letter.
- A morning that sits empty, or is pulled when the key arrives at four, wastes about €120 of reserved time — put your own figure in, not ours.
- A two-week outbound chase recovers half of those missing mornings. Challenge this first; vans vary.
- 7 files still open on paper, two weeks out.
- Half recovered — 3 mornings that move on the key they needed, this example rounds down.
- 3 × €120 = €360 of reserved time protected, in one week of chasing.
- Several such weeks a year — this example counts four.
About €1,440 a year of van time, from calls that only ask whether someone will be there with the key.
What it costs
CITT is pay as you go: no packages, no minimum, no contract. The current rates — the monthly fee per number and the per-minute rate — are on the pricing section of the home page, which is the only place they are published.
Frequently asked questions
Can it tell them what is missing for the inspection?
It can name the item you put on the list — the machine-room key, access to the landing, the log book. It should not rebuild the lift on the call, and it should not decide that a particular noise means the inspection is overdue. If they ask which buttons to press, that is a callback. The technician is at the controller.
What if they ask for a reset, on the chase call?
The assistant does not answer. It says the technician is at the controller, takes the question in their words, and ends the chase. A chase that becomes a walkthrough has no one at the cabinet. The transcript still helps — you return a real question rather than “they rang”.
Can it offer a new morning for the inspection?
Yes, if you allow that purpose and if it checks the book before it offers a morning. It still does not tell them which buttons to press. A reminder that starts reading a sequence has stopped being a reminder.
Does it still ask for the building when we ring?
Yes. The call opens with the van name, the building or the name on the file, and it stops if the person on the line does not recognise them. That is how you avoid briefing a tenant about a shaft, or a neighbour about someone else's cabin.
Can it chase an inspection from an existing client?
As a morning reminder, yes: we have a window this week, can you be there, here is who should hold the key. Not as a sentence that the lift is safe until Friday, and not as a price. “We still have Thursday at 09:00 for the inspection” is reception. “Just press reset until then” is a sequence.
Who decides who is on the list?
The van. The assistant does not invent people to ring. You export or tick the files that need a reminder or a chase, with one purpose each. A list that mixes “where is the key” with “see if they want a modernization” is two jobs, and only the first one belongs here.
