Your AI receptionist should ask who is calling, what help they need and how your team can reach them. If the phone number is wrong or the service request is missing, you may not be able to call back or prepare the next step. TQP configures the questions, checks the important details and gets the call record to the person who needs to act.
A long transcript may contain all of this somewhere. Somewhere is an unfortunate place to keep the one detail the dispatcher needs now.
I would judge the intake by the colleague receiving it. Can the bookkeeper choose the right introductory call? Can the dispatcher tell where the job is? Can the law firm's intake coordinator arrange a human review without inviting the caller to tell the whole confidential story to a machine?
This is why I recommend The Quiet Protocol's configured AI Receptionist, from US$449 per month with free setup (normally US$1,495), with no contract, the AI Business OS and call minutes included. We map the approved questions, booking and transfer paths, configure and test realistic call scenarios, then maintain the agreed routing and after-call actions. The work is to make your team's next step easier, not to collect the largest possible pile of information.
Every field needs a reason and a recipient
Start with one ordinary call your business receives. Write the action a person must take after it: review service fit, return the call, arrange an estimate, or offer a defined appointment. Work backwards from that action.
Ask who uses each proposed answer. If nobody can name the decision it changes, leave it out of the first call. A question about annual revenue may help a particular advisory service decide fit; it is unnecessary for an existing client's request to change a meeting. A job address matters to a field-service dispatch; a general location may be enough before deciding whether to offer an introductory conversation.
Your questions can differ by call path. A new prospect and an existing client need different routes. A request for a person should not force the caller through the whole prospect questionnaire first.
For website forms, W3C recommends asking only for information needed to complete the process. I would apply the same discipline to voice intake: collect enough to serve the immediate request, then move deeper collection to the appropriate step. This is our design recommendation, not a claim that a website-form standard certifies a receptionist. W3C forms tutorial
A minimum first-call dictionary
| Field | What belongs in it | Confirmation or boundary |
|---|---|---|
| Contact name | The name needed for the receiving action | Confirm unclear spelling when it affects matching or a professional check; do not silently invent it |
| Reachable contact | Caller-confirmed phone or appropriate email | Read back the route needed for the next step; caller ID alone is not confirmation |
| New or existing request | New inquiry, existing-client request, or another defined route | Use an uncertain state if the caller cannot tell; do not treat caller claims as verified identity |
| Requested help | Approved service category plus a short factual summary | Keep the caller's request separate from an AI interpretation or professional conclusion |
| Location or jurisdiction | Only the detail needed to route or check service coverage | Collect a full site address when that next step requires it; otherwise start smaller |
| Timing stated by caller | Preferred timing or a stated deadline | Record the actual date and uncertainty; flag approved urgent conditions for a person |
| Contact preference | Preferred route, suitable callback time and any need for a discreet message | Record separately from any permissions your business requires for later messages |
These are starting points, not seven questions every caller must finish. Decide which fields each action requires and what happens if a caller cannot or does not want to answer.
Then add the fields your team supplies: record ID, time and source, assigned person, next action, due time and unresolved questions. The caller should not have to explain your staffing chart. The configured route and receiving team should make that assignment.
Define the meaning of a blank. Was the question not asked, did the caller decline, was the answer unclear, or does it not apply? Those are different conditions. A required field should never force the AI to guess in order to finish a record.
- Who is calling: a name your team can use.
- A number that works: repeated back to the caller and confirmed.
- What they need: in their words, not a category the system picked.
- Where: the service address or area, checked against where you work.
- How urgent: what changes if it waits until tomorrow.
- When to reach them: the best time and method, so the callback lands.
The trade changes what enough means
For a plumbing or electrical request, the receiving person may need the site location, type of problem and whether the caller is asking for an estimate or an existing-job update. An address outside the service area changes the next action. A caller's description of danger needs the business's approved escalation instructions, not an AI diagnosis or a promise of dispatch.
A suitable prompt might be: “What help are you looking for, and where is the property? I can pass the request to our team to confirm the next step.” If a visit has not been reserved, the record and spoken confirmation should say so. “Preferred this afternoon” must not become “technician arrives this afternoon.”
For a bookkeeping or accounting prospect, start with requested service, entity type if relevant, general location, and the period or timing they are asking about. A cleanup request for the previous year is different from ongoing monthly bookkeeping. “Records are incomplete” may be useful; collecting the records during a first phone call is a separate decision.
For a law firm, the approved path may need practice area, location, a caller-stated deadline, safe contact details and the party names needed for a firm's conflict review. Ask only what the firm has approved at that stage. An AI receptionist should not declare that there is no conflict, calculate a filing deadline, accept the engagement or offer legal advice.
Those differences should appear in the field rules, not just a different welcome sentence. We configure the call paths around the decision your team can actually make, and route the exceptions to a person.
Sensitive details belong in the right later step
Leave tax identity numbers, account passwords, payment-card details, sensitive documents and detailed legal narratives out of this general first-call dictionary. If your firm needs more information for the next stage, define its approved collection channel, access and retention with the responsible professional.
Canada's privacy regulator describes PIPEDA's limiting-collection principle as collecting the personal information needed for a legitimate identified purpose. Which privacy laws apply depends on the business and jurisdiction; this dictionary is a practical starting point, not a compliance determination. OPC: limiting collection
For US tax practices, the IRS describes written information security plans and the need to assess and safeguard client data. Decide where the first-call note sits within the firm's actual plan before connecting it to tax documents. IRS: protecting client information
For legal intake, the ABA's Model Rule 1.18 addresses prospective-client information even when an engagement does not follow. It is a model rule; firms need to check their applicable professional rules. The useful operational conclusion is to have the firm approve what can be asked before human review, rather than treating “not a client yet” as permission to collect everything. ABA Model Rule 1.18
Access, storage, recording notices and retention also need decisions. Define those with the business before launch. A short intake list helps reduce unnecessary collection; it does not settle the rest of the firm's obligations.
Confirm the details that can send the work to the wrong place
Read back the callback number when a callback is the next action. Confirm an unclear email if the team will use it. Confirm the property or entity detail needed for routing. Ask a short follow-up when “next Friday” or “the end of the month” would otherwise leave an ambiguous date.
Keep caller statements distinguishable from conclusions. “Caller says the return is due on October 15” is a report of what was said. “Return due October 15” can look like a deadline the firm has verified. The same applies to a caller's description of damage or the status of a legal matter.
When an answer remains uncertain, preserve that uncertainty and give the recipient the follow-up question. “Address unclear; dispatcher to confirm before scheduling” is more useful than a plausible wrong address.
A short approved closing could be: “I have your request for bookkeeping cleanup and your preferred callback time. Our intake coordinator will review the request. No appointment has been booked yet.” Use your real receiving process and only a response promise the team can keep.
A complete handoff is shorter than a transcript
Here is a fictional bookkeeping inquiry, presented as a record the intake coordinator could continue. No sensitive documents or identity numbers are needed to understand this next action.
A note someone can use
- Request
- New prospect seeking bookkeeping cleanup for the previous financial year, then possible monthly service. The caller says some records are missing.
- Contact
- Name and callback number confirmed with the caller. Afternoon callback preferred. Relevant contact preference saved in the record.
- Context
- Business entity type collected for the firm's fit review. General location recorded. Accounting software unknown.
- Timing
- Caller requests a discussion this week. No professional deadline has been confirmed.
- Next action
- Assigned intake coordinator to review service fit and offer the appropriate introductory appointment. Due time set by the firm's genuine response policy.
- Limits and open question
- No engagement accepted, appointment booked or documents collected. Coordinator to confirm software and the cleanup period before offering the appointment.
- Traceability
- Unique request ID, intake time and source saved with the note, with access limited according to the firm's approved process.
A transcript can remain available where the approved process allows it, but the recipient should not have to read the whole conversation to discover that the appointment does not yet exist. Give them the useful summary and a way to verify it.
Test missing answers, not only tidy calls
Use labelled fictional calls. Start with an ordinary request, then try an uncertain address, a correction to the callback number, a caller who declines a question and someone who needs a person. Use no real confidential customer information for these checks.
Inspect both sides: what the caller heard and what the receiving colleague sees. Is a preference marked as a request? Did a correction replace the wrong detail? Is the unresolved question visible? Does the task reach the assigned person? Can the colleague continue without asking every question again?
These are acceptance checks to agree for an implementation, not a claim that TQP has tested your business. We configure and test the purchased call path against realistic scenarios, and maintain the agreed handoffs and after-call actions. That continuing work matters when staff, services or the approved questions change.
Bring us your most common call and the one that regularly causes a second conversation just to establish the basics. Choose a configured TQP AI Receptionist. If an accounting firm needs the website, forms, client records and calendars connected as well, our Client Intake & Booking System includes a professional website and the receiving client workflow.
The goal is a useful start for the next person. When the intake gets that right, a colleague can spend their attention on the customer's actual problem instead of locating the phone number in paragraph fourteen.
Frequently asked questions
Which fields should voice AI collect from a service inquiry?
Collect the approved contact route, stated need, location and facts that change the next step. Keep uncertain answers visible and ask for confirmation where it matters. Avoid adding sensitive fields merely because the software can ask them.
Is a call transcript enough for the receiving team?
Not always. The next person needs a usable brief, the promise made and the action to carry. A transcript can be supporting material without becoming the only way to understand the request.
What does TQP configure beyond the conversation?
We define the receiving record and its owner alongside the approved questions. The system carries the context forward so the next employee can act without listening through every call or asking the customer to start again.
We map your call questions, confirmation rules, booking paths and human handoffs, then configure, test and maintain the agreed receptionist. Bring one ordinary request and one call that needs a person.
Configure an AI receptionist your team can work with