BROLLY / MENU
Get in TouchLogin

Brolly VoxFlow: an AI voice agent for outbound calls

Bring a lead list and a clear calling objective into one workflow. Brolly VoxFlow combines spreadsheet information, task instructions and a voice pipeline to support contextual outbound conversations. Request a team-led demonstration to explore the application.

Explore the workflow

From a lead list to a contextual conversation

Outbound calls often depend on information already stored in a file: a person’s name, an event time or a note about their enquiry. VoxFlow is designed to connect that context with a task written in plain English. The workflow uses CSV, Excel or text data and prepares per-lead information for the voice conversation. The demo is the place to review the calling process against your real operating requirements.

Why use Brolly VoxFlow?

Use the context already in your list

A call about a demonstration or appointment is more useful when the relevant details are available. Review the accuracy and completeness of the source records before using them in a calling workflow.

Describe the purpose of the call

A clear task explains what the conversation needs to achieve. For example, a reminder and an attendance confirmation are related, but they require different questions and follow-up decisions.

Evaluate the whole workflow

Consider preparation, the conversation and what happens after a call. The demo should cover the dashboard and how your team will handle incomplete conversations, questions and follow-up work.

How Brolly VoxFlow works

  1. Step 1

    Prepare the contact data

    Start with a CSV, Excel or text lead list. Check the contact details and the fields that provide context for the calling task.

  2. Step 2

    Define the calling objective

    Describe the purpose in plain English, such as reminding invited leads about a scheduled demo and asking whether they can attend.

  3. Step 3

    Build the conversation context

    The RAG workflow extracts relevant details for each lead and supplies them to the voice pipeline alongside the task instructions.

  4. Step 4

    Review calls and follow-up

    Use the demonstrated dashboard to inspect call activity. Agree what your team should do when a call needs further attention or a human response.

Architecture and technology flow

Follow the functional layers from input to output. During your demo, our team can discuss the technology choices, integrations and deployment requirements for your environment.

  1. 01 →

    Data ingestion

    CSV, Excel and text information provide contact records and task-specific context for the workflow.

  2. 02 →

    Retrieval and context

    The RAG layer selects the relevant lead details and combines them with the instructions for the conversation.

  3. 03 →

    Language and voice pipeline

    The voice-agent workflow connects generated conversation responses with telephony. Languages, providers and operating capacity need to fit the intended deployment.

  4. 04

    Operator visibility

    The application’s status dashboard provides a place to review calling activity. Discuss reporting, escalation and integrations using your team’s process during the demo.

Use cases to explore

Demo and event reminders

An example task is reminding invited contacts about a scheduled demonstration and asking whether they can attend. The event details need to be accurate and available in the source data.

Enquiry follow-up

Discuss how a calling workflow could follow up on an existing enquiry and identify the next conversation a person needs. Confirm the questions, expected responses and handover process before a rollout.

Appointment-related conversations

For an appropriately scoped deployment, explore reminders or confirmations using appointment context. Review contact permissions, calling windows and exception handling with the team.

Make your demo useful

Tell us what you would like to see and include your preferred meeting time and time zone. Our team will follow up to agree a suitable time.

  • The purpose of the outbound conversation
  • An anonymised example of your lead-list fields
  • Target languages, time zones and calling windows
  • Expected follow-up, reporting and integration needs

Brolly VoxFlow: common questions

What information does VoxFlow use for a call?

The workflow uses a lead list and task instructions. Relevant details such as names, times and notes provide context for each conversation. Confirm the required fields and supported inputs during the demonstration.

Can I launch calls from this page?

No. This page explains VoxFlow. Request a demo and our team will show the application; submitting the form does not launch calls or give access to the calling system.

Which languages, integrations and call volumes are supported?

Review those requirements with our team for your deployment. This page does not promise a fixed concurrency limit, universal language coverage or a specific telephony integration.

How do I arrange a demo of Brolly VoxFlow?

Select Request a demo, enter your contact details and describe the workflow you want to see. Our team will follow up to agree a time for the demonstration.