Brokerage and teams
A lead reaches the right person under your rotation or territory rules, and the history follows. On a team, an orphan lead is a loss nobody notices.
Follow Up Boss
A call filed as an inbound event triggers your follow-up workflow; filed as a plain contact it triggers nothing. The exact destination decides, not the connection.
7 days, 20 answered calls, no card
Where your lead lands
The lead is written into Zenvox — source, property sought, buyer or seller role, timeline, stated budget — then filed into Follow Up Boss as an inbound event. The research verified it: a lead filed as an inbound event sets off the follow-up workflow; the same contact created through the people route does not.
Access rests on an account key and user rights you supply, with your explicit agreement; contact ownership follows your rotation or territory rules. Until that agreement is given, the receptionist works in native mode and the software keeps its truth.
Follow Up Boss holds contacts, lead source and the follow-up workflows of residential agents; the receptionist qualifies without approving financing or quoting a value, then asks whether the person is already represented by somebody else.
Read, create, update, cancel
The status below separates what was verified in the documentation from what still has to be proven on a real account.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | Finding a contact and its stage makes it possible to answer without asking for the history again. Access rests on an account key and user rights, and it requires your prior agreement. |
| Create | To qualify | Filing an inbound lead through the events route is the verified route: it is what sets off your workflow. Creation through the people route does not. Before activation, deduplication and contact ownership have to be settled. |
| Update | To qualify | Writing a note, changing a stage and closing remain to be tested. A stage changed by mistake chases a client who already signed elsewhere: the kind of error that costs a reputation. |
| Cancel | Zenvox native mode | Outbound won and lost events are unvalidated. Stopping a follow-up that no longer fits is therefore decided by the agent, and Zenvox stops its own at the same moment. |
What is included, what needs an add-on
Answering during a showing, capturing source and representation context, qualifying timeline and area, and handing you everything belong to your real estate base. Routing across a team and sales follow-up are named add-ons.
The authorisation, and what holds the truth
Sales follow-up software sends messages in the agent name. The points below exist so nobody receives a message that should have stopped.
- The account key and user rights come from you, with your explicit agreement; Zenvox asks for no password
- Deduplication is settled before activation: one buyer must not exist twice with two workflows
- Contact ownership is set by your rules, not by the order calls arrive in
- The agent validates representation, advice, offers and property availability; none of that is promised on the phone
- An already represented prospect suspends showing booking and goes to the agent to decide
Saturday afternoon, the agent is holding an open house. The call comes from a lawn sign. Nothing is written into the software.
CallerHi, I am calling about the house on Main Street, the one with the sign.
ReceptionistLet me take your name and a callback number. Are you already working with an agent on your purchase?
ReceptionistGood, I am noting that. Which area are you looking in, and do you have a timeline in mind? I am passing this to the agent with the source of your call; she calls you back about a showing.
The agent receives a qualified lead with its source, the property concerned, the caller role, representation context and stated timeline. No property value and no financing were put forward on the phone.
When the connection is not there
The software keeps its truth, and the receptionist works in Zenvox native mode.
- The lead is created inside Zenvox with its source, the property, the role and the timeline
- Representation context is captured and flagged to the agent
- You find the call, its transcript and its reason in the app
- No capability in your base depends on third-party software
- The day event filing is proven, it is added without redoing your setup
Questions about this connection
Why does the exact destination matter so much?
Because a lead filed as an inbound event sets off your follow-up workflow, while the same contact created through the people route does not. The research verified it, and the events route is the one kept.
Does Zenvox change the stage of a deal?
Not before it is tested. A stage changed by mistake chases a client who already signed elsewhere: writing a note, changing a stage and closing remain to be proven on a real account.
What if the person is already represented by another agent?
Showing booking is suspended and the file goes to the agent to decide. Representation context is captured on the call and flagged, connected or not.
How do we avoid two records for the same buyer?
Deduplication is settled before activation, and contact ownership is set by your rotation or territory rules, not by the order calls arrive in.
Does the receptionist put forward a value or financing?
No, no property value and no financing are put forward on the phone. The agent validates representation, advice, offers and property availability.
Where to next
See the practice concerned, or the full list of software studied.
Follow Up Boss