Client intake for professional services
Client intake is where a new inquiry becomes a usable record. The caller may have a clear request, a complicated history, or only a vague sense of what help they need. Meanwhile, the professional they want to reach may be with another client. Sending that call to voicemail creates more work: someone must call back, ask the missing questions, and determine the next step from scratch.
An AI phone agent can handle the repeatable part of intake. It can identify the business, explain its role, collect the approved fields, confirm important details, and follow a defined route. It should not decide whether a law firm can take a case, an accountant should accept an engagement, or an advisor should recommend a course of action. Those are human judgments. This page covers the shared intake function; ThunderPhone's industry guides cover how the surrounding workflow changes by field.
A concrete client intake call
Consider a caller contacting a consulting firm after receiving a referral.
Agent: Thank you for calling. I am the firm's AI intake assistant. I can collect information and help arrange the next step. What would you like help with?
Caller: We need to replace our inventory system before our busy season.
Agent: I can record that for the consulting team. What kind of business do you operate, and when does the busy season begin?
Caller: We distribute restaurant supplies. We would like the new system running before October.
Agent: Understood. May I collect your name, company, phone number, and email address? I will repeat the details back to make sure they are correct.
The agent then asks only the firm's approved follow-up questions: current system, locations involved, desired timing, and the best person for a return call. If the inquiry fits the firm's defined intake path, the agent can offer a consultation through Cal.com or Google Calendar. If the caller reports an issue that requires immediate professional review, the agent follows the escalation rule instead of continuing the questionnaire. On an eligible production number, that may be an attended warm transfer, with a private briefing before the recipient accepts.
The resulting record is useful because the caller's contact details, request, timing, and next step were confirmed in one conversation. It is still an intake record, not a professional assessment or a promise that the firm will accept the work.
How to configure the workflow on ThunderPhone
Start with the intake outcome, not a long script. Define which information every inquiry needs, which answers change the route, and which topics must go to a person.
An agent prompt for client intake should cover:
- the opening disclosure and a plain explanation of the agent's role;
- required fields, such as name, organization, contact details, request type, location, timing, and referral source;
- confirmation rules for names, email addresses, dates, and other details that are easy to mishear;
- questions the agent must not answer, including advice, eligibility decisions, estimates, or engagement promises;
- the conditions for scheduling, routine follow-up, cold transfer, or warm transfer; and
- a fallback when the caller declines a question, the request is outside scope, or an integration is unavailable.
Attach approved service descriptions, office policies, and intake instructions from the organization's knowledge base. ThunderPhone supports text, Markdown, CSV, PDF, and DOCX documents, with attachments selected per agent. Keep sensitive professional analysis out of general reference material and tell the agent to escalate when the approved sources do not answer a question.
Choose telephony for the intended stage. An inbound demo U.S. number is suitable for testing, but it is inbound-only and not intended for production. Production numbers can be brought through a supported direct connection or manual SIP configuration. Verified imported numbers support inbound and outbound calling, and an eligible production number is required for attended warm transfer.
Use only the connections the workflow needs. Cal.com or Google Calendar can support the scheduling branch. HubSpot or Salesforce can receive a lead or client record. Google Sheets may suit a simple structured intake queue. Slack can support internal notification, while REST or webhooks can deliver records to an existing system. A remote Zapier MCP server can be added by URL, synchronized for tool discovery, and attached to the agent; custom remote MCP servers must use streamable HTTP.
Before launch, run browser mic tests and AI-caller simulations for straightforward inquiries, missing details, out-of-scope requests, integration failures, and urgent handoffs. Reusable scenarios, graded call logs, and regression suites help keep the prompt's boundaries intact after changes. Simulations are billable real calls, and ThunderPhone shows the charge before a run.
What to measure
Measure whether the intake is usable, not whether the agent kept the caller talking. Review:
- completion of required fields;
- corrections needed for names, contact details, and dates;
- scheduling success and integration failures;
- transfers accepted, declined, or returned to the caller;
- records that staff must rework before follow-up; and
- callers routed to the wrong service or professional.
Pair those results with call grading. A good rubric checks the disclosure, question order, confirmation, boundary language, and final next-step summary. If humans frequently correct the same field or route, revise the prompt or receiving-system rules rather than adding more conversation everywhere.
Where a human remains necessary
A phone agent should not determine conflicts, suitability, scope, risk, price, or professional recommendations. It also cannot repair a calendar, CRM, or downstream system that returns incomplete or contradictory information. Route uncertain cases to staff, preserve a clear fallback when no one answers, and let a person review sensitive records before relying on them.
For narrower workflows, see phone intake forms and appointment scheduling by phone.