InstaNexus AI Setup: What an AI Receptionist Needs to Know About Your Shop
A shop owner evaluating an InstaNexus AI setup is really asking one question: what does this thing need from me before it can answer my phone the way my best dispatcher would? This post is the honest answer. It is a checklist of the inputs an AI receptionist needs about your business — service menu, calendar rules, escalation tree, FSM integration, and a few things owners forget — so you can walk into any vendor demo knowing exactly what to bring to the table.
The framing matters. Different vendors structure their setup process differently, and the right path for your shop will depend on your call volume, your FSM, and how much depth your trade requires. The inputs themselves are universal. Get them clear in your head and the rest of the conversation goes faster.
What an InstaNexus AI setup actually requires
Every AI receptionist needs the same five categories of information about your business before it can take a call you would put your name behind. The proportions shift by trade — a dental office spends more time on insurance intake, a roofer spends more time on storm-surge script branches, an HVAC shop spends more time on emergency-versus-schedulable triage — but the buckets are fixed:
- Service menu — what your shop does, what it doesn’t, and where you draw the lines.
- Calendar and dispatch rules — what gets booked, how long it takes, and which truck or chair it lands on.
- Greeting, hold, and escalation language — what the AI sounds like, in your voice.
- Pricing posture per call type — when the AI quotes a number and when it defers to the on-site visit.
- FSM and notification integration — where booked jobs land in your system of record.
We will walk each one. Skim or read in order; the order matters because each input depends on the one above it.
1. Service menu — what your shop does and doesn’t do
The service menu is the single highest-leverage input. It is the difference between an AI that confidently answers “yes we can work on that, when would you like us out” and one that says “let me check with someone and call you back.”
The four things a good service menu captures, regardless of trade:
- What you service. For HVAC, the refrigerants, brands, and system types. For roofing, the materials and pitches. For plumbing, the residential vs commercial split and the equipment you carry on the truck. For dental, the procedures in scope and the procedures you refer out. For auto, the makes, models, and service types. For general contractors, the project types and budget range you take.
- What you don’t service. The shorter and more useful list. The AI politely declines out-of-scope calls and offers a referral instead of leaving the caller hanging.
- Service area by ZIP. A clean list of every ZIP you drive to, plus any “only in peak season” ZIPs and any hard-no ZIPs.
- Emergency vs schedulable definitions. The one-page decision tree of what counts as an emergency in your trade. For HVAC: “no cool in July with elderly or infant in the home = emergency slot.” For plumbing: “water actively running and shutoff failed = emergency dispatch.” For roofing during storm season: “active leak with interior damage = same-day tarp crew.”
If you cannot write these down today, the AI cannot ask the right next question on the call. Sit with your dispatcher for an hour and write them down before you evaluate any AI receptionist — including ours.
2. Calendar and dispatch rules
Calendar wiring is usually the second-scariest part for owners and usually one of the simpler steps in practice. The AI needs to know:
- Hours of operation — including after-hours and weekend coverage rules.
- Job-type duration. How long a diagnostic takes versus a full estimate versus a tune-up. The AI books the right block, not a generic 60-minute slot.
- Buffer rules. Drive-time buffer between jobs (typically 30 minutes in suburban markets, 45 in rural), plus any end-of-day paperwork buffer.
- Tech or chair routing. Which techs are certified on what, which dental chairs handle which procedures, which auto bays handle alignments versus diagnostics.
When all of that is wired, the AI books directly into the calendar on the call — no message, no callback, no “let me check with dispatch.” That is the mechanic that turns missed calls into booked jobs.
3. Greeting, hold, and escalation language
This is the step where the AI stops sounding like software and starts sounding like your shop.
Greeting. “Thanks for calling [Shop Name], this is Nova, how can I help you today?” reads very differently from “You have reached [Shop Name] HVAC, this is the automated assistant.” The first books more calls because it does not announce “you are talking to a robot” in the first four words. Pick a greeting line that sounds like the person who currently answers your phone on their best day.
Hold language. For the rare moment the AI is pulling calendar data or looking up a ZIP, there is a 2-to-4-second hold phrase. “Let me check that for you” works better than silence. You pick the wording.
Escalation phrase. The exact phrase the AI says when a call is outside its scope and needs to escalate to a human. Default: “Let me get one of our dispatchers on — can I have them call you back within 15 minutes?” Most shops edit this to match how their owner or lead dispatcher actually talks.
4. Pricing posture per call type
The question every owner asks: what does the AI say when a caller asks “how much will this cost?”
There are three answers, and you pick one per call type:
| Call type | Pricing posture options |
|---|---|
| Diagnostic fee | Quote the flat fee (“$89 diagnostic, waived if you proceed with repair”) |
| Repair estimate | Do not quote, book the diagnostic |
| New install or replacement quote | Do not quote, book the in-home estimate |
| Tune-up / maintenance | Quote the flat fee or membership price |
| After-hours emergency | Quote the after-hours trip fee, if you have one |
Five minutes of clicking through your matrix and the AI knows when to say a number and when to book the visit. This is the part shops over-worry about; in practice, callers accept “our tech will quote on site” on every call that is not a flat-fee diagnostic.
5. FSM and notification integration
This is where the question can AI integrate with ServiceTitan or Housecall Pro stops being abstract. An AI receptionist’s job does not end when it captures a lead — the booked job has to land in the system of record your dispatcher already lives in.
Common integrations across the trades:
- ServiceTitan — new customer record, new job, assigned dispatch board, notification to the on-call tech.
- Housecall Pro — new estimate or job with source-of-lead tagged.
- Jobber — new client + request, routed to the right branch.
- Google Calendar — for shops that run lightweight, a dedicated calendar with the AI as the only write-account.
- Dentrix, Open Dental, or Eaglesoft for dental offices, with a scheduling portal hand-off rather than direct write when PHI is in scope.
Two things to confirm with any AI receptionist vendor — including us — before signing:
- What gets written? Customer record, job code, address, equipment, source-of-lead, technician assignment? Or just a calendar slot?
- What happens when the integration write fails? A serious vendor logs the failed write and still captures the lead in their own dashboard with an SMS notification, so you do not lose a customer to a third-party API outage.
The U.S. Bureau of Labor Statistics’ occupational data on customer service representatives is a useful benchmark for the loaded cost of a part-time human handling the same intake work — useful when you are pressure-testing whether the AI input cost is worth the output.
A few things owners forget about every time
Three inputs come up later and waste time if you have not thought about them up front:
- Spanish-language coverage. What share of your callers prefer Spanish? Should the AI default to English with a Spanish fallback, or open in Spanish in some service areas?
- Recording consent posture. Two-party-consent states require the caller to be notified that the call is being recorded. The AI announces this in the greeting where required. See our call recording consent laws post for state specifics. Not legal advice; verify with counsel.
- AI disclosure expectations. The Federal Trade Commission has been increasingly explicit about disclosure for AI-driven customer interactions. Decide up front whether the AI discloses itself proactively, on request only, or both.
For the broader category framing on AI vs human services, see our pillar: AI receptionist vs answering service. For a deeper trade-specific walkthrough, see what an AI receptionist for HVAC actually captures.
Frequently asked
Q: What does an InstaNexus AI setup actually need from me? A: The five inputs above — service menu, calendar and dispatch rules, greeting/hold/escalation language, pricing posture per call type, and FSM integration details. The shape of the conversation depends on your shop and your trade; the inputs themselves are universal.
Q: Do I need to replace my current CRM or phone system? A: No. An AI receptionist layers on top of an existing CRM and phone system, either on a new dedicated number you forward to or by accepting calls forwarded from your existing main line.
Q: What happens on a call the AI cannot handle? A: A well-built AI receptionist has a defined escalation path — hot transfer to your on-call number, SMS-page the owner, or a callback queue with a full transcript. Confirm the exact mechanic with any vendor on your shortlist.
Q: Can I start with after-hours only? A: Yes, and many shops do. After-hours-only mode is a common “toe in the water” configuration; only the forwarding rule changes between after-hours-only and all-day coverage.
Q: How do I know whether a vendor’s integration with my FSM is “deep enough”? A: Ask the vendor to demo a real call that ends with a job written into your FSM, not just a calendar slot booked. Watch which fields populate — customer, job, dispatch board, technician.
Not legal advice. Call-recording consent and AI-disclosure rules vary by state and by vertical; confirm your jurisdiction’s requirements before going live. Setup specifics differ by vendor and by shop — the inputs in this post are the universal categories any AI receptionist needs to know.
See InstaNexus AI configured for your shop
The inputs in this post are what any AI receptionist evaluation conversation should cover. If InstaNexus AI is on your shortlist and you want to see how a trade-specific script handles your actual call volume, the demo is the fastest way to get a concrete answer.