--- title: "Voice" url: "https://fieldcamp.ai/voice/" date: "2026-08-11T11:50:27+00:00" modified: "2026-08-18T13:04:55+00:00" type: "WebPage" resource: "https://fieldcamp.ai/voice/" timestamp: "2026-08-18T13:04:55+00:00" author: name: "Jeel Patel" word_count: 1837 reading_time: "10 min read" summary: "FieldCamp Voice" description: "FieldCamp Voice is an AI voice agent platform for field service ops. It looks up the caller, qualifies the job, and books a technician through AI Dispatcher." keywords: "AI voice agent platform for field service" language: "en" schema_type: "WebPage" --- # Voice _Published: August 11, 2026_ _Author: Jeel Patel_ FieldCamp Voice # FieldCamp Voice — the voice platform that dispatches, *not just talks.* FieldCamp Voice is a standalone voice AI platform built for field operations. It looks up the caller in your system before it answers, qualifies the job, and books it through FieldCamp AI Dispatcher against technician skills, zones and drive time. Generic voice platforms hand you an API and a blank page. This one already knows what a work order is. Inbound and outbound, on your existing phone numbers, writing into the system you already run. [Start free](https://voice.fieldcamp.ai/auth/signup)[Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min)Buy it on its own, or as FieldCamp AI Receptionist, ready to answer. 7 Telephony providers, including your own Asterisk PBX 2-way Sync with the field service system you already run 31 Language, speech and voice providers, swappable 01 Knows who is calling ## It pulls the record *before it says hello.* Most voice agents start every call from nothing, then spend the first minute asking things you already know. FieldCamp Voice [fires a lookup into your CRM or field service system](https://docs.fieldcamp.ai/ai-agents/voice-agents) the moment the phone rings, and merges what comes back into the conversation before the first word. The agent already has the service address, the equipment on file, the open balance, the last visit. Callers do not repeat themselves, and the call is shorter — which is also what it costs. Incoming callringing+1 480 555 0142 Marisol Reyes Known customer since 2019 ✓ Record foundin 240msMerged into the call context before the agent speaks. Pulled from your systemJobber`customer`Marisol Reyes`service_address`4418 E Presidio Rd, Mesa`equipment`Trane XR14 · installed 2019`last_visit`Mar 4 — capacitor replaced`balance`$0.00`plan`Comfort Club · active“Hi Marisol — is this about the Trane unit again?” 02 Qualifies the lead ## Every call comes back *as structured data.* [A transcript](https://docs.fieldcamp.ai/ai-dispatcher/reviewing-call-recordings-and-summaries) is a record. Structured fields are something you can route on. You define what each step of the call must capture — urgency, equipment, budget, decision maker, whether anyone in the home is at risk — and the agent extracts it as typed values while it talks. Qualified work goes onto the board. Everything else goes to a queue, a pipeline stage, or a person, on rules you set. What the caller saidUpstairs unit stopped blowing cold about an hour ago. It's a four ton, the split system out back. Thermostat says eighty nine in here. My wife has COPD so she really can't be in this. Yeah, I can approve whatever it needs. What came back6 fields`urgency`enumemergency`equipment_type`stringSplit system, 4 ton`indoor_temp_f`number89`occupancy_risk`booleantrue`decision_maker`booleantrue`service_plan`stringComfort ClubTwo fields flagged. This one routes to tonight, not the morning queue. 03 Books through AI Dispatcher ## The part *nobody else does.* Voice platforms book a calendar slot. An empty box on a grid is not a scheduled job. FieldCamp Voice books through FieldCamp AI Dispatcher, live on the call. It [matches the job to a technician by skills and certifications](https://docs.fieldcamp.ai/ai-dispatcher/what-is-ai-dispatcher), keeps them inside an allowed zone, and sequences the day around drive time. When the day changes, the board re-optimizes. A confirmed appointment never moves. [How FieldCamp AI Dispatcher decides](/ai-dispatcher/) Assigned0.9sTechnician Andre Coulter EPA 608 · Mesa zone · 5 of 8 jobs Tonight, 9:00 – 11:00pm Held pending dispatcher confirmation Why✓EPA 608 certification✓Inside Mesa zone✓Capacity tonight–Shortest driveWes is 5 min closerClosest is not the answer. Certified, in-zone and with room is. 04 Outbound campaigns ## The same agent *can call out.* Answering the phone fills half a board. The other half is the list nobody has time to work. Load a list and FieldCamp Voice runs the campaign — maintenance renewals, unsold estimates, seasonal tune-ups, appointment confirmations — with pacing, concurrency limits and retry rules you control. Pause it, resume it, watch it. Answered calls route into the same qualification and dispatch path as an inbound one. Spring maintenance renewalsRunning412 of 780 called53%96 Booked 38 Callbacks 6 At once Pacing and retry rules are yours. Pause it any time. OutcomesEllery DanforthBooked · Tue 8-10aSunil RamaswamyBooked · Wed 1-3pTomasz WierzbickiCallback requestedDelphine OkaforNo answer · retry 2Harlan BootheDeclinedBooked calls route through AI Dispatcher, same as an inbound one. 05 Connects to what you run ## Your system of record *stays your system of record.* FieldCamp AI Dispatcher is the integration layer, and FieldCamp Voice runs on top of it — which is why the agent can book into whichever system you already use. Jobs sync both ways, so your dispatchers keep working where they always have. Leads flow in from the places you already pay for them. Field service systems - Jobber - Salesforce Field Service - ServiceTrade - Microsoft Dynamics 365 - Housecall Pro (read-only) - ServiceTitan (job import) Lead sources - Angi - Thumbtack - Website forms - Google Local Services - CSV lists Housecall Pro is read-only today. Angi and Thumbtack are on the roadmap; every other connector listed is live. 06 Build it from your AI tools ## Design the call flow *in a conversation.* FieldCamp Voice ships an MCP server. Point Claude, Cursor, or any MCP client at it and your coding agent builds the agent with you. List your agents, read one back as TypeScript, change the triage rules in plain language, save it as a draft. The same API key works for the [REST API](https://docs.fieldcamp.ai/api-reference/authentication) and for MCP. There is a [visual builder](https://docs.fieldcamp.ai/ai-agents/creating-and-configuring-agents) too — most people end up using both. ▤after-hours triage rulesour after-hours agent keeps booking non-emergencies onto the same night. route commercial to the on-call dispatcher instead Reading the agent now — it has one triage node with no commercial branch, which is why everything lands on tonight's board. Ran 2 commands › Added a commercial intake path and tightened the emergency bar so routine work books into the next open slot. Ran 3 commands, saved workflow +2 nodes -1 edge › Saved as draft v7. Commercial callers now transfer to the on-call dispatcher, routine residential books into the morning, and emergencies still go out tonight. Test it before you publish. Type / for commandsfieldcamp-voice MCPOpus 5 · High07 Platform capabilities ## Everything a call needs — *start to finish.* Organised the way a call actually happens, not the way a platform is built. 1Before the ring ### Verified numbers Bring numbers you have already registered with your carrier, so your caller reputation carries over. ### Branded call ID Register your business name with your carrier so it shows on the handset instead of an unknown number. ### Knowledge base Your [pricebook and service agreements](https://docs.fieldcamp.ai/online-booking/ai-knowledge-base-and-personas) loaded, so answers are yours. ### Caller lookup The record pulled from your system before the agent speaks. 2On the call ### Book appointments A real slot held through AI Dispatcher, not a box on a grid. ### [Call transfer](https://docs.fieldcamp.ai/ai-dispatcher/voice-assistant) Hand to a person mid-call with the whole conversation attached. ### One agent, any carrier The same agent configuration runs across all [seven telephony providers](https://docs.fieldcamp.ai/ai-agents/agent-connections). 3After they hang up ### Post-call analysis Recording, transcript and the extracted fields, on the job it created. ### Call reporting Call volume, outcomes and duration, filterable by agent and campaign, exportable to CSV. ### [Webhooks and API](https://docs.fieldcamp.ai/api-reference/webhooks) Signed, retried delivery of the whole call to whatever you run. ### Batch calling Feed the outcomes into the next campaign and run it again. 08 Models and voices ## Three layers, *each one swappable.* The best voice model today is not the one that was best six months ago, and it will not be the one that is best six months from now. An agent hears, thinks, and speaks. FieldCamp Voice keeps those three independent, so you can change any one of them without rebuilding the call flow. Around thirty providers are wired in today. HearsSpeech recognitionDeepgramAssemblyAIGladiaSpeechmaticsSarvamAzureThinksLanguage modelAnthropic ClaudeOpenAIGoogle GeminiGrokGroqAWS BedrockAzure OpenAISpeaksVoiceElevenLabsCartesiaRimeLMNTInworldMiniMaxAzure SpeechSwap any slot and the call flow, the prompts and the dispatch logic stay exactly as they were. 09 Telephony and channels ## Keep your numbers. *Keep your carrier.* FieldCamp Voice runs over the telephony you already have. There is no migration onto our carrier, because there is no our carrier. Seven providers are supported including a direct Asterisk PBX connection, with call transfer to a human wherever the provider supports it. [Web chat and messaging](https://docs.fieldcamp.ai/integrations/fieldcamp-whatsapp-setup) run through FieldCamp alongside the voice agent, so an after-hours conversation can start wherever the customer already is and finish on the phone. - Twilio - Telnyx - Plivo - Vonage - Cloudonix - Vobiz - Asterisk (ARI) 10 Or take it configured ## Do not want to build one? *Do not.* FieldCamp AI Receptionist is built on FieldCamp Voice, configured and ready to answer. Same platform, same dispatch, none of the design work. It answers after hours, triages emergencies, and books the job. That is the bar for an [answering service for field service businesses](/answering-service/) today. If you are shortlisting it against the other AI receptionists in field service, the two head-to-head pages are written to be useful even when FieldCamp is not the answer. [FieldCamp AI ReceptionistThe configured agent — after-hours answering, emergency triage, booked through AI Dispatcher.](/ai-receptionist/)[FieldCamp vs Avoca AIBoth answer and book. The real split is named-technician resolution versus CSR coaching.](/ai-receptionist/vs-avoca/)[FieldCamp vs ProBook AIBoth dispatch. ProBook is home services with a ServiceTitan listing; FieldCamp is wider field ops.](/ai-receptionist/vs-probook/) 11 FieldCamp Voice FAQ ## Questions, answered. What is FieldCamp Voice? FieldCamp Voice is a standalone voice AI platform built for field operations. It answers and places calls, looks the caller up in your system before it answers, qualifies the job into structured fields, and books it through FieldCamp AI Dispatcher against technician skills, zones and drive time. It can be bought on its own, without the rest of the FieldCamp platform. How is it different from a general voice AI platform? General voice AI platforms give you speech infrastructure and an empty project. FieldCamp Voice already understands work orders, technicians, skills, zones and service windows, and it books through a dispatch engine rather than into an empty calendar slot. If you are building a voice agent for something other than field work, a general platform is the better tool. Does it work with my existing phone system? Yes. FieldCamp Voice runs over Twilio, Telnyx, Plivo, Vonage, Cloudonix, Vobiz, or a direct Asterisk PBX connection, so you keep your numbers and your carrier. Calls can transfer to a person wherever the provider supports it. Can it make outbound calls as well as answer them? Yes. The same agent runs outbound campaigns for maintenance renewals, unsold estimates, seasonal tune-ups and appointment confirmations, with pacing, concurrency limits and retry rules you control. Answered outbound calls route into the same qualification and dispatch path as an inbound call. Can I build the agent myself? Yes, two ways. There is a visual call-flow builder, and there is an MCP server, so Claude, Cursor or any MCP client can list your agents, read one back as TypeScript, edit it in plain language and save it as a draft. The same API key works for both. Do I need the full FieldCamp platform to use it? No. FieldCamp Voice is sold standalone and runs on top of the field service software you already use, syncing jobs both ways so your dispatchers keep working where they always have. ## Want one that knows your shop? We configure FieldCamp Voice around how your business actually takes calls — your hours, your emergencies, your pricebook, your board. [Start free](https://voice.fieldcamp.ai/auth/signup)[Book a 15-minute call](https://calendly.com/jeel-fieldcamp/30min) --- _View the original post at: [https://fieldcamp.ai/voice/](https://fieldcamp.ai/voice/)_ _Served as markdown by [Third Audience](https://github.com/third-audience) v3.6.1_ _Generated: 2026-08-18 13:04:56 UTC_