What Should an AI Receptionist Know About Your Business?

An AI receptionist needs a small, current business reference more than a large pile of documents. The reference should explain what your business does, which questions it may answer, how callers reach the right person, and where its authority ends. Internal information becomes useful only when the assistant also knows whether it may share it.

Quick answer

Create a receptionist reference with approved public facts, intake questions, routing rules, unavailable responses, and a date for review. Keep price exceptions, private customer details, and contractual decisions outside ordinary answering authority. Mark unknown information explicitly instead of inviting the assistant to fill gaps.

Righthand's customer support use case provides a starting point for routing and inquiry handling. The exact phone setup, available business data, and permission rules determine which parts you can use in practice.

Include the facts callers actually need

Start with the questions your team hears repeatedly: services offered, service area, business hours, how appointments are requested, and which department handles an existing job. Supply approved wording where the distinction matters. “We accept inquiries for weekend work” is different from “We provide weekend service.”

For hours, include the time zone and holiday exceptions you currently know. For location, use the public address and approved arrival instructions. For pricing, explain whether the receptionist may quote a published figure, describe a range, or only request an estimate from the team.

Every fact should have an owner. Someone must update the holiday hours or removed service when the business changes. A beautifully formatted reference that nobody maintains can produce confidently outdated answers.

Add routing and identity boundaries

Name the recipient for new business, existing projects, complaints, supplier questions, and billing inquiries. State what information is needed to identify the request, without asking the caller to reveal unnecessary sensitive data.

Treat caller claims as claims. A person saying they are a customer's colleague does not automatically receive the customer's schedule or contact information. The receptionist should follow your approved identity process and escalate when it cannot establish the right to disclose something.

Define the fallback when the recipient is unavailable. This may be a callback request with the caller's preferred window. It should not be an invented response-time promise.

An illustrative business reference

A bike repair shop publishes its opening hours, address, and repair categories. Its receptionist reference adds that repair completion dates require a technician's confirmation; callers can request an assessment but cannot reserve a repair slot through a casual availability answer.

An incoming caller asks whether an unusual component can be repaired today. The assistant can capture the model, issue, and callback preference. Because the reference does not confirm that component or same-day availability, it routes the question to the shop manager.

The assistant has enough context to help without needing to know every bicycle specification. The reference makes the uncertainty visible and supplies a useful next step.

A reference-building brief

Build a receptionist reference from the approved website pages and the current business-hours document. Organize services, public contact details, intake questions, routing, and unavailable responses. Mark each item as approved to share, internal routing only, or needing confirmation. Flag conflicting hours or service descriptions instead of selecting one silently. Do not include private customer records. Show me the draft before using it on calls, and list the owner responsible for future updates.

Review it with whoever currently answers the phone. They will often spot practical omissions, such as the entrance customers should use or the reference number needed to locate a job.

Keep the knowledge base compact

A useful reference can link to detailed material rather than repeating it. Put the immediate conversation rules first: introduce the role, identify the request, answer approved questions, and escalate beyond scope.

Record when a fact was last confirmed. Review the reference after a new service, a change in hours, or an escalation caused by missing information. Do not treat every unusual question as a reason to add a new promise; sometimes the right improvement is a clearer human route.

FAQ

Should the receptionist read our entire shared drive?

Start with approved sources and limited access. Broad access creates more conflicting and private information than most phone tasks need.

Can it answer questions from our website automatically?

Public information is useful input, but review it for currency and intended meaning. A marketing phrase may not establish a booking or pricing policy.

Who should maintain the reference?

Assign a named business owner, with contributors for hours, services, and routing. An unowned reference will drift.

Related resources

Explore voice AI and task delegation for turning your reference into a bounded answering workflow.