Direct Answer (TL;DR)
Yes — Brilo AI can work with your existing published phone numbers when those numbers are routed to Brilo AI’s telephony endpoint or ported into a supported telephony setup. Brilo AI voice agent use of an existing number typically requires one of two approaches: carrier-level call forwarding to a Brilo AI number or porting the number to a SIP provider that Brilo AI can route to (number porting). Configuration depends on your telephony carrier, regulatory obligations, and the routing model you choose. When enabled, Brilo AI preserves caller experience while applying your configured routing, voicemail, and escalation rules.
Can Brilo AI use our published number?
Yes. Brilo AI can accept calls to your existing number when you forward or port it to Brilo AI’s endpoint.
Can we keep our public phone numbers with Brilo AI?
Yes. Keeping a published number is possible when your carrier forwards the number or you port it to an endpoint Brilo AI can route.
How do you route a published number to Brilo AI?
Forward or port the number to Brilo AI’s SIP endpoint or phone number; Brilo AI will then apply your configured call routing and handoff rules.
Why This Question Comes Up (problem context)
Buyers ask this because changing public numbers affects marketing materials, compliance registers, patient or customer trust, and regulatory notices. Enterprises in healthcare, banking, and insurance must avoid service disruption and preserve published numbers on websites, statements, and emergency contact records. IT and telecom teams also need clarity on whether Brilo AI requires a new number or can integrate with existing numbers via forwarding or porting.
How It Works (High-Level)
Brilo AI handles existing published phone numbers by routing incoming calls into Brilo AI workflows when one of these arrangements is in place:
Carrier-level call forwarding: your carrier forwards a published number to a Brilo AI-assigned number or SIP endpoint so Brilo AI receives the call.
Number porting / SIP routing: you port the number to a telephony provider or SIP trunk that Brilo AI can integrate with, allowing Brilo AI to answer directly on the published number.
In Brilo AI, phone number forwarding is a configuration option where carrier-level forwarding directs incoming calls to Brilo AI’s endpoint. A SIP endpoint is the network address Brilo AI uses to receive calls from your telephony provider. For more details on call capacity and routing considerations, see the Brilo AI article about handling concurrent callers: Brilo AI article on handling multiple callers.
Related technical terms: number porting, carrier-level forwarding, SIP trunk, DID, call routing, warm transfer.
Guardrails & Boundaries
Brilo AI will not change carrier billing, complete carrier-managed porting forms for you, or alter regulatory records without your carrier and legal approval. Typical guardrails:
Escalation: if forwarding or SIP routing fails, calls should fallback to a human contact or voicemail to avoid dropped calls.
Limits: number porting lead times, carrier restrictions (e.g., transfer authorization), and regulatory notifications can delay activation.
Safety: Brilo AI will apply configured consent, privacy, and session logging rules but cannot unilaterally remove required disclosures from your published channels.
A published number is any phone number you list publicly that must remain reachable; changes to published numbers require coordination with your carrier and compliance teams. For operational resilience and recovery options, review guidance on system availability and failover processes: Brilo AI system outage & recovery guidance.
Applied Examples
Healthcare: A regional clinic keeps its published patient scheduling line. The clinic forwards the published number to Brilo AI’s endpoint so the Brilo AI voice agent handles triage and appointment booking, while the clinic preserves patient-facing materials and messages.
Banking: A small bank ports a customer service number into a managed SIP trunk that routes to Brilo AI. The Brilo AI voice agent authenticates callers using the bank’s configured prompts and then routes complex disputes to human specialists.
Insurance: An insurer uses carrier-level forwarding during a pilot so existing claims lines ring Brilo AI during business hours; urgent or high-risk calls are escalated to a live adjuster per configured rules.
Note: Do not interpret examples as legal or compliance advice. Coordinate with your compliance and telecom teams for HIPAA, regulatory, or contractual obligations.
Human Handoff & Escalation
Brilo AI voice agent workflows support predictable handoffs:
Warm transfer (with context): Brilo AI can pass caller context and session metadata when transferring to a human agent or another workflow.
Cold transfer: Brilo AI can route the call to a destination number without session context when required by the carrier setup.
Fallback routing: If forwarding or SIP connectivity fails, configure fallback numbers, voicemail, or a queue to ensure no calls are silently dropped.
In practice, Brilo AI uses routing rules you configure in the workflow to decide when to escalate (for example, authentication failures, sensitive data requests, or explicit caller requests to speak to a person). See the handling and transfer considerations in our multiple-caller and routing guidance: Brilo AI article on handling multiple callers.
Setup Requirements
Verify: Confirm ownership and administrative access for the published phone number with your telecom team.
Choose: Decide between carrier-level forwarding or full number porting to a SIP provider that Brilo AI will route to.
Configure: Update carrier forwarding rules or submit porting requests through your carrier according to their process.
Provide: Share your SIP endpoint details or forwarding destination with Brilo AI support and supply expected peak concurrent calls for validation.
Test: Run inbound test calls and validate routing, voicemail, and transfer workflows.
Monitor: Validate session logs and call recordings (if enabled and permitted) to confirm call quality and routing behavior.
For integration specifics and CRM routing examples, review Brilo AI product resources such as the HubSpot integration overview: Brilo AI HubSpot integration page.
Business Outcomes
Preserve customer trust and published contact consistency.
Reduce a migration burden by avoiding immediate number changes.
Enable gradual rollouts (forwarding during pilot, porting later) to control risk.
Maintain continuity for regulated communications while applying automated triage and routing.
Outcomes depend on telecom provider timelines and your escalation policies; Brilo AI supports the routing and workflow controls that implement those outcomes.
FAQs
Do we have to port our number to use Brilo AI?
No. Porting is optional. You can use carrier-level call forwarding to route calls to Brilo AI without porting, or port the number if you want Brilo AI to answer directly on the published number.
Will call recordings remain associated with our number?
Call recordings and session logs are retained per your Brilo AI account settings and applicable policies. Ensure your retention and disclosure policies meet regulatory requirements before enabling recordings.
How long does porting or forwarding take to activate?
Porting lead times depend on your carrier and region; forwarding can often be configured quickly by your telecom admin. Brilo AI cannot control carrier processing times and will advise on testing and fallbacks.
Can Brilo AI ring both our existing call center and the Brilo AI agent at the same time?
This depends on your carrier and routing model. You can configure simultaneous ringing via your telephony provider or use Brilo AI workflow rules to perform warm transfers or parallel ring strategies when supported.
What happens if forwarding fails?
Configure fallback destinations (voicemail, alternate numbers, or human agents) to avoid dropped calls. Brilo AI recommends testing failover behavior before going live.
Next Step
If you’re ready to proceed, gather your carrier contact and number ownership details, then contact Brilo AI support or your Brilo onboarding specialist to begin forwarding or porting validation. For integration planning and CRM routing, reference: Brilo AI HubSpot integration page.
A published phone number is any phone number your organization currently publishes and wants Brilo AI to answer without changing the customer-facing contact. Number porting is the process of transferring number ownership or routing to a provider that Brilo AI can integrate with. Carrier-level forwarding is the configuration your telecom carrier applies to forward incoming calls from your published number to a Brilo AI endpoint.