HubSpot

The request is written into Zenvox, then filed into HubSpot as a contact or a deal under your rules. The authorisation sits on your account, and it can be revoked cleanly.

7 days, 20 answered calls, no card

Where your request lands when a CRM already exists

The request is written into Zenvox: who is calling, what they want, the qualification done on the phone. HubSpot keeps the truth of your commercial activity, and the connection files a contact or a deal there under your rules. Zenvox reads, creates, updates and closes deals in HubSpot, within the rights you grant.

Access goes through an authorisation you install on your own account, with the read and write rights you set: no key to create, no connector to program. A per-account authorisation can be revoked cleanly, and that is what counts when you are handing over your client book.

HubSpot is a CRM: contacts, companies, deals filed into pipelines. When one is already in place, the question is not whether to replace it, but who writes what — a seller wanting a valuation and a buyer wanting a viewing enter a pipeline differently.

Read, create, update, cancel

All four actions run through the authorisation installed on your account, with the read and write rights you set. Every write keeps a Zenvox identifier and its source, and HubSpot keeps the record of the commercial state of each deal.

ActionWhat that means
ReadZenvox reads and searches contacts and deals, together with the pipeline and stage identifiers. Reading a contact or a deal on the owner's behalf does not depend on an acquisition add-on; its first job is simply to recognise who is calling.
CreateZenvox creates the deal and associates it with the contact and the company. A Zenvox identifier is kept on the deal, so that a callback from the same customer does not produce a second record of the same file.
UpdateZenvox updates the deal and its associations as the request moves along. A custom stage is followed by its internal identifier, not by its label: you rename your stages in your account without breaking anything.
CancelArchiving or deleting a deal is not the same as marking it lost, and neither of them is a withdrawal of consent: three different things, handled separately. The receptionist marks a deal lost with its reason, archives nothing without your decision, and records a withdrawal of consent separately, in your workspace.

What is included, what needs an add-on

Answering, qualifying, taking the appointment and passing the request along belongs to your base, CRM or no CRM. Reading a record to recognise a customer who is calling back is part of that too. The pipeline, assigning an owner, following up by stage and sending the outcome back are the work of the acquisition add-on. The CRM's own automations depend on the plan you hold with them.

Add-ons that work with your software

Lead capture and sales follow-up

Assigns an owner, follows up by stage, keeps the reason for a loss and measures performance by source. This is the add-on that needs a pipeline, and that knows what to do with one.

Multi-site and entities

An agency with several offices, or several entities inside one account: how far the receptionist can see and write is settled here, before you open a shared CRM.

The authorisation, and what holds the truth

Handing over your client book deserves rules that are written down. Here are the ones set before your installation.

  • The authorisation is installed on your own account with the read and write rights you set, and your password does not go through Zenvox
  • The per-account authorisation is the normal road, because it can be revoked cleanly
  • A deal created from a call keeps a Zenvox identifier and its source, so that two tools do not produce two files for the same customer
  • Custom stages are followed by their internal identifier, not by their label
  • The CRM holds the truth for the commercial state: it is what decides whether a deal is won, lost or still open
  • The reason for a loss is written down, because a pipeline with no reasons in it helps nobody understand a bad quarter

A real estate brokerage team. The CRM holds the seller and buyer pipelines. The authorisation is installed on the team's account, and the receptionist files the request into the seller pipeline.

CallerHi, I would like to know roughly what my house might be worth.

ReceptionistLet me take your name and a number to reach you on first. What is the address of the property?

CallerIt is a semi-detached, and we are thinking of selling in the spring.

ReceptionistGood. Is it already listed with another broker? I do not give an opinion on value over the phone — the broker establishes that on site — but I can book you a seller meeting.

The request goes to the seller queue with the address, the type of property, the timeline and where the call came from. The deal opens in HubSpot in the right pipeline, at the right stage, with the Zenvox identifier and the source of the call.

If the connection is not there

A team that would rather not open its CRM — or that does not have one — keeps the same reception and the same follow-up. The workspace carries its own intake and its own pipeline.

  • The request is created in your workspace with the same fields and the same qualification as on the phone
  • An owner is assigned, the follow-ups run by stage, and the reason for a loss is kept
  • You copy the record into your CRM if you want to, with its origin intact
  • Installing the authorisation later preserves the source of every deal, with nothing to redo

Questions about this connection

Can the authorisation be revoked cleanly?

Yes, and that is why the per-account authorisation is the normal road: it is installed on your own account, with the read and write rights you set, and your password does not go through Zenvox.

Will I end up with two records for the same customer?

A deal created from a call keeps a Zenvox identifier and its source, so two tools do not produce two files for the same customer. A callback from that customer therefore produces no second record of the same file.

Our pipeline stages are custom — is that a problem?

No. They are followed by their internal identifier, not by their label: you rename your stages in your account without breaking anything.

Does she archive a lost deal?

No. Archiving or deleting a deal is not the same as marking it lost, and neither of them is a withdrawal of consent: three different things. The receptionist marks the deal lost with its reason, and archives nothing without your decision.

Do I need the acquisition add-on to recognise a customer calling back?

No: reading a contact or a deal on the owner's behalf does not depend on it. The pipeline, assigning an owner, following up by stage and sending the outcome back are the work of the add-on.

Where to next

See sales follow-up, the trade concerned, or open the full software list.

HubSpot

The request is written into Zenvox, then filed into HubSpot as a contact or a deal under your rules. The authorisation sits on your account, and it can be revoked cleanly.

Start your free trial7 days, 20 answered calls, no card