Examples

These walkthroughs show how Voice Outreach behaves once calling is connected. 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, which is expected, and none of the calls below can be placed.

Example 1: A Meeting-Booking Call You Approve

An advisor at a firm in your territory is flagged by a signal. The goal for the call is to book a short intro meeting.

Step 1: The call is queued. Voice Outreach picks the advisor up from the queue and researches them. It assembles a brief: who the advisor is, the firm they sit at, the reason for the call, the points to cover, and the goal (book a meeting). The brief also carries the required disclosure that the caller is an AI voice agent and that the call may be recorded.

Step 2: Compliance review. The brief goes through your firm's compliance rules and clears them.

Step 3: Pre-call checks. The structural checks run: the number is valid, the caller identity is set, the advisor is not on your Do Not Call list, consent state permits the call, the disclosure is present, and a call template is configured. All pass.

Step 4: The call is held for you. This is the step that surprises people who have used other calling tools. The call is not dialed. It appears under Needs Approval on the Voice tab, showing the brief and every check result. Nothing happens until a person acts.

Step 5: You approve it. You read the brief, see that the checks passed, and click Approve. The row is marked Approved in place. The call is dialed straight away, so you approve it when you are content for the call to happen now.

Step 6: The call runs and is scored. The AI voice agent opens with the disclosure, covers the talking points, and the advisor agrees to a meeting. When the call ends, Voice Outreach derives the outcome as a meeting booked, saves the transcript, and runs the post-call check, which finds nothing to flag. The call moves to Recent Calls.

Step 7: You review it. You open the call. The detail view shows the brief, the compliance result, each pre-call check, who approved it, the outcome, and the full transcript with a link to the recording. You read the transcript to confirm the meeting time and prepare.

Example 2: A Call Held for Review

Another advisor is queued for a call. This one never becomes eligible for your approval.

Step 1: The call is queued. Voice Outreach prepares the brief in the usual way and it clears the compliance review.

Step 2: A pre-call check fails. During the structural checks, the advisor's number matches your Do Not Call list. That is a hard check, so Voice Outreach stops there. The call routes to needs-review and is never dialed.

Step 3: It surfaces on the page. The call appears in the needs-review count rather than under Needs Approval. Because there is no chat channel for this agent, the Voice tab is where you see it; nothing is pushed to Slack.

Step 4: You look into it. You open the held call. The detail view names the specific reason: the advisor is on your Do Not Call list. The brief and trigger context are there so you can see what the call was for. You confirm the call should not be placed and leave it held. No call was made, which is exactly what the checks are there to produce.

Example 3: A Call You Approve Out of Hours

A call was prepared during the afternoon and cleared everything, and you are working through the Needs Approval lane at nine in the evening.

Step 1: The call is waiting. It has been under Needs Approval since the afternoon, with all of its checks recorded as passed at the time it was prepared.

Step 2: You approve it. The checks are re-run as you approve. Everything still passes except the advisor's local calling window, which has closed for the evening. Because a closed window means "not now" rather than "not allowed", your approval is accepted rather than refused.

Step 3: The call waits, not you. The button reads "Approved, dials in calling hours" and the call moves to Awaiting Calling Hours. You are finished with it. There is nothing to come back to, no second click, and no risk of the call being forgotten because it needed one.

Step 4: The call is placed next morning. When the advisor's calling window opens, the checks run once more against that morning's facts, and the call is dialed using the brief you approved the previous evening. Nothing about it was regenerated in between: what goes out is what you released.

Step 5: What would have stopped it. If the advisor had been added to your Do Not Call list overnight, the morning re-check would have caught it. The call would move to needs-review instead of being placed, and your approval would not override that. Approval authorizes a call; the checks still decide whether it happens.

Example 4: Approving While Dialing Is Switched Off

Dialing has a master switch, and it is off by default on a new install.

Step 1: You approve a held call. Everything looks normal: the brief is there, the checks passed, you click Approve.

Step 2: The button tells you what happened. Instead of Approved, it reads "Approved, dialing is off". Your approval was recorded and no call was placed.

Step 3: The call stays held. It remains under Needs Approval rather than being lost or marked as failed, and it will not dial later on its own once the switch is flipped. When dialing is turned on, you approve it again to place it.

This is the expected state before your firm has gone live on calling, and it is why the first call of a rollout is a deliberate act rather than something that happens by surprise.