Yes — Brilo AI can work with existing Google Voice numbers in many deployments, and Brilo AI’s pricing model offers preallocated minutes and per‑minute top‑ups (minute blocks) that teams can purchase to run AI phone agents. Keeping Google Voice typically requires routing your calls to Brilo AI through your existing telephony path (for example, SIP trunking or a connector) or forwarding, and then assigning Brilo AI voice agent call handling and minute allotment to that inbound number. Depending on your setup you can either apply Brilo AI minutes to calls handled by the agent or use your carrier minutes while Brilo provides AI processing; the exact workflow depends on how your Google Voice is routed into Brilo AI. See Setup Requirements below for the actions your IT or telco will need to take.

Can I keep my Google Voice number and use Brilo AI minutes? — Yes. In most cases Brilo AI can accept calls forwarded from Google Voice and apply Brilo AI minute usage when the agent answers.

Do I need to buy minute blocks from Brilo AI if I keep Google Voice? — Sometimes. If calls are routed through Brilo AI for full agent handling, Brilo AI’s minute blocks apply; if Google Voice handles carrier termination and only forwards metadata, you may keep your carrier minutes.

Can Brilo AI bridge Google Voice into my CRM and buy minutes for AI handling? — Yes. When routed through Brilo AI, voice agent interactions and minute accounting can be tied to the agent and synced to your CRM.

Enterprises ask this when they already operate Google Voice for business numbers but want Brilo AI voice agent capabilities without ripping out existing telephony. Buyers want clarity on billing (who charges minutes), routing options (call forwarding vs. SIP trunking), and whether they must migrate numbers. For regulated sectors such as healthcare and banking, teams also need to know how call handling and minute accounting affect compliance, call recording, and audit trails.

Brilo AI can accept calls from an existing Google Voice number if the number is forwarded or routed into Brilo AI’s telephony interface. Once Brilo AI receives the call, the Brilo AI voice agent can answer, execute call flows, and consume Brilo AI minute blocks (prepaid minutes) according to your account plan. In deployments where Google Voice continues to terminate calls, Brilo AI may only receive a forwarded call leg and therefore your carrier minutes could still be consumed instead.

In Brilo AI, minute blocks are prepaid or plan‑based minutes that the account uses to cover AI speech processing and call time.

In Brilo AI, call routing is the configuration that determines whether an incoming number is answered by a Brilo AI voice agent, forwarded to a human, or sent to another IVR or webhook.

In Brilo AI, a voice agent is a programmable phone agent that handles live calls using configured scripts, CRM lookups, and escalation rules.

For integration patterns and example connectors, see the Brilo AI HubSpot integration page for how call metadata and transcript data flow back into your CRM: Brilo AI HubSpot integration.

Brilo AI should not be assumed to automatically control carrier billing for a number that remains fully managed by Google Voice. If your Google Voice plan continues to terminate PSTN calls before forwarding to Brilo AI, your carrier may still record those minutes. Avoid assuming minute portability without confirming your routing path.

A forwarded call is not the same as an inbound SIP trunk leg — forwarding can add an extra call leg that affects minute accounting and call metadata. Configure tests to confirm which system (carrier vs. Brilo AI) is consuming audio minutes. For guidance on appropriate AI phone answering configurations and limitations, review Brilo AI’s resources on AI phone answering systems: Brilo AI AI phone answering system overview.

Typical guardrails:

Healthcare example:

A medical practice keeps Google Voice numbers for patient callbacks but forwards incoming calls to Brilo AI during business hours. Brilo AI handles intake questions and books follow-ups while transcribing notes to the EHR (via your webhook). The practice verifies whether Brilo AI or Google Voice is billed for each call before purchasing additional Brilo AI minute blocks.

Banking / Financial services example:

A regional bank uses Google Voice for a small branch phone number but routes priority customer lines into Brilo AI during off hours. Brilo AI performs identity checks, triages routine requests, and escalates complex issues to a live agent. The bank configures Brilo AI minute blocks to cover AI processing for the routed calls and confirms recording and audit requirements with their compliance team.

Insurance example:

An insurance call center retains Google Voice numbers for local agents but uses Brilo AI for 24/7 claim intake. Calls forwarded to Brilo AI consume Brilo AI minutes; claim data and call summaries are pushed into the insurer’s core system after the call.

Note: Do not treat these examples as legal or compliance advice. Confirm regulatory requirements directly with your compliance team.

When Brilo AI handles a call from a Google Voice number, Brilo AI workflows can transfer the call to a human agent, warm transfer to a queue, or create a callback task.

Handoff methods include:

Configure escalation rules so that if confidence thresholds are low (for example, failed authentication or repeated negative intent), Brilo AI automatically elevates the call to a human. Document the handoff destination (your agent queue, webhook endpoint, or external telephony provider) so minute accounting and handoff quality are traceable.

Keeping Google Voice while enabling Brilo AI can reduce migration risk and preserve local numbers, while Brilo AI minute blocks give predictable budgeting for AI processing when calls terminate at Brilo AI. Typical benefits include continuous 24/7 intake via AI voice agents, faster first‑contact resolution for routine requests, and automated CRM logging for downstream teams. Realize value only after you verify routing and minute accounting to avoid unexpected carrier charges.

Can Brilo AI use my Google Voice number without porting it?

Yes. You can forward Google Voice calls to Brilo AI for agent handling. Forwarding is often the fastest way to start, but forwarding may create extra call legs that affect minute accounting. Test call flow to confirm which provider invoices for minutes.

Will I be charged Brilo AI minutes and Google Voice minutes at the same time?

Potentially. If Google Voice terminates the PSTN leg before forwarding, your carrier may bill you for that leg while Brilo AI bills for the AI processing leg. To avoid double billing, route calls so Brilo AI receives the inbound call leg directly when you want Brilo AI minutes to apply.

Do I have to port my number into Brilo AI to use Brilo AI minute blocks?

No — porting is optional. Porting gives Brilo AI direct control of the number and typically simplifies minute accounting. Forwarding works for many setups but may change billing and metadata behavior.

How do I verify who is consuming minutes on a test call?

Run controlled test calls and review call records and billing logs from both Google Voice and Brilo AI. Check the call leg timestamps and the Brilo AI call record to see whether audio was answered by Brilo AI. If unsure, work with Brilo AI support and your carrier to correlate logs.

Will call recordings and transcripts be available if I keep Google Voice?

If Brilo AI processes the audio (i.e., answers the forwarded call), Brilo AI can generate transcripts and store recordings per your account settings. If Google Voice handles the call entirely, Brilo AI will not have the audio data unless forwarded. Confirm recording storage and retention policies with Brilo AI during setup.

If you’d like help mapping your Google Voice routing to Brilo AI and estimating minute needs, contact your Brilo AI rep or start a configuration review with the Brilo AI onboarding team.