Reception interviews test how you come across in the first ten seconds and how you hold up when the phone, a queue and a courier all need you at once. Expect a few questions on why you want the job, stories from past work with the public, what-would-you-do scenarios about security, privacy and upset visitors, and checks on the basics: taking a message, booking appointments and the computer tools a desk runs on. Each question shows what the interviewer is listening for, a shape for your answer and a short answer to say out loud. Put your own stories in before the day.
Search all questions by round, difficulty and level, or save the ones you want to practise.
The pull: what you genuinely like about front-of-house work, with one small example.
The skill: why being the first face matters to a business.
Why here: a link to this office and its visitors.
"I like being the person who sets the tone. In my last job at a dental clinic, I noticed that if I greeted someone by name and told them roughly how long they'd wait, they sat down relaxed. If I didn't, the same wait felt twice as long to them. That showed me the desk isn't just admin, it shapes how people feel about the whole place. I'm also someone who's happy juggling lots of small things, so a day of calls, visitors and bookings suits me better than one long task. And here you have clients coming in for meetings that matter to them, so a calm, organised welcome counts for a lot."
Saying it looks like an easy job, or that you just want something quiet and nine to five.
Who: the likely mix, such as clients, candidates, couriers, contractors and staff.
What they need: a quick welcome, clear directions, the right person reached fast.
Your fit: why your experience matches that mix.
"From your website, you're a law firm with three teams in this building, so I'd expect clients arriving for meetings, some of them stressed about their case, plus job candidates, couriers and the odd contractor. On the phone it's probably clients chasing their lawyer and people asking if you handle their kind of problem. What they all need is to feel expected and to reach the right person quickly. For clients, I'd guess discretion matters most, since nobody wants their legal problem discussed in a waiting room. I've worked a busy front desk before and I'm used to switching from a courier to a nervous visitor in a few seconds, so that mix doesn't worry me."
Knowing nothing about the business, or talking only about the tasks and never about the visitors.
Transferable proof: one or two jobs where you served people and juggled tasks.
Specific skill: calm, accuracy or friendliness, each with a quick example.
The gap: what you'd need to learn and how fast you'd learn it.
"I haven't sat on a reception desk, but I spent two years working the till and the phone at a busy café. At lunchtime I'd be taking a phone order, serving a queue and answering a delivery driver, all at once, and I learned to acknowledge everyone quickly so nobody felt ignored. I also volunteered at a community centre where I signed people in and kept the room bookings, so the idea of a visitor log and a diary isn't new. What I don't know yet is your phone system and booking software. I pick up new systems fast, and I'd ask to shadow whoever covers the desk for my first few days so I learn it properly."
Claiming there's nothing to learn, or giving no example at all of dealing with the public.
Get to know them: names, roles and who handles what.
What you give: being reliable, and passing on patterns you notice at the desk.
What you ask for: heads-up on visitors and leave, and cover for breaks.
"Reception works best when I know everyone, so in the first weeks I'd make a point of learning names, roles and who deals with what, so I'm never guessing where to send a call. I stay part of the team by being dependable: messages that are right, visitors who are looked after, and telling people things they'd want to know, like a client who seemed upset on the way out. What I need back is a heads-up. If people tell me about expected visitors, when they're on leave, or when they don't want calls, I can protect their time. And I'd want a clear arrangement for breaks so the desk is never left empty."
Describing the role as just sitting at the front and doing what you're told, with no link to the people behind you.
Situation: what went wrong before they reached you.
What you did: the words and the small practical fix.
Result: how they left, and what you learned.
"At the physio clinic where I worked, a patient arrived soaked because the car park signs sent her to the wrong entrance, and she'd had to walk round the block in the rain. She came in cross and ten minutes late. I didn't start with forms. I said, I'm sorry, those signs catch people out, let me get you a towel and a hot drink. Then I told her physio she was here and asked if they could still see her for the full slot, which they could. When she left she was laughing about it. Afterwards I told my manager about the signs, and we put a clear arrow on the gate so it stopped happening."
A story where you simply followed the rules and the visitor stayed unhappy, with no sign you tried to help.
Welcome: look up, smile, greet within seconds, even if you're on the phone.
Sign in: name, company, host, time, badge, and any safety notes.
Handover: tell the host, offer a seat and a drink, give a real wait time.
"When someone walks in, I look up and smile straight away, even if I'm on the phone, so they know they've been seen. Then I say, Good morning, welcome, who are you here to see? I sign them in with their name, company, who they're visiting and the time, and give them a visitor badge. If the site needs it, I'll point out the fire exits or ask them to read the safety notes. I call the host, tell them their guest has arrived, and tell the visitor honestly how long it'll be. I offer a seat, water or a coffee, and mention where the toilets are. When the host arrives, I introduce them by name. When they leave, I sign them out and collect the badge."
Skipping the sign-in or badge because the visitor seems familiar or trustworthy.
The slip: what went wrong, owned plainly.
The fix: how you put it right for the caller and your colleague.
The new habit: what you now do every time.
"Early in my last job I took a message for a manager from a supplier and wrote the number down in a rush. When he called back, he got a stranger, because I'd swapped two digits. The supplier rang again the next day, a bit annoyed that nobody had come back to him. I apologised, got the number again and made sure the manager called straight away. Since then I read every number and the spelling of every name back to the caller before they hang up, and I always write down when they called and how urgent it is. It adds maybe ten seconds a call, and I haven't had a wrong number since."
Saying you've never made a mistake with a message, or blaming the caller for speaking fast.
Greeting: good morning or afternoon, said with a smile.
Who they reached: the company name, then your first name.
Invitation: a short offer to help, then listen.
"I'd pick up within a few rings and say, Good morning, Brightside Dental, this is Priya speaking, how can I help? The greeting is there because the first word can get clipped as the line connects, so you want that word to be a friendly one, not the company name. The company name tells them they've dialled correctly. My name makes it personal, and it gives them someone to ask for if they call back. Then how can I help hands it over to them. I say it slowly enough to be understood, and I smile when I answer, because it comes through in your voice. And I never answer mid-conversation with someone else."
Just saying Hello, or rushing the company name so the caller can't tell who they've reached.
Who and how: caller's name spelled right, company, number.
What and when: reason, urgency, time of call, best time to call back.
Check: read it back, then send it where it will be seen.
"A good message has the caller's name, spelled correctly, their company if they have one, and the best number to reach them. Then who the message is for, the date and time they called, and what it's about in a sentence. I also ask if it's urgent and when's a good time to call back, and I put my initials so the colleague knows who to ask. Before they hang up, I read back the number and any tricky spelling. Then I send it the way the office actually uses, usually an email or the message system, not a sticky note that falls off a screen. If it's urgent I'll also tell the person directly."
A message with only a name and please call back, or a number that was never read back.
Ask first: may I put you on hold, and wait for the yes.
Check back: return often if the hold is long, and offer a message instead.
Warm transfer: tell the colleague who is calling and why before connecting.
"For hold, I always ask, Can I put you on hold for a moment while I check? and wait for them to say yes. If it's taking longer than I said, I come back and tell them, rather than leaving them listening to music wondering if they've been forgotten. For transfers, I tell the caller who I'm putting them through to and why. Where the phone system allows, I speak to my colleague first and say, I've got Mr Ahmed on the line about his invoice, so the caller doesn't have to repeat the whole story. If the person isn't there, I go back to the caller and offer to take a message, rather than dropping them into voicemail without warning."
Putting people on hold without asking, or transferring blind and hoping someone picks up.
Listen first: let them finish, keep your voice low and steady.
Acknowledge: name the problem back to them without blaming anyone.
Move it on: a next step, and a quieter spot if others are watching.
"At the hotel where I worked, a guest came to the desk furious because his room hadn't been cleaned by the afternoon, and he had a video call in twenty minutes. He was loud, and there was a queue behind him. I let him finish without interrupting, then said, That's not what you should come back to, especially with a call coming up. Here's what I can do right now. I rang housekeeping while he stood there, and offered him a quiet meeting room for his call so he wasn't waiting on the cleaners. I kept my voice lower than his, which usually brings the other person down too. He took the room, and later he stopped by to say thanks."
Telling the visitor to calm down, quoting policy at them, or admitting you argued back.
Go to them: calmly, and apologise for the wait without excuses.
Real information: find out the actual delay and give them a true estimate.
Options: wait, rebook, or another person if one is free.
"I'd go over to them rather than calling across the room, and say, I'm really sorry, you've waited much longer than you should have. Let me find out exactly what's happening. Then I'd check with the person they're seeing and come back with a real time, not a vague Shouldn't be long. If it's another twenty minutes, I'd say so and give them choices: wait with a drink, rebook for the first slot tomorrow, or see someone else if that's possible. Giving them control usually takes the heat out. I'd also have a word with the others waiting so they know what's happening too. From then on I'd tell people about delays when they arrive, before they get to boiling point."
Promising a time you haven't checked, or telling them everyone else is waiting too.
The scene: how busy it was, in concrete terms.
Your method: how you decided who came first and kept others informed.
How it ended: nothing dropped, and one thing you'd do better.
"The Monday after a public holiday at the medical centre was always chaos. One morning I had four people in the queue, two lines ringing, and a delivery at the door. I gave everyone a quick signal first: a smile and a Be with you in one moment to the queue, and I answered each call with a short greeting and asked if they could hold for a minute. The person in front of me came first, unless something was urgent. I signed for the courier in a few seconds so he could go, and put the boxes behind the desk to log later. After that I asked my manager if a second person could cover the phones for the first hour on those days, and we did that from then on."
Saying you just work faster, with no method, or admitting you let calls ring out.
Acknowledge all: eye contact, a quick word, nobody ignored.
Order: finish the person in front unless something is urgent; answer the call briefly.
Close the loop: return to each one and apologise for the wait.
"I'd give the courier a nod and a quick Two seconds, then say to my visitor, Excuse me one moment. I'd answer the call with the normal greeting and ask, Can I put you on hold for just a minute? If it sounded urgent, I'd deal with it there and then. Otherwise I'd finish signing in the visitor, since they're my guest and the first impression matters, and call their host. Then I'd sign for the parcel, which takes seconds, and go back to the caller with a thank you for holding. The key is that all three know within a few seconds that I've seen them. People mind being ignored far more than they mind waiting."
Letting the phone ring out, or turning away from the visitor mid-sign-in to take a long call.
Mindset: the interruption is the work, not a break from it.
Habits: small resets that keep you fresh during the day.
Keep track: how you pick up tasks after being stopped.
"I think the trick is not seeing people as interruptions. The visitor or the caller is the job. The filing is what I do in between. That shift helps a lot. For the fortieth person, I remind myself it's their first time meeting me today, even if it's my fortieth hello. Practically, I take my breaks properly, I keep water at the desk, and if I've just had a difficult conversation, I take one breath before looking up at the next person. For the tasks that keep getting stopped, I keep a running list, so after an interruption I can see exactly where I was instead of trying to remember."
Saying interruptions don't bother you at all, or that you get short with people late in the day.
Situation: who it was and why it felt awkward.
What you said: firm, friendly, and focused on the rule, not the person.
Outcome: how it resolved, and whether anyone backed you up.
"At my last office, a man in a smart suit walked in, said Morning, I'm here for the board meeting, and headed for the lifts. He wasn't on the visitor list. I stood up, stepped towards him and said, Good morning, welcome. Could I just sign you in and let the team know you're here? He said he was running late and knew the way. I said, I understand, it'll take thirty seconds, and everyone signs in, even our directors. I rang the meeting organiser, who'd never heard of him. It turned out he was selling something and hoped to catch people before the meeting. My manager thanked me, and after that we put the board meeting guest list on my desk every time."
Letting someone through because they looked important or were in a hurry.
Stay polite: welcome them and ask them to wait at reception.
Verify independently: call your IT contact using a number you already have, not one they give you.
Decide and record: escort and sign in if confirmed; keep them out and report it if not.
"I'd be friendly, ask for their name, company and who booked them, and ask them to take a seat while I check. Then I'd call our IT lead or facilities manager on the number I already have, not a number on the visitor's paperwork, because that could lead straight back to an accomplice. If IT confirms it, I sign them in, give them a visitor badge and make sure someone escorts them, since the server room isn't somewhere a visitor walks around alone. If nobody can confirm it, they don't go past reception, however annoyed they get, and I'd tell security or my manager. A uniform and a clipboard are exactly what someone would use to get in."
Letting them in because they have a uniform, a badge or a convincing story.
Follow the plan: the building's own evacuation procedure, no lifts.
Take the list: the sign-in book or visitor tablet, grabbed on the way out, never a reason to delay.
Roll call: hand it to the fire warden and report anyone missing; nobody goes back in.
"I'd follow our building's evacuation plan, which I'd learn in my first week. My main extra job is the visitor list, because visitors don't know the exits and nobody else knows they're in the building. So I'd grab the sign-in book or the visitor tablet on my way out, without stopping to print anything, direct anyone in reception to the nearest exit, and not use the lifts. At the assembly point I'd hand the list to the fire warden and help check that every visitor is out, usually by asking their hosts. If someone's missing, I tell the warden or the fire service where they were likely to be. I wouldn't go back in to look, and I'd stop anyone arriving from walking into the building."
Leaving the visitor list behind, or going back inside to search for someone.
Check and call: go to them, speak to them, and call the first aider.
Emergency line: if they don't respond or aren't breathing normally, call the local emergency number straight away.
Manage the scene: keep others back, meet the ambulance, record what happened.
"I'd go straight over and speak to them to see if they respond. At the same time I'd call our trained first aider, or ask someone nearby to fetch them. If the person isn't responding or isn't breathing normally, I'd call the local emergency number right away, not wait for the first aider, ask someone to bring the defibrillator if we have one, and follow what the call handler tells me. I wouldn't try to move them unless they were in danger where they are. Then I'd keep other people back to give them space, let their host know, and have someone ready at the entrance to bring the paramedics straight in. Afterwards I'd write down what happened and when, and fill in an incident report."
Waiting to see if they recover on their own, or trying medical treatment you haven't been trained to give.
What it records: name, company, host, time in and out, badge number.
Why: knowing who's inside in an emergency, security, and a record if something happens later.
Protect it: other visitors shouldn't be able to read earlier entries.
"The log tells you exactly who is in the building at any moment. It records each visitor's name, their company, who they're visiting, the time they arrived and left, and the badge number I gave them. It matters most in an emergency, because in a fire the warden needs to know which visitors to account for. It also matters for security, since it's a record of who was here if something goes missing or an incident happens later. The catch is that it's personal information, so I don't leave a paper book open where the next visitor can read everyone else's names. A digital system or a sheet where earlier entries are covered is better."
Treating the log as paperwork, or not seeing that signing out matters for a roll call.
What it is: someone following a staff member through a secured door without swiping in themselves.
Why it matters: nobody knows they're inside, and no badge means no record.
How to stop it: a friendly question and a clear route to the desk.
"Tailgating is when someone slips through a secure door behind a person who has swiped in, so they never use a badge of their own. It works because staff don't want to be rude and shut a door in someone's face. From reception, if I see someone follow a colleague through without a pass, I'll call out in a friendly way, Hi there, can I help you? Could you just pop back and sign in for me? Most of the time they're a genuine visitor who didn't know. If they ignore me, I let security or my manager know immediately, with a description. I'd also gently remind staff that holding the door isn't doing anyone a favour."
Saying it's not your job to stop it, or that you'd let it go to avoid an awkward moment.
What happened: the clash, and whose mistake it was, honestly.
The person waiting: the apology and the choice you offered them.
The fix: what you changed in how bookings are made.
"At the salon, two clients turned up for the same four o'clock slot with the same stylist. One booked online and one on the phone with a colleague, and the two systems hadn't synced. I apologised to both, then checked who had booked first, which was the online client. For the second client I offered a choice: another stylist straight away, or her usual stylist at five with a free treatment the manager agreed to. She took the five o'clock slot and a coffee. Afterwards I suggested we stop writing phone bookings in the paper diary and put everything straight into the online system, so there was only one place to check. We didn't have a clash after that."
Blaming a colleague or the system in front of the client, or leaving them to sort it out themselves.
Act now: call them as soon as you notice, before they set off.
Own it: a plain apology, no excuses.
Protect both sides: tell the colleague, and hold or find a slot that works.
"I'd call them straight away, while there's still time for them to change their plans. I'd say, I'm really sorry, I made a mistake yesterday and gave you the wrong time. Your appointment is actually at eleven, not two. Can you still make it? If they can't, I'd find the nearest slot that suits them, and if the mistake has cost them something, like time off work, I'd check with my manager whether we can prioritise them. I'd also tell the colleague they're seeing, so they aren't caught out. If I couldn't reach the caller, I'd leave a clear message and tell the team, so whoever's on the desk knows the story when they arrive. Then I'd check how I made the mistake."
Hoping they won't notice, or blaming the system when they arrive.
One source: every booking goes into one system, straight away.
Confirm details: name, contact number, reason, read back date and time.
Reduce no-shows: reminders, easy cancelling, and a list of people who want an earlier slot.
"The biggest thing is one diary. Whether it's a phone call, an email or someone at the desk, it goes straight into the same system while they're still with me, never on a note to type up later. I take the name, a contact number and the reason, and I read back the date and time so we both agree. I leave the buffer between appointments that each colleague needs, rather than booking back to back because the gap looks empty. For no-shows, reminders help most, by text or a call the day before, with an easy way to cancel. And I keep a short list of people who'd like an earlier slot, so a cancellation gets filled instead of wasted."
Keeping bookings in more than one place, or not confirming the time back to the person.
The ask: who wanted what, and why it sounded reasonable.
Your line: what you said, without confirming or denying anything.
The safe route: what you offered instead, such as passing on a message.
"At the GP surgery, a woman called saying she was a patient's daughter and wanted to know what time her mum's appointment was and what it was for. She sounded worried and genuine, but I had no way of knowing who she was, and the patient hadn't given us permission to share anything. I said, I'm sorry, I can't share any details about appointments over the phone, even with family. What I can do is pass a message to your mum or ask her to call you. She was frustrated, but I stayed kind and didn't budge. Later I let the practice manager know about the call, in case it came up again."
Sharing a small detail to be helpful, or confirming someone is a client because the caller seemed nice.
Don't confirm: no schedules, no leaving times, no details about her day.
Offer a route: take a message and pass it to her.
Flag it: if it feels off, let her and your manager know.
"I wouldn't tell them whether she's in or when she leaves. I'd say, I'm sorry, I can't share anyone's schedule, but I'm happy to take a message and pass it straight to her. If they're really a friend, they'll have her number, and a message costs them nothing. I'd take their name and number and tell her about the call, without judging it, because it might be fine. But if they pushed, or wouldn't leave a name, I'd also mention it to my manager. Someone asking when a person leaves the building could be someone she's trying to avoid, and the front desk is often the first place people try."
Giving out a leaving time or daily routine because the caller sounded friendly.
What's said: confirm details quietly, never read personal information out.
What's heard: call people by name only, never say why they're here.
What's seen: screen angled away and locked, sign-in sheet covered.
"Most privacy slips at a front desk are spoken, so I watch my voice first. If I need to confirm a date of birth or an address, I ask the person to tell me, or I point to it on the screen, rather than reading it out for the whole room. I don't say out loud why someone's here, just their name if I have to call them. My screen faces away from the counter, I lock it every time I step away, and papers go face down or in a drawer. I don't leave the sign-in sheet showing other people's names. On the phone, if a call gets personal, I'll keep it brief and call back from a quieter spot."
Only talking about locked filing cabinets and never about what's said or seen at the desk.
The basics: email, calendars, word processing, simple spreadsheets, typing speed.
Desk systems: a booking or visitor system and a phone system you've used.
Learning: how you got up to speed on the last new one.
"Day to day I use email and shared calendars a lot, a word processor for letters and notices, and simple spreadsheets for things like the room booking list or a record of deliveries. I type quickly and accurately, which matters when you're entering details while someone waits. At my last job I used a clinic booking system and a phone system with hold, transfer and a shared voicemail. When I started there, I'd never seen that booking system. I asked for a short walk-through, practised on test bookings in a quiet hour, and wrote myself a one-page cheat sheet for the less common tasks. Within about a week I didn't need it."
Saying you're not really a computer person, or listing tools with no example of using them.
Open: arrive early, check messages and the day's visitors and bookings, tidy area.
During: greet, answer, book, sign in and out, and fit small tasks into quiet spells.
Close: everyone signed out, messages passed on, tomorrow prepared, desk secured.
"I'd get in before the doors open, switch the phones from the night message, and check voicemails and emails that came in overnight. Then I'd look at today's visitor list and bookings, print badges for expected guests and make sure meeting rooms are ready. Through the day it's greeting people, the phones, bookings, deliveries and signing people in and out, and I'd use the quiet spells for filing, restocking or the next day's confirmations. Before I leave, I check every visitor has signed out, pass on any message still waiting, set up tomorrow's list, put the phones on the night message, and lock away anything confidential. A good day is one where nobody waited without knowing why."
Describing only the greeting and phones, with no sense of opening, closing or preparing.
Check and sign: it's for someone here and looks intact before you sign.
Record and notify: log it, tell the person, store it safely.
Caution: don't open other people's post; report anything that looks suspicious.
"Before I sign, I check the name is someone who works here and the parcel isn't damaged. If it is, I note that on the courier's device. I log each delivery with the date, who it's for and who brought it, then message the person so they know it's here. If they're out, it goes somewhere secure, not on the open counter, and anything valuable or confidential gets locked away until they collect it, and they sign for it when they do. I never open someone else's post unless that's been agreed. If a package looks wrong, say leaking, oddly addressed or with no sender, I don't handle it more than I have to and follow the building's procedure for suspicious items."
Leaving parcels on the counter or handing them to whoever offers to take them.
ClapAssist is an AI interview assistant for Mac and Windows. It listens to the interview on your computer and shows you what to say, in short lines you can read while you talk. Your resume and notes are never stored on our servers. It stays out of screen share on every plan; only you can see it.