Key takeaways
- Write it for the same reason you would for a person: so everyone agrees on the job, and its limits, before the first bad day.
- Use five headings: purpose and duties, hours, authority, escalation, and the measures you will review each month.
- The authority section does the most work: what it decides alone, what it decides within limits and what it never decides.
- Payments and anything patient-specific belong in the never column on a recorded line[2][3].
- Two of the monthly measures, transfers that rang out and unanswered questions, really measure your own team.
Why write one at all
Write a job description for software for the same reason you write one for a person: so everyone agrees, before the first bad day, what the job is and what it isn't. Front-desk work is full of small decisions. In O*NET's survey of receptionists, 88% said they make decisions every day that affect other people, money or the company's reputation[1]. A person learns which of those decisions are theirs by asking. Software only knows the ones you wrote down.
Nobody would hire a receptionist without a written role. SHRM's benchmark puts the average cost per hire at nearly $4,700[4], and a vague job description is one of the quickest ways to waste it. The same discipline applies here, minus the recruiting bill. The page becomes the brief for setup, the checklist for testing and the yardstick for your monthly review. When someone asks whether the phone line should have quoted that price or promised that time, the answer is on one page.
Use the five headings you would use for a hire: purpose and duties, hours, authority, escalation, and how the work is measured. The running example is a fictional two-dentist practice, Brightwater Dental, because healthcare shows the authority limits more clearly than any other industry.
Purpose
Which calls it answers and what a good outcome is
Hours
Overflow, lunch, evenings, weekends, holidays
Authority
Decides alone, within limits, or never
Escalation
Who gets each hard call, the backup, the fallback line
Measures
Six numbers checked monthly from transcripts
Example structure; one page in total.
Purpose and duties
Start from the duties of the human role and cross out what doesn't apply. BLS lists the core receptionist duties as answering the phone and taking messages or forwarding calls, scheduling and confirming appointments, greeting and checking in visitors, entering customer information and handling correspondence, and adds that receptionists in medical and legal offices may handle confidential data[5]. Greeting visitors stays with people. Each of the rest needs a line saying how far the software goes.
| Section | What it says |
|---|---|
| Purpose | Answer every call to the main line that the front desk can't take, give accurate office information, and get each caller to the right person or a clear message. |
| Hours | Overflow after four rings during opening hours, the lunch hour, evenings and weekends. |
| Duties | Hours, holiday closures, address, parking and patient-portal directions; whether the practice takes new patients and which insurance plans it accepts, from the approved list. |
| Hands off | Anything about a specific patient: appointments, results, bills, refills. These go to the front-desk line, or become a message with name and callback number only. |
| Never | Ask about symptoms or health details, give clinical advice, take card numbers, or promise an appointment time. |
| Emergencies | If a caller describes an emergency, tell them in the approved words to hang up and call 911. A caller in dental pain is offered the urgent line the practice chose. |
| Reports to | The office manager, who reads the summary emails daily and runs the monthly review. |
Notice how much of the dental version is about what the line won't do. That isn't caution for its own sake. Before an outside service handles patient information for a practice, HIPAA requires the practice to get satisfactory assurances from that business associate, documented in writing[2], and AssistCall does not sign business associate agreements today. So the job is office information, new-patient questions and routing, with patient-specific work kept at the desk. A plumber's or a salon's version would include booking straight into the schedule; this one doesn't.
Hours and coverage
Say exactly when the line answers and how calls get there. The business forwards its number all day, after hours on a schedule, or as overflow when the desk doesn't pick up. Write the ring count for overflow, the after-hours window, lunch cover and what happens on holidays. Brightwater uses overflow plus lunch and evenings, which leaves every call the desk can take with the desk.
Write down the staffing reason too, because it changes the review. About 62% of dentists named staffing shortages as their biggest challenge for 2025 in an ADA survey[6]. If the line exists to cover a vacancy, the monthly question is whether callers are still getting through; if it exists to catch the lunch hour, the question is whether lunch calls still go to voicemail.
Authority: what it may decide alone
This is the section owners skip and most problems trace back to. For each kind of decision, choose one of three levels: decides alone, decides within limits, or never decides. Receptionists themselves vary widely here: 40% told O*NET their job gives them a lot of freedom to decide without supervision, 34% some freedom and 14% limited freedom[1]. Your SI Employee's level should be set on purpose, not inherited from whoever happened to set up the account.
- Decides alone: answers from the approved facts; books a bookable job into an open slot, where booking is part of the job; moves or cancels a caller's own booking; takes a message.
- Decides within limits: quotes only the prices on the list, exactly as written; offers the closest open times when a requested slot is taken; marks a message urgent when it matches the urgent list.
- Never decides: discounts, refunds or exceptions to policy; diagnosis or advice beyond approved safety wording; anything that needs a license; arrival or completion times.
Payments belong in the never column on any recorded line. Card industry guidance for telephone payments says sensitive authentication data, which includes the security code a caller might read out, should not be stored after authorization and must be made unrecoverable if it is recorded[3]. A call that is recorded and transcribed is the wrong place for a card number, so payments go to staff, at the desk or through the payment method the office already uses.
Escalation: who gets the hard calls
Escalation rules are the human team's duties written from the phone line's side. For each type of call that needs a person, say whether it is transferred or taken as an urgent message, and what the caller hears if nobody answers. The simplest setup is one approved transfer number for the urgent path, with everything else as messages; keep that number to a phone that will really be answered at those hours.
- Caller
- SI Employee
- System
- Your team
01Caller
Caller asks for urgent help
Says they are in pain and need to be seen; no health details are asked.
02SI Employee
Urgent rule applies
Offers the practice's urgent line, in the approved words.
03System
Plain transfer
Rings the urgent mobile the practice chose.
04System
Nobody answers
The call comes back to the line.
05SI Employee
Caller told plainly
Hears that nobody could be reached and who will call back.
06Your team
Urgent message emailed
Name and number only, marked URGENT, read by the dentist on call.
Example. A transfer is plain: whoever answers talks to the caller straight away, with no spoken briefing.
Write the fallback for every transfer. A transfer that rings out is not a failure if the caller is told plainly what happens next and the urgent email reaches someone who reads it at night. It is a failure if nobody owns that inbox after 6 pm. The transfer target can't be the main line that forwards to the software, because the call would loop, so name a mobile or a direct line.
Same headings, other businesses
The headings stay the same across industries; the lines under them change with what is live for that kind of business and what can go wrong on its calls. Three short contrasts show how much.
- A plumbing company: duties include taking down the job, address and urgency, and booking routine work such as drain cleanings into one tested schedule. Escalation runs to the on-call plumber, then a backup, then a clear callback promise. Authority stops at any price the owner hasn't listed.
- A salon or day spa: duties include booking open slots and moving or cancelling a client's own appointment. Deposits, gift cards and redo requests stay with the desk. Authority stops at exceptions to the cancellation policy.
- A law firm: duties include asking the intake questions the firm signs off for one practice area, including the names needed for a conflict check. Escalation can run through up to three destinations with a tested fallback. Authority never extends to saying whether a case is worth taking, or promising that a lawyer is available.
If your version reads like any of these, start from it. If it reads like none of them, that is often a sign the job is mostly judgment, and the line should do less: answer the basics, take clean messages and hand everything else to a person.
A blank version to copy
Fill in each line in plain sentences. Where a line doesn't apply, write not part of this job rather than deleting it, so the gap is a decision and not an oversight.
- Purpose: answers [which calls] so that [what a good outcome is for the caller and for us].
- Hours: [all day / after hours from __ to __ / overflow after __ rings], plus [lunch, weekends, holidays].
- Duties: answers questions from the approved facts list; [books / takes booking requests for] [which jobs]; takes messages for [names].
- Hands off: [call types] go to [number or person]; [call types] become a message.
- Never: [list, including payments, advice that needs a license, and promises about timing].
- Escalation: urgent means [definition]; transfer to [approved number]; if nobody answers, the caller hears [words]; everything else becomes an [urgent / normal] message for [names].
- Reports to: [name], who reads summaries [how often] and runs the monthly review.
- Measures: answered rate, right outcome, details correct, transfers that rang out, unanswered questions, unapproved statements.
How the work will be measured
End with the numbers you will check each month, and who checks them. Every call leaves a recording, a transcript and a summary, so each measure can be counted rather than guessed.
| Measure | How to check it | Example target |
|---|---|---|
| Calls answered in its hours | Call log against the forwarding schedule | Every forwarded call answered |
| Right outcome | Read 20 transcripts a month | At least 9 in 10 handled as the rules say |
| Details correct | Names, numbers and dates in the summaries | No uncaught error in a callback number |
| Transfers that rang out | Urgent emails after a failed transfer | Each one returned within the hour |
| Unanswered questions | Messages asking something not on the facts list | Each gap added within a week |
| Unapproved statements | Anything said that isn't in the facts or rules | None |
Two of these really measure your team. A transfer that rings out is a staffing question, and an unanswered question is a gap in your own facts list. That is the honest value of a job description: it shows where the software ends and the business's own habits begin. The monthly scorecard turns these measures into a short review, and training it on your business knowledge covers closing the gaps it finds.
Review the description whenever the business changes, not once a year. A new service, a second location or a change in who covers evenings all change the job. The split of roles with your staff is the companion page, and what front-desk turnover costs is worth reading if a vacancy is the reason you are writing this. To compare with a human role, see the dental receptionist job description; the dental practice example shows this scope at a three-chair office.
Frequently asked questions
Isn't this just a list of settings?
No. Settings say how the line behaves; the job description says why, who it reports to and how it is judged. Settings change often. The description changes when the business does.
Who should write it?
The owner, with whoever runs the front desk. The owner decides authority and escalation; the desk lead knows which calls cause trouble.
Should staff see it?
Yes. It tells them which calls will now reach them as transfers or messages, and which jobs are still theirs. That conversation goes better with one page in front of everyone.
How long should it be?
One page. If the authority section runs longer than the duties, simplify the rules before adding more of them.
Does it change when I add a service?
Yes, together with the facts list and any booking rules. Update all three at once, then make a test call about the new service.
References
O*NET OnLine (U.S. Department of Labor, Employment and Training Administration) (2026). 43-4171.00 - Receptionists and Information Clerks (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (2026). 45 CFR § 164.502 - Uses and disclosures of protected health information: General rules (opens in a new tab) ↑
PCI Security Standards Council (2018). Information Supplement: Protecting Telephone-Based Payment Card Data (version 3.0) (opens in a new tab) ↑
Society for Human Resource Management (SHRM) (2022). The Real Costs of Recruitment (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2025). Receptionists: Occupational Outlook Handbook (opens in a new tab) ↑
ADA News (American Dental Association) (2025). Five years later: Staffing shortages, infection control since the COVID-19 pandemic (opens in a new tab) ↑