Assisted estimates
A new door file: model, dimensions, photos, then follow-up until an answer lands. A homeowner comparing three doors forgets yours within a week absent a nudge.
Garaga and its dealer network
A manufacturer request arrives carrying its identifier, and it is written into Zenvox. A web form is not an interface: nothing is written into the network.
7 days, 20 answered calls, no card
Where your enquiry lands
The request is written into Zenvox: the person, the address, the model discussed, the manufacturer request identifier when one exists, and the nature of the call. Inside the network, nothing is written: ordering screens went unverified, network access rights for an integrator are unknown, and no webhook was verified.
It is no interface, and research is blunt about it: nobody infers an interface from a web form. An observed case sat in Ontario, leaving local configuration to establish. Until it is, the receptionist works in native mode and keeps the identifier so your follow-up stays attachable.
Garaga builds garage doors and sells through a dealer network; a new door enquiry and a broken spring repair then reach one line at opposite hours, demanding two different answers.
Read, create, update, cancel
Research describes a commercial path, not operations. This matrix says so, dressing it up as no technical wait.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | A manufacturer request arrives carrying an identifier. Authorised network access, along with integrator rights, remains unestablished. |
| Create | Zenvox native mode | An estimate or repair request gets created inside Zenvox during a call, carrying a model if a caller knows it, plus a manufacturer request identifier if he has one. |
| Update | Zenvox native mode | An order, a build lead time or a promotional agreement belongs jointly to a dealer and a manufacturer. Zenvox leaves all three alone. |
| Cancel | Zenvox native mode | Cancelling a door order commits a made-to-measure product. A human decides that, at a dealer. |
What is included, what needs an add-on
Telling an emergency apart from a sale is half this trade. A broken spring, a loose cable, a derailed door or a car trapped inside calls for an immediate alert; a new door enquiry calls for an on-site estimate. Your receptionist sorts that out inside a few seconds, evenings and Saturdays included.
Authorisation, and where truth sits
Nothing plugs into a manufacturer network. What follows says who holds what.
- Your dealer access stays yours; Zenvox asks for no network credentials
- A manufacturer request identifier gets kept on a request, so one file matches on both sides
- A promotional agreement offered inside a manufacturer form is a separate box, and it gets presumed by nobody
- A dealer holds truth on order, lead time and price; a receptionist commits on none of those three
Costs of a network connection or partnership stayed unknown through research.
Seven in the morning. A door came down hard, trapping a car inside a garage.
CustomerMy garage door slammed down and it will not go back up. My car is stuck inside.
ReceptionistTaking a name and a callback number right away. Do not force that door, and keep away from a spring above it: tension there is dangerous. Can you see a broken spring?
ReceptionistFlagging an emergency, along with an address and postal code. An on-call technician gets alerted now, then calls you back with an arrival window.
An alert reaches an on-call technician alongside a recording and a summary. No price was quoted, no fault was diagnosed over a phone, and no exact arrival time was promised: only a window.
If no connection exists
Here that is a default, and a phone stays a channel deciding outcomes.
- A request gets created in Zenvox, carrying brand and model if a caller knows them
- A manufacturer request identifier gets noted, following you inside a file
- Safety emergencies leave an ordinary queue, reaching on-call staff
- Zenvox changes nothing about how you already work with a manufacturer
Questions about this connection
Is there a connection to the manufacturer network?
No. Ordering screens went unverified, network access rights for an integrator are unknown, and no webhook was verified. Nobody infers an interface from a web form.
Is the manufacturer request identifier kept?
Yes, it is noted on the request when one exists, so the file matches on both sides. That is what keeps your follow-up attachable even with no connection.
How does she tell an emergency from a new door sale?
A broken spring, a loose cable, a derailed door or a car trapped inside raises an immediate alert to the on-call technician; a new door enquiry goes to an on-site estimate. That sorting happens within the first few seconds, evenings and Saturdays included.
Can she cancel a door order?
No. Cancelling an order commits a made-to-measure product, and a human decides that, at the dealer. An order, a build lead time or a promotional agreement belongs jointly to the dealer and the manufacturer.
Does she promise an arrival time?
She gives a window, not an exact hour, and she quotes no price and diagnoses nothing over the phone. The dealer holds the truth on order, lead time and price.
Where to next
See a trade concerned, or a full software list.
Garaga and its dealer network