Assisted estimates
An estimate file, missing photos or measurements, a sent version, plus follow-up until somebody replies. A connection helps find a matching quote; it stands in for no add-on.
Choose the software you use to see what your receptionist can read or do, the permissions it needs and the relevant add-ons.
41 results
Job requests, estimates, visits and job follow-up.
Intake, availability and appointments within your practice’s permissions.
Tenant requests, leads, files and team calendars.
Bookings around your available places, resources and opening hours.
Your appointments, advertising forms and sales enquiries.
Your receptionist writes into Zenvox: the request, the reason for calling, the recording and the transcript are there, connection or no connection. A connection does one further thing, and one only — it keeps a single piece of information from being typed twice. It adds no capability to your base, and your software keeps the truth of its schedule and its records.
The deciding question is your edition. A higher tier, an interface module, a vendor review or partner access govern writing at several vendors, and each page names the one that applies. Your own part is bounded: an authorisation granted from your own account, no password handed over, no connector to program, no bespoke development. Where a vendor offers nothing but a key you create yourself, the page says so, and the receptionist works in native mode until it is done.
Thirty-six software products were surveyed one by one; no Zenvox authorisation grant is established at those vendors to date, and every page says so in the same order.
“Zenvox integrates with your software” means nothing. Finding a customer record, filing a request, moving an appointment and cancelling it are four separate authorisations, and every software page states all four.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | Finding an existing customer, file or appointment. It is best documented at most vendors, yet no authenticated test from Zenvox has confirmed it. |
| Create | To qualify | Filing a request, an estimate or an appointment. A write needs required fields, plus defined behaviour if a caller reaches a business twice in a row. |
| Update | To qualify | Moving a visit or changing a status. It rests on events a vendor publishes, so an exact event list has to be checked at every vendor. |
| Cancel | To qualify | Cancelling touches money taken, penalties and statuses edited by hand inside your software. It carries heavier consequences, so it opens last. |
Answering in French or English, qualifying, texting back a caller nobody reached, handing you a request, and stepping aside as soon as you pick up: all of it sits in your base, whatever software you run. A connection unlocks no capability — add-ons carry capabilities, and they attach with or without third-party software.
One protocol applies across every software product on this list, whoever builds it.
Vendor charges — a subscription tier required before an interface opens, a network commission — belong to a vendor and get checked with them. Research recorded those charges as unconfirmed.
A service business runs field software. No connection exists yet; a receptionist works in native mode.
CustomerHi, I need somebody this week. You did work at my place last fall.
ReceptionistHappy to help. I will take a name plus a callback number first, in case a call drops, then you tell me what is happening.
ReceptionistNoted, along with an address plus postal code. I am flagging you as a returning customer. An owner gets this right away, then calls back with a window.
A complete request reaches an owner, in a workspace plus by text. He copies it into his software if he wants to. Nothing was written outside Zenvox, since nothing was authorised to be.
Today that is a default, and it blocks nothing. A receptionist works inside Zenvox, so you pick up work where you already are.
That depends on your software and your edition, and every page states it action by action. Thirty-six software products were surveyed one by one, and no Zenvox authorisation grant is established at those vendors to date. Your request is written into Zenvox either way.
One thing only: it keeps a single piece of information from being typed twice. It adds no capability to your base, and your software keeps the truth of its schedule and its records. Add-ons carry capabilities, and they attach with or without third-party software.
Because finding a record, filing a request, moving an appointment and cancelling it are four separate authorisations. Cancelling touches money taken, penalties and statuses edited by hand inside your software: it carries the heaviest consequences, so it opens last.
No. Authorisation is granted from your own vendor account, with no password handed over and no bespoke development. Where a vendor offers nothing but a key you create yourself, that software page says so, and the receptionist works in native mode until it is done.
Any charges belong to the vendor — a subscription tier required before an interface opens, a network commission — and they get checked with them. Research recorded those charges as unconfirmed, and each page names the one that applies to that software.
Native mode stays complete: the request, the reason for calling, the recording and the transcript live in your workspace, connection or no connection. To have your tool qualified, it takes a named product, its edition and the person who holds the account.
Read a full software page, or start from an industry.
You can start with Zenvox’s tools and describe what you want to connect. Each connection explains the actions covered and the permissions needed.
Explore options for my softwareKeep what works in your business. Compare working with your current tools and working directly in Zenvox.
Understand both ways of working