Add to VOX backlog
What this page is — the rules that hand a lead to Orbit Vox for an automated outbound call.
What it is for — turning a qualifying lead into a call target, so an AI voice agent rings them without anybody queueing it manually.
The problem it solves — following up at volume. It is also the one conversion family that crosses into another module, so this page draws the boundary: which leads get called is here, everything about the call itself is Vox.
Route: /org/marketing/leads/settings?tab=rules&rule=convert-vox
Permission: Manage Conversion Rules for Lead to Contact or Deal
1. What this does
Rather than creating a contact or a deal, a matching lead is added to Orbit Vox's outbound calling backlog — a queue of people an AI voice agent should ring.
| Owned by Pulse | Owned by Orbit Vox |
|---|---|
| The rule, its conditions, the Run action | The backlog itself, campaigns, the dialler |
| Showing the resulting call log on the lead | Placing the call, the agent script, recordings |
2. The boundary
This is a genuine module handoff, so the documentation splits here.
| Question | Where |
|---|---|
| Which leads get called? | This page |
| What does the agent say? | Orbit Vox — voice agent configuration |
| When does it dial? | Orbit Vox — outbound campaigns |
| Which number does it call from? | Orbit Vox — numbers |
| Where do I see the outcome? | Calls tab on the lead |
Separately from this rule family, Vox campaigns can be built from a lead queue — which is why queue information also accepts Vox campaign permissions. Adding to the backlog and building a campaign from a queue are two different routes to the same outcome.
3. What a rule is
The same shape as the other two families: name, conditions, trigger, active toggle, and a Run that applies it retroactively.
There is no preview and no summary. A broad rule can enqueue hundreds of real people for an automated outbound call — with the compliance consequences that implies.
Check the lead's consent flags in your conditions. consent_sms and consent_whatsapp are stored on
every lead precisely so routing decisions can respect them.
4. The admin contract
| Needs | Or |
|---|---|
| Orbit Vox configured with a voice agent and a number | Backlog entries are created and never called |
| Manage Conversion Rules for Lead to Contact or Deal | Rules render and every save fails |
| Leads with a phone number | There is nothing to dial |
| Consent conditions on the rule | You may call people who declined |
5. Downstream
| Reaches | As |
|---|---|
| Orbit Vox outbound backlog | A queued call target |
| The lead's Calls tab | The resulting lead_voice_logs entry |
| The lead timeline | Activity from the call outcome |
6. Don't confuse this with…
| This | Not this |
|---|---|
| Adding to the backlog | Placing a call — Vox does that |
| A Vox voice agent | A lead agent, which is a user |
| This rule family | Convert to contact or deal |
7. Troubleshooting
| Symptom | Cause |
|---|---|
| Backlog entries never called | Vox has no agent, number or active campaign |
| Nothing added | No rule matches, or leads have no phone number |
| Rules save with an error | Missing manage_conversion |
| A declining contact was called | Consent flags were not part of the rule. Section 3 |