What your AI receptionist does
Vulcan Voice is the answering agent inside TradeVulcan. It uses your saved voice preferences, company information, service boundaries and connected workflows to handle customer conversations. A good setup gives every caller a clear next step: a confirmed appointment where supported, a saved service request, or a handoff to your team.
Think of the system as four connected parts. The agent defines the conversation. The answering line receives calls. Your phone system decides which calls reach that line. Your booking system determines which actions can actually be completed. Writing “answer after hours” in a knowledge field does not, by itself, create a phone-system schedule.
Choose your coverage pattern
- First line: send the intended incoming calls directly to the AI agent. Your team handles exceptions and follow-up.
- Backup or overflow: let your people ring first, then route unanswered or busy calls to the AI answering line.
- After hours: use your phone system's schedule to send closed-office calls to AI, with clear next-business-day and escalation instructions.
- Hybrid: combine these patterns by number or schedule, with Call Spark connecting your wider calling workflow.
Start with a limited, well-understood route. Expand only after your team has heard real test conversations and verified the resulting records.
Know the difference between configuration and results
A saved agent profile is not evidence that your business number forwards correctly. A passing voice connection check is not a completed telephone test. An agent saying it will help with scheduling is not a confirmed CRM appointment. Use the test line, call history and saved CRM result to verify each stage.
The current setup offers TradeVulcan lead capture, the Housecall Pro service-request workflow, and configured ServiceTitan live booking. Do not assume every integration shown elsewhere in the ecosystem exposes the same booking actions in this wizard.
Prepare the people behind the agent
Assign an owner for business knowledge, someone to maintain routing, and a person or queue responsible for requests that need follow-up. Decide who may review call records or supervise live calls. Keep the handoff destination separate from a number that routes straight back to the same AI agent.
Use this collection in order for a new deployment, or jump to the KPI and troubleshooting guides for an existing one. Examples are starting points to adapt to your actual policies—not new promises to make to customers.