Voice Outreach
Voice Outreach places outbound phone calls to advisors using an AI voice agent. For each call it researches the advisor, writes a brief for that specific conversation, checks the brief against your firm's compliance rules, and runs a set of structural pre-call checks. It then holds the call and waits for a person to approve it. Nothing is dialed until someone clicks Approve.
You work all of this from the Voice tab on the Outreach page in the app: the calls waiting on your approval, the queue, and a detail view for each call. There is no chat channel for Voice Outreach; it is a queue you work, not an agent you message.
Calling activates once your firm's phone calling account is connected and its call templates are set up. Until then the Voice tab stays empty and nothing is dialed. That is expected, not a fault.
What It Does
Voice Outreach exists to reach the long tail of advisors your team would never have the hours to phone by hand. A call starts from a trigger: a market or regulatory signal, an action on a prospect or advisor record, an operator placing a call from an advisor's workspace, or an optional automatic rule you have switched on.
From there the agent assembles a brief for that one conversation: who the advisor is, the firm they sit at, why you are reaching out, the points to cover, the outcome the call is for, and the disclosure that the caller is an AI voice agent and that the call may be recorded. The brief goes through your firm's compliance rules, the same gate that reviews outbound email.
Then come the structural pre-call checks, which are pass or fail rather than judged: a valid number and caller identity, the advisor's Do Not Call status, consent state where consent is required, the required disclosure, and a configured call template. A call that fails the compliance review or any of these does not dial. It routes to the needs-review lane and waits for a person.
The local calling window is checked too, but it behaves differently from the rest: a closed window means "not now" rather than "not allowed", so the call returns to the queue to be prepared again later instead of being held for review.
A call that clears everything still does not dial. It holds for approval, which is the point of the design: the compliance gate and the pre-call checks narrow what is allowed to go out, and then a person decides whether it actually goes out.
Once approved, the call is placed. It can be warm-transferred to a person mid-conversation when that is the goal. After the call ends, Voice Outreach derives the outcome, saves the transcript, links the recording where one exists, and runs a post-call check that flags anything worth reading closely.
Key Capabilities
| Capability | What it gives you |
|---|---|
| Autonomous outbound calling | Reach across the long tail of advisors without your team dialing each one by hand |
| Per-call briefing | An advisor-specific brief before every call: who they are, why you are calling, and what to cover |
| Compliance gating | Every brief checked against your firm's compliance rules before the call is eligible to dial |
| Structural pre-call checks | A valid number and caller identity, Do Not Call status, consent, the AI and recording disclosure, and a configured call template, each a hard pass or fail. A closed local calling window returns the call to the queue rather than dialing |
| Approval before every dial | A cleared call is held, not placed. A person approves it, and only then is the number dialed |
| Separation of duties | The approver must differ from whoever queued the call, so a person cannot place a call and release it themselves |
| Warm transfer | A live call handed to a person when the goal is to connect the advisor with a human |
| Outcome capture | The result of each call recorded automatically: a meeting booked, a callback requested, a voicemail, or no interest |
| Transcript and post-call check | A full transcript after each call, plus a check that flags anything worth a second look |
| Optional call types | Extra call purposes (meeting confirmation, speed-to-lead, dormant re-engagement, data verification, inbound qualifying, internal escalation), each switched on one at a time and all off by default |
The Approval Rule
Voice Outreach follows the same rule as every other outbound path in the product: a person approves before anything reaches an advisor. For email that is the Drafts folder and the Send button. For the phone it is the Needs Approval lane and the Approve button.
There are four layers behind that, and they are cumulative rather than alternatives:
- The compliance gate. The brief is scored against your firm's compliance rules. A brief that cannot clear them routes to needs-review instead of becoming eligible to dial.
- The structural pre-call checks. A valid number and caller identity, Do Not Call status, consent, the disclosure, and a configured call template. These are deterministic pass or fail checks, not judgment calls, and they run after the compliance gate rather than instead of it.
- Separation of duties. The person who approves a call must not be the person who queued it. If you place a call from an advisor's workspace yourself, a colleague releases it, not you. This applies to calls a person queued; a call raised automatically by a signal or a scan has no human originator to conflict with, so it needs only one approver. Your compliance team owns whether this rule is on for your firm.
- Your approval. A call that clears the other layers is held. It appears under Needs Approval with the brief and every check result visible, and it is dialed only when you approve it.
If separation of duties blocks you, the call is not rejected and nothing is lost: it stays in Needs Approval for someone else on your team to release, and the refusal is recorded like any other decision.
The second layer runs more than once. The checks are recorded when the call is prepared, re-run when you approve, and re-run again immediately before the call is placed, so a call is judged on current facts rather than on whatever was true when it entered the queue. A hard check that changes during the wait stops the call even after approval.
That is also why you can work the Needs Approval lane at any hour: approving a call outside the advisor's calling window records your authorization and the call is placed when the window reopens. See Schedule.
There is a fourth backstop you will see if it is in play. Dialing itself has a master switch that is off by default. If it is off when you approve a call, the approval is recorded, the call stays held, and the button reads "Approved, dialing is off" rather than implying a call went out.
The optional call types are also off by default. None of them queues a call until someone turns it on, which keeps the scope of automated calling to exactly what you have chosen.
Who It's For
- Wholesalers and external sales staff: reach advisors that would otherwise never get a call, with a researched brief on each one and a transcript afterward.
- Distribution leaders: extend phone coverage across the territory while every call still passes compliance and a human approval before it dials.
- Compliance officers: every call brief is gated against your firm's rules, the pre-call checks are recorded per call, and no call reaches an advisor without a named person approving it.
Related
- Commands: how you approve calls and review results in the app
- Notifications: what each notice on a call means
- Schedule: what it does on its own and when
- Examples: end-to-end walkthroughs
- Troubleshooting: common questions and what to check
- Outreach: the Voice tab, where the call queue and the per-call view live in the app