Skip to main content
Brilo connects to your stack in four ways: it answers a number you already own, it runs actions in apps you connect from the app store, it sends call data to your own software, and it sends email from your domain. Most setups use two of the four.

​
The four ways Brilo connects

Each row below is a different kind of connection, with a different setup and a different person who owns it. This page points you at the right one. It deliberately does not list every app, because the app store in your dashboard is the live answer to that and it changes more often than this page does.

​
Your phone system

You do not have to move your phone system to use Brilo. Any phone system that can forward a number to another number can send calls to a Brilo agent, and your team carries on as before.

​
Your apps

Connecting an app does two things. It lets your agent look something up mid call, so it can tell a caller their order status or find a free appointment slot. And it lets your agent write back, so a new lead or a call summary lands where your team already works. A connected app does nothing on its own. You choose which actions your agent gets, and when each one runs.

​
Your own software

When the app store does not cover something, there are two routes and neither waits on Brilo to build anything. A custom action lets your agent call your system during a conversation, including reading the answer back to the caller. A webhook sends the details of every call to your system after it ends, which suits reporting and record keeping.

​
Your email domain

Your agent can send email from your own address rather than ours, which matters when the reply lands in a customer’s inbox next to the rest of your correspondence.

​
FAQ

Almost certainly, by forwarding. Any phone system that can forward a number to another number can send calls to a Brilo agent, and RingCentral and most cloud phone systems can. Importing the number itself into Brilo needs Twilio, Telnyx or Plivo.
Yes, two ways. A custom action lets your agent call your system during a conversation, and a webhook sends the details of every call to your software after it ends. Both need someone technical for about an hour. See Build a custom action.
The actions using it stop working. Your agent keeps answering calls, but any action that reached the disconnected app fails, and your agent follows whatever your instructions say for that case. Write that fallback before you go live rather than after.
Your plan does not include it. The app store is on the higher paid plans, and which ones is listed on Plans and what they include. Webhooks work on every plan, including Free, so you can send call data out before you upgrade.
Forward first, move later. Forwarding takes minutes, leaves your current provider untouched, and reverses in a minute, so it is how you evaluate. Moving the number is how you consolidate once you are committed. See Use your existing number for both routes.