LO
Get told when a verified record lands on this occupation →
Receptionist / front desk
The first person at the door: signs people in, answers the phone, knows where everyone is, and handles whatever walks in that nobody planned for.
This is not a probability of losing your job. It combines how much of the role's task load is exposed to automation with how far adoption has actually gone — useful for comparing occupations on one consistent basis, and for nothing else.
Covers office and building reception, and hotel front desk where the tasks overlap. It does not cover call centre work, which is a separate occupation here with a larger volume and a different structure. Whether the desk is also doing office administration — ordering, travel, facilities — changes the exposure a great deal, because that work is not at the door.
The evidence base holds verified records for other occupations, but not one for this one yet. Until it does, the analysis below is reasoning about task structure and known technical capability — for this job in particular it is not backed by traceable sources, and we would rather say so than cite things we have not verified. An empty section here is a gap in our coverage, not a finding about the work.
What is actually changing#
The unit of analysis is the task, not the job title. A role is not replaced — its task mix shifts.
Is this your job? Say so and this page narrows to your share of it.
A job title is a bundle of tasks bought together, and no two people hold the same bundle. Nothing is sent anywhere — it stays in this browser.
Signing people in
Automating≈ Platform inferenceVisitor registration, badges, notifying the host, the delivery, the courier who needs a signature.
Visitor kiosks are a solved product and have been for years: the process is a fixed sequence with a machine-checkable outcome — the visitor is registered and the host is notified, or the screen says so. This is the clearest completed automation in office administration and it happened without any model being involved.
The kiosk handles the compliant visitor and escalates everyone else, and everyone else is the reason the desk exists: the contractor not on the list who is expected, the person who is early and upset, the delivery that cannot be left. Automating the rule does not assign the exception to anyone, and several buildings that removed the desk have re-added a person under a different title and grade.
The phone and the routing
Automating≈ Platform inferenceWorking out, from a vague description of a problem, which of forty people is the right one — and whether this caller should reach them at all.
Routing is a classification problem with a checkable result, and it has been automated in stages for thirty years — menu trees, then directories, now models that handle a caller who cannot name the department. Each stage took a share, and this one takes the share the menu tree could not.
Routing is not gatekeeping, and the second is what a desk actually does for the people behind it — deciding that this caller should not be put through, or should be put through immediately. Automating the routing without assigning the gatekeeping converts a filter into a funnel, and the cost lands on everyone else's calendar rather than on the desk's budget.
Whatever walks in
Still human-led≈ Platform inferenceThe unhappy visitor, the alarm, the person who is unwell in the lobby, the journalist, the delivery of something nobody ordered.
These are low-frequency, high-variance events handled in person with whatever authority the desk has, and the value is that somebody is visibly responsible at the entrance. It is the same property that holds the security guard's response task, and it fails the same way for a machine: the point is that a person is there.
The frequency is the problem. A task that matters enormously and happens twice a week is impossible to justify a full-time post with, which is why this role gets merged into security, facilities or office management rather than removed. The task survives and the job title does not, and that is the most likely shape here.
The office around the desk
Being augmented≈ Platform inferenceMeeting rooms, couriers, supplies, travel, the thing the office manager asked for — the administrative work that accretes onto a desk because somebody is sitting there.
Scheduling, ordering and booking are structured tasks that tools already handle in part, but they are held together by knowing this office: which room actually has a working screen, which supplier answers, whose travel needs to be booked a particular way. That knowledge is unwritten and is the reason the work stays attached to a person.
This is where the hours actually are for most people with this title, and it is not at the door — which means the exposure of the visible half of the job is a poor guide to the exposure of the post. Anyone reasoning about this occupation from the kiosk alone will get the answer wrong in both directions.
Which technologies matter here#
Four separate signals. They are deliberately not added together — a job exposed to two technologies is not twice as exposed.
How it got here#
The index is not a static number. This is where it would have sat at each capability checkpoint since ChatGPT — reconstructed, and labelled as such.
A high, early climb that mostly predates generative models: visitor kiosks are a solved product because registering a compliant visitor is a fixed sequence with a checkable outcome, and call routing has been automated in stages for thirty years — menu trees, then directories, now models that handle a caller who cannot name the department. The flattening is the exception: the contractor not on the list who is expected, the person unwell in the lobby. Two cautions on reading the height. Most people with this title spend more hours on the office administration around the desk than at the door, so the visible half is a poor guide to the post; and the likely change is the title being merged into facilities or office management rather than removed.
A flat line is not a forecast of safety. It says which tasks automation has reached so far — the occupations that moved least here are the ones where the constraint is physical or regulatory, and both of those can change.
Recent changes#
No verified events recorded yet.
This section will fill from the monitoring pipeline as events are collected, de-duplicated, graded and linked to the tasks above. An empty list here means we have not verified anything — it does not mean nothing is happening.
"We found no news" is not the same as "you are safe."
What this means for you#
This has been a standard first office job and the door half of it is the most automated part of office administration. What that means practically is to get the administrative half into your job description as fast as possible — meeting rooms, suppliers, travel — because that half is held in place by unwritten knowledge of this specific office and the door half is not.
The likely change is not that you are replaced but that the title disappears into office management, facilities or security. That is a negotiation you can get ahead of by being the person who already holds the administrative work, because that is what the merged role is actually made of.
Your options#
Four directions, each with its real constraints and one thing you can test this week. Continuing as you are is a legitimate choice — it just has to be a chosen one.
Take the office, not the door
The administrative work around the desk is held together by knowledge of this specific office, and that is where the hours and the negotiating position both are.
It is usually added to the desk job rather than exchanged for it, so it arrives as more work before it arrives as a different title.
Split your week into hours spent at the door and hours spent on everything else. If the second is larger, your job title is describing the smaller half.
Move to a desk where the exception is the job
A hotel front desk, a clinic reception or a building with contractors coming and going is mostly exceptions, and the exception is the part no kiosk takes.
Those desks have worse hours and more difficult people, and the pay is rarely better.
Count how many visitors this week did not fit the standard flow. That number is the part of the door that still needs a person.
Common questions#
The door half is the most automated part of office administration and has been for years — visitor kiosks are a solved product, because registering a compliant visitor is a fixed sequence with a checkable outcome. What kiosks do not do is the exception, and the exception is why the desk exists. The likelier change is not replacement but the title disappearing into office management or facilities, because the administrative work around the desk is where the hours actually are.
No date. Split your own week into hours at the door and hours on everything else. If the second number is larger, the exposure of the visible half is a poor guide to your job and you are safer than the question implies — and if it is smaller, the honest signal is not a kiosk arriving but a reorganisation merging the desk into another team. That is announced in a meeting, not by a vendor.
For the compliant visitor, completely — that is why they are standard. What they do is handle the rule and escalate everything else, and several buildings that removed the staffed desk have re-added a person under a different title and grade, usually after discovering that nobody had been assigned the exception. That pattern is worth knowing because it means the post can come back smaller and cheaper rather than not at all.
The tasks overlap and the ratio does not, which is what matters. A hotel desk handles a much higher share of exceptions — arrivals that do not match the booking, complaints, the room that is not ready — and the exception is the part no kiosk takes. Self check-in has been deployed widely in hotels for years and the desks are still staffed, which is the useful precedent: the automation took the compliant path and left the rest.
Method and sources#
- Assessment date
- 2026-09-14
- Basis of the task judgements
- 0 evidence-backed · 4 platform inference · 0 not enough evidence
- Verified events
- 0