Start with the calls that interrupt a job
If you are on a job when someone calls, the next step may be as simple as collecting a usable callback request. Another business may need an office team to receive an assessment request with the property details already recorded.
Choose one call path first: routine new inquiries, overflow when the office is busy, or after-hours requests. Decide which services and locations it covers. A narrow process gives your team something concrete to review before expanding it.
The workflow below is an illustrative design, not a client case study or a claim that it has been installed in your business.
Capture enough information for a useful next step
An intake conversation should collect what your team needs to decide how to respond. Ask the caller to explain the work, then confirm the details that matter. Leave unclear information marked for review rather than filling in an answer.
Vapi's tools documentation describes how a configured assistant can look up information or take an action during a call. That is a platform capability; the information it can access and the actions permitted for your business must be agreed and connected separately.
- Name and a callback number, confirmed with the caller.
- Service location and whether it is within your agreed coverage area.
- Type of work and the caller's description of the problem.
- Preferred contact time and any access details your team requires.
- A clear flag for requests outside the approved intake process.
Give the office a request it can act on
Illustrative workflow: the caller describes a plumbing repair, the assistant checks the configured service area, and the conversation becomes a job request for office review. A connected system then creates or updates the appropriate customer record and alerts the person responsible for the callback.
The record should separate the caller's request from a staff decision. Include the contact details, work description, location, summary, missing information and next action. Agree how existing customers are matched and how a repeat inquiry is handled.
If the request cannot be saved or the alert fails, the workflow needs a visible exception for someone to resolve. Your team should know where to look for unresolved inquiries instead of assuming silence means there was no call.
Keep a requested time separate from a confirmed booking
A caller's preferred time is useful information, but it is not yet an accepted appointment. Decide whether the process collects a callback request, schedules an assessment, or books an approved service. Each needs its own rules and confirmation.
Jobber's documentation illustrates this distinction: requests can be scheduled for an assessment and later converted into a quote or job. This is an example of how a field service system organizes work, not a claim that a Jobber integration is included in every RTS.AI project.
For your setup, define which calendar is authoritative, what availability can be offered, and who handles exceptions. If confirmation is unavailable, record the request for staff follow-up and say that the booking is still unconfirmed.
Sources: Jobber: requests in the Jobber app
Set limits for urgency, advice and human handoff
Agree which requests need a person and what the caller should hear. Do not design the intake assistant to diagnose a fault, promise a technician's arrival or make a safety judgment from an uncertain description.
If live transfer is part of the agreed setup, test it when the destination is busy or unanswered. Vapi documents these outcomes separately from a successful connection. The fallback may be a callback request or another approved route; the caller should hear what actually happened.
AI call intake is not an emergency service. Any instructions for urgent situations need to be approved by the business and kept separate from routine scheduling.
- Give callers a clear way to request a person.
- Confirm coverage hours and who receives escalations.
- Keep pricing, availability and advice within approved limits.
- Review ambiguous requests and incorrect summaries with your team.
Bring your process, then test the whole handoff
Before a build, gather the services you offer, service area, working hours, intake questions, staff contacts and the system where requests should live. Identify which decisions staff must keep.
Test an ordinary inquiry, an existing customer calling again, an address outside your area, an unclear request and an unavailable booking. Follow each one from the conversation through the saved record and staff action. The useful result is a process your office can explain and operate.
RTS.AI's website offers an outbound Voice AI demo call about your business. It shows our own inquiry and follow-up process. Incoming customer calls, job-system connections and scheduling rules for your business are a separate custom scope. You can also turn off the call option and describe your needs in the form.
Common questions
Does this replace the person who schedules our work?
It does not have to. The first scope can be collecting structured inquiries and preparing them for your office. Your team can retain decisions about pricing, crew assignment, unusual work and appointment approval.
Can it book a job directly into our existing system?
That depends on the system, available connection and booking rules. A project may collect a request, schedule an assessment or confirm a permitted appointment. We establish which outcome is supported before describing it to callers.
What happens when the caller is outside our service area?
Choose an approved response during setup. The process can flag the request for review or explain the configured service-area limit. It should not promise coverage your business has not agreed to provide.
Is the website demo an incoming call to my business?
No. When you request the demo and complete the required checks, our Voice AI calls the number you provide. A customer-facing incoming call workflow is designed separately around your business.
Do we have to start with every type of call?
No. Start with one defined call path and the information your staff needs from it. Review the outcomes and exceptions before extending the process.
Sources and further reading
- Vapi: tools for actions during a call
Official product documentation, checked 11 November 2026. Shows configurable actions such as looking up records and booking appointments; it does not establish that a particular client integration is installed.
- Vapi: call transfers and their outcomes
Official product documentation, checked 11 November 2026. Describes transfer modes, unanswered destinations and failures. A transfer attempt does not establish that a person answered.
- Jobber: requests in the Jobber app
Official product documentation, checked 11 November 2026. Explains requests, assessments and conversion to a quote or job. Used as an example of distinct work stages, not as a promise of an installed integration.