Inbound-only by design
No outbound dialing - a deliberate scope decision, not a missing feature.
AI Receptionist & AI Voice Agent
A custom inbound AI voice agent built to help answer missed and overflow calls and to book appointments into the scheduling system you already run, with ServiceTitan, Dentrix and GoHighLevel scoped per project. Expected call volume, concurrent-call capacity and a human fallback are scoped with you, and bookings and revenue are not guaranteed. Run it for your own business, or white-label it and resell it to clients under your brand.
The agent only answers calls your business already receives - no outbound dialing.
ServiceTitan & Dentrix booking write-paths scoped per project, not a generic FAQ bot.
Custom domain and branding throughout — resold to your clients as your own product.
The problem, by vertical
No industry figures are asserted here. These are the three launch verticals, and the table lists the inputs we would scope with you to build a client-specific estimate. Missed-call count, contact rate, qualified-lead conversion, booking value and attribution are separate inputs, and none of them is assumed.
| Vertical | Missed-call and contact inputs | Conversion and booking inputs | Value and attribution inputs |
|---|---|---|---|
| HVAC & Plumbing | Missed-call count by hour, including after-hours and overflow, and how many callers leave a message or call back | Share of contacts that are qualified leads, and how many become booked appointments, routine or emergency | Job value by service type, set by the business, and how bookings are attributed to the receptionist rather than other channels |
| Dental Practices | Missed-call count by hour, new versus existing patients, and how many callers are reached again | Qualified new-patient inquiries and the share that book a first visit | Patient value is a figure the practice defines and is not revenue per missed call. Attribution is agreed up front |
| Legal Services | Missed-call count by practice area and hour, and how many callers reach an intake step | Qualified intake rate, conflict checks and consultations booked | Case value varies widely and is not revenue per missed call. Attribution is agreed up front |
Deployment models
Whether it's one SMB client or a full agency roster, the same core platform adapts — tell us which of these fits and we'll scope it with a written proposal before development.
One phone line, timeline scoped up front, booked straight into their existing scheduling system.
Shared call handling, appointment routing scoped per branch.
Your brand throughout, resold to every client on your own domain.
Integration with ServiceTitan, Dentrix or GoHighLevel, scoped to whatever the SMB already runs.
Two sides, one platform
Your agency runs the platform; every SMB client gets a receptionist designed to catch the calls it would otherwise miss. Same backend, one source of truth.
01 · For the caller
02 · For your agency
Beyond the standard build
Not a chatbot bolted onto the side. Each layer here is aimed at a missed call or a manual dispatch decision, labeled for what it is.
A streaming STT → LLM → TTS pipeline designed for low-latency responses with barge-in, so a caller can interrupt naturally. Response time and interruption handling are scoped targets, verified in real-call testing for each deployment.
AI disclosure, opt-out handling and call logging are scoped as design and acceptance-test requirements for each deployment, after legal review for your jurisdiction and use case. They are requirements to be built and tested, not an implemented guarantee.
Designed to check technician or appointment availability before confirming a slot and to re-check for conflicts at booking time, with a human fallback when a slot cannot be confirmed. Booking accuracy is scoped and tested per integration.
The agency dashboard can show a hypothetical estimate calculated from inputs you supply, such as call counts and booking value. It is not a trained prediction and not measured incremental revenue.
The revenue estimate is a hypothetical calculation from inputs you provide, not a trained prediction and not measured incremental revenue. It is labeled that way on the dashboard.
Tech stack
A streaming design rather than a sequential record-transcribe-respond pipeline, aimed at a more natural conversation. Latency is a scoped target that is tested on real calls for each deployment.
What we build
Every engagement draws from the same core engine, these are the most common starting points.
Built to answer, converse and book in real time. The core product, designed for missed-call recovery.
Your brand end to end, custom domain, flat-rate billing your agency controls.
Booking write-paths into the systems HVAC, plumbing, and dental practices already run, built and verified per project.
One platform, tenant-isolated data, a single dashboard across every SMB client.
How it pays for itself
Most agencies combine two or three of these, we'll help you pick the mix that fits your existing client relationships.
A predictable monthly platform fee your agency controls, not usage-based billing from Matrytech that punishes a busy month. Provider usage for telephony, speech and models is billed separately.
Resell to each local business at whatever retail price the agency sets.
A one-time fee per new SMB client connected to their scheduling system.
An agency can use its own LLM/telephony accounts and pay those providers directly instead of a resale markup.
Protects the lead flow an agency's own advertising already generates — a reason for SMB clients to stay, not just a line item.
One franchise client, multiple locations, priced per line.
Source-code and IP terms for agencies that want to run the platform themselves are agreed in the contract.
Additional CRM/PMS integrations (Dentrix, legal case-management systems) priced as they're added.
From discovery call to launch
Real-time voice is new technical territory — Phase 1 is a deliberate risk-reduction spike, not a leap of faith.
A pre-launch proof gate: test latency and barge-in on real calls against the scoped target before anything is scoped to sell.
Booking write-path into ServiceTitan, built and verified per project rather than a generic webhook.
Custom domains, BYOK, flat-rate billing — what makes it resellable under your brand.
Legal review for your jurisdiction and use case, then AI disclosure, opt-out and logging acceptance tests before any real SMB call.
Dentrix integration, additional agencies onboarded on the proven platform.
Why Matrytech
No outbound dialing - a deliberate scope decision, not a missing feature.
No per-minute Matrytech markup compounding against your resale price as you scale clients. Provider usage costs are separate.
ServiceTitan and Dentrix booking write-paths are scoped and built per project, not a generic chatbot builder.
One person accountable for your build, not a rotating pool.
Ownership and hosting terms are agreed in your contract, not locked to a single vendor path.
One SMB client today, an entire agency roster tomorrow, same multi-tenant platform.
We don't disappear the day it ships.
You hear it get built and tested on real calls, not just the finished result.
Build vs subscribe
Short answer: off-the-shelf receptionists vary by vendor, plan and setup. Some start quickly from templates, while others offer custom prompting and integrations on enterprise plans (see Smith.ai pricing). A custom build is scoped around your own intake flow and booking systems, with its timeline agreed in your written proposal, and it still pays separate provider usage costs for telephony, speech and models (see Twilio US voice pricing).
| Off-the-shelf (Smith.ai, Synthflow, Bland, GoHighLevel AI) | Custom-built (Matrytech) | |
|---|---|---|
| Time to first call | Varies by vendor, plan, setup and integrations | Contract-scoped timeline, agreed in your written proposal |
| Pricing shape | Varies by vendor and plan: per-minute, per-call, subscription or enterprise contract | Scoped build fee and hosting, plus separate telephony, speech and model usage costs |
| Scripts | Varies from templates to custom prompting, depending on vendor and plan | Your own intake flow, scoped to your requirements |
| CRM & scheduling | Varies by vendor: native calendar and CRM connections, bridges such as Zapier, or custom integrations on some plans | Booking write-paths scoped per project: ServiceTitan, Dentrix, GoHighLevel, or yours |
| Branding | Varies by vendor and plan | Your brand, your voice, your domain |
| Data | Hosted on the vendor platform; terms vary | Your infrastructure, your retention rules |
Hear it work
Three sample flows, one per launch vertical. Illustrative scripts, every deployment gets its own intake flow, voice, and booking rules.
HVAC, after-hours
Caller: “My AC just died and it’s 91 degrees in here.”
Agent: “I’m the AI assistant for Ace HVAC. I can book a technician right now, can I confirm your address?”
Confirms address → finds a same-day slot → books into the dispatch board → texts confirmation. Illustrative flow.
Dental, new patient
Caller: “I’d like to book a cleaning, I’m new.”
Agent: “Welcome! I can set that up. Who’s your insurance provider, and do mornings or afternoons suit you better?”
Captures insurance → offers two slots → books into the PMS → texts the intake-form link.
Legal, intake
Caller: “My landlord is refusing to return my deposit.”
Agent: “I’m the AI assistant for Rivera & Cole Law. Let me take a few details so the right attorney calls you back prepared.”
Captures case type + conflict-check name → books a consultation → flags urgency to the attorney.
Before you ask
Software that answers your business phone with a natural voice, understands what the caller needs, and takes real action — booking appointments, capturing intake details, or routing urgent calls — instead of just taking a message. This one is inbound-only by design: it answers the calls you are already getting.
Many answering services charge per minute or per call and work from scripts. A custom AI receptionist is designed to answer promptly and to avoid putting callers on hold, with concurrent-call capacity scoped and load-tested against your expected call volume. It writes into your scheduling system once that integration is built and tested. Live agents still win for highly emotional or unusual calls, and the build can hand those to a human.
No, by design. Outbound AI calling is subject to consent and other rules that depend on jurisdiction and use case. This product answers the calls your business already receives. Inbound-only, intentionally.
Compare each vendor's current plan, integrations, data controls and resale terms. We scope a custom inbound workflow and integration tests for your business. This product has a flat-rate Matrytech platform fee, with a bring-your-own-key option, so the platform fee does not grow with call volume. Telephony, speech and model usage from providers is billed separately and varies with volume.
Local, appointment-driven service businesses: HVAC and plumbing, dental practices, and legal services are the three launch verticals because each depends on inbound calls to book appointments. The value of a missed call differs by business and is scoped with you, not assumed.
It is designed around a streaming speech pipeline rather than a sequential ASR-then-TTS pattern, with a low-latency response target and barge-in support so a caller can interrupt naturally. Latency, interruption handling and voice quality are scoped targets that are tested on real calls for each deployment, not measured capability claims.
It depends on the jurisdiction, the type of call and how the call is used, so it needs legal review before launch. Some rules, for example California's AB 2905 on calls placed with automatic dialing-announcing devices, address outbound or automated calls, and whether and how a rule applies to an inbound receptionist depends on the jurisdiction and use case. AI disclosure, opt-out handling and call logging are scoped as design and acceptance-test requirements for your deployment, not as an implemented guarantee. This is not legal advice.
Booking into your scheduling system is the target. For ServiceTitan, that means resolving business unit and job type, checking technician capacity, and creating the appointment, not just logging a callback request. The integration is scoped, built and tested with you before launch.
The Matrytech platform fee is flat-rate for the agency, not per-minute or per-message billing. Telephony, speech and language-model usage are separate provider costs that vary with call volume. A bring-your-own-key (BYOK) option lets an agency use its own LLM/telephony accounts, so those providers bill the agency directly instead of through a resale markup.
Yes, every engagement starts with a signed NDA and a written scope before any code is written.
Get started
A short discovery call is usually enough to scope your proposal — bring your current call volume, even a rough estimate.
An NDA is signed before the discovery call, your workflow and data stay confidential from the first conversation. We reply within 1 business day.
Prefer to call? +91 7004488728 · info@matrytech.com
Also popular
AI Customer Support Agent·AI Sales Copilot·All white-label products·AI Agents & Automation