Key takeaways
- A confident guess is the expensive option: a made-up ship date or a price without its fees can break consumer rules as well as trust[2][3].
- Use three moves in order: admit it in one sentence, name who will find out, and commit to a time you control.
- Promise a callback window, not an answer time, and say which number you will call from, because most people let unknown numbers ring[4].
- Log every question nobody could answer and turn the repeats into approved answers each week.
- Automated answering should follow the same rule: answer from approved information, or say so and take a message for a person.
Why a confident guess costs more than an honest pause
The moment comes several times a day at any front desk. A caller asks something specific, such as whether a part will be in by Thursday, whether their plan covers a certain visit, or what the total will be once the fees are added, and the person holding the phone has no idea. There is a half-second pause, and in it the temptation to guess. Guessing feels like good service because it ends the awkwardness. It is usually the most expensive thing you can say.
A wrong answer does not stay on the phone. A guessed delivery date becomes a customer who rearranged their week around it. A guessed price becomes an argument at the counter. Some guesses also run into rules: under the FTC's mail, internet and telephone order rule, a seller needs a reasonable basis before stating or implying that an order will ship within a certain time[2], and California's hidden-fee law bars offering a price that leaves out mandatory fees[3]. Neither rule makes an exception for a new hire who was trying to be helpful.
Not knowing is also normal, and staff should hear that from the manager rather than work it out alone. Customer service reps typically get two to four weeks of on-the-job training[1], and Gallup found only 12% of employees strongly agree their organization does a great job onboarding new people[5]. In O*NET's survey of the occupation, 26% of customer service reps said the job gives them no freedom to make decisions without supervision, and another 30% reported limited freedom[6]. Most people answering business phones are not supposed to decide refunds, exceptions or diagnoses. The skill worth teaching is what to say in the ten seconds after you realize you don't know.
Admit, own, commit: the three-part answer
Every good version of "I don't know" has the same three parts, in the same order. Admit it plainly in one sentence. Own the next step by naming who will find out. Commit to a time you control. Leave any part out and the caller fills the gap with their own worst guess.
- Admit: "That's a fair question, and I don't want to guess at it." One sentence, then move on. Three apologies in a row make the caller think the answer is bad news.
- Own: "Our service manager, Dana, handles warranty questions. I'm sending it to her now." A name or a role tells the caller the question has somewhere to go.
- Commit: "I'll call you by 3 today with the answer, or with where it stands if we're still waiting." The promise is about when you will call, not about when the answer will exist.
Tone matters more than the exact words. Keep your voice level and drop the hedges that sound like guessing anyway: "I think", "it should be fine", "probably by Friday". Callers hear those as commitments and repeat them back to you later. And never shrink yourself to explain the gap. "I'm only the receptionist" tells the caller they rang the wrong person; "I'll get you to the person who knows" tells them they rang the right place.
| Situation | Say this | Avoid | Why it works |
|---|---|---|---|
| You have no idea | "I don't want to guess at that. Let me find out properly." | "Hmm, I think so?" | A guess said with a question mark still counts as an answer |
| Someone in the building knows | "Dana knows this one. Can you hold two minutes, or shall I call you back by 11?" | "Let me transfer you" with no explanation | The caller knows who, how long, and has a choice |
| The answer is a price | "I can give you the exact total once we've seen it. Here's what the visit fee covers." | A number off the top of your head | Quoted prices are remembered, and some states require all mandatory fees in them |
| Nobody knows yet | "The supplier hasn't confirmed. I'll call you Thursday morning either way." | "Should be this week" | A dated check-in beats an estimate that quietly slips |
| It needs a professional judgment | "That one is for the technician. Let's book a slot so they can look properly." | "That's nothing to worry about" | Staff stay inside their role and the caller gets a real assessment |
| The caller pushes for a guess | "I'd rather be right than quick on this. You'll hear from me by 4." | Giving in so the call can end | Holding the line once is easier than unwinding a wrong promise |
Scripts for the calls that stump new staff
Write these out and keep them next to the phone for the first month. They are short on purpose: the caller should hear one clear sentence and a next step, not a speech about how busy everyone is.
- Order or parts status: "I can see the order, but not a confirmed arrival date. I'm emailing the supplier now, and I'll call you tomorrow by noon with what they say."
- Insurance or coverage: "Coverage depends on your plan, and I don't want to tell you yes and be wrong. Our billing coordinator can check it today. What's the best number for her to reach you after 2?"
- Policy exceptions: "That's a decision for the manager, not me. I'll put it to her this afternoon with your details, so you don't have to explain it twice."
- Technical questions: "Rather than guess over the phone, let's get it in front of someone who can see it. I have Thursday at 9 or Friday at 2."
- Questions about another customer or a staff member: "I can't share that, but I can pass on a message." Here "I don't know" is the wrong phrase; say what you can do instead.
Example: a caller asks an auto repair shop whether the grinding noise in their car is safe to drive with. The new service advisor doesn't know, and nobody would without seeing the car. The right answer books a diagnostic slot, and the shop's written policy tells the advisor what to say if the caller mentions brakes, steering or smoke: don't drive it until it has been checked. The six-bay auto repair example shows how a shop can write those boundaries down so every caller hears the same thing, whoever picks up.
The follow-up promise you can actually keep
Most of the trust is won or lost after the call. A caller forgives "I don't know" easily. They do not forgive "I'll call you back" followed by silence. Three habits keep the promise honest.
- Promise a window you control. "By 3 today" is in your hands; "as soon as the supplier replies" is not. If the answer isn't in by 3, call anyway and say so.
- Write it down before you hang up: name, number, the exact question in the caller's words, who owns it and the deadline. A promise that lives only in your head is gone by lunch.
- Tell them the number you'll call from. In Pew's survey, 80% of US adults said they generally don't answer calls from unknown numbers, and 67% said their habit is to let them go to voicemail and check the message[4]. Say "We'll call from the office line", and when you have the answer, leave it on the voicemail itself.
- Caller
- Your team
- System
01Caller
Asks a specific question
A parts date, a coverage check, a price with fees, an exception to policy.
02Your team
Admits it, names an owner
One sentence, no guess, then who will find out.
03Your team
Agrees a callback window
Confirms the number and the latest time the caller will hear back.
04System
Logs the open question
Caller's words, owner and deadline go on the open-questions list.
05Your team
Calls back on time
With the answer, or with where it stands and the next check-in.
Example flow for a small office. The log can be a shared spreadsheet; what matters is that every promise has an owner and a time.
If you are choosing between a short hold and a callback, use one test: can you name the wait? A two-minute check with someone in the building is fine on hold. If you can't say how long it will take, offer the callback instead; scheduled callbacks instead of hold covers how to run them without dropping any.
Turn every "I don't know" into next week's answer
The same handful of questions stump people over and over. In O*NET's task list for customer service reps, passing unresolved issues to the department that owns them and then checking the problem was actually fixed are both rated core parts of the job[6]. An open-questions log does both, and as a bonus it shows you exactly what your front desk was never taught.
Log it
Every question nobody could answer goes on the list during the call, even if it was solved ten minutes later.
Route it
Each entry gets one owner: billing, scheduling, the manager, a technician. Never just "the office".
Close the loop
The owner answers the caller by the deadline, then records the answer they gave next to the question.
Promote repeats
Any question that comes up twice in a month goes onto the front-desk answer sheet, in approved wording.
Review weekly
Fifteen minutes on Friday: what came up, what's still open, which answers have changed.
Example: a two-person front desk logs nine open questions in its first week. Four are about a new payment-plan option nobody briefed them on, two are parts dates and three are one-offs. One line on the answer sheet removes almost half of next week's "I don't know" moments. The gaps are rarely random; they cluster around whatever changed most recently, which is why the weekly review matters more than the log itself. Keep the answer sheet with your caller FAQ list so staff have one document, not two.
The same rule for automated answering
Whatever answers your phone, the rule should not change. An SI Employee answers from the information the business approves, such as hours, services, service area and the fees it chooses to share. When a question falls outside that, it says so instead of improvising, takes the caller's details and the question in their own words, and the summary reaches the person you choose by email, with the recording and transcript in the account. A person then makes the callback with the real answer.
That boundary is worth testing before anything goes live. Ask it the questions your new staff get wrong: a price with fees, a coverage question, a diagnosis. How an AI receptionist works explains where the answers come from, and the pros and cons from the front desk covers what to keep with people. For trade businesses, the home services guide to answering "how much do you charge?" works through the price question in detail.
Pair these scripts with the wording for when the owner isn't available and the rules in call screening for businesses. Together they cover most of the calls where the honest answer is "not me, not yet", and they give a new hire something better to say than a guess.
Frequently asked questions
Is it unprofessional to say "I don't know" to a customer?
No. Guessing and being wrong does far more damage. What sounds unprofessional is stopping there. Pair it with who will find out and when the caller will hear back.
Should I put the caller on hold or call them back?
Hold if you can name the wait and it is a couple of minutes at most. If you can't say how long it will take, offer a callback with a time window and confirm their number.
What if the callback deadline arrives and I still don't have the answer?
Call anyway. Say what you have done, what you are waiting for and when you will call next. A missed deadline with no call is what loses the customer, not the delay itself.
How do I handle a caller who insists on a rough guess?
Hold the line once, politely: you would rather be right than quick, and they will hear from you by a set time. If you do give a range, make it one you can stand behind and say what it depends on.
Can an AI phone system say it doesn't know?
A well set-up one should. It should answer only from approved information, say plainly when something isn't covered and take a message for a person instead of inventing an answer. Test it with questions you know it can't answer before you forward real calls.
References
U.S. Bureau of Labor Statistics (2025). Customer Service Representatives: Occupational Outlook Handbook (opens in a new tab) ↑
Federal Trade Commission (2011). Business Guide to the FTC's Mail, Internet, or Telephone Order Merchandise Rule (opens in a new tab) ↑
California Department of Justice, Office of the Attorney General (2024). SB 478 - Hidden Fees (opens in a new tab) ↑
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) ↑
Gallup (2018). Why the Onboarding Experience Is Key for Retention (opens in a new tab) ↑
O*NET OnLine (U.S. Department of Labor, Employment and Training Administration) (2025). 43-4051.00 - Customer Service Representatives (opens in a new tab) ↑