Blureon PBX

Yes, on the web interface: the product name, the logo, the browser tab icon and the main colour, with a brand chosen for each customer company. White-label is included in Enterprise and can be added to the other paid packages. Emails sent to users keep the Blureon PBX name for now. The Blureon Phone app keeps its name; on Enterprise, on Mac and Windows, it shows the company’s name and logo.

Yes, on your own infrastructure or at the end client’s site, when their policy requires on-premises.

You choose a package (PBX Free, PBX Essential, PBX Business, PBX Pro or PBX Enterprise) and a size, unlimited too on Business, Pro and Enterprise. You pay monthly or yearly, or once, for the lifetime licence, as much as 4 years of subscription. The prices are on this page.

That we use it with real calls on our own test phone system, but we still change it often; we will call it commercial once it runs at the first customers. The AI features are built, but we have not yet tested them with a real AI provider. Meanwhile you can request a test PBX: we set it up on our server for 14 days, which we can extend; it receives calls on our test number and cannot call out.

It is a multi-tenant phone system (PBX), installed at your site (the cloud version is in preparation), with built-in AI features: an agent that generates the call flow from a natural-language description, voice agents, transcripts and summaries. It brings together in one product the telephony features a company needs.

On-premises, we install the platform on your own server. In the cloud, a version still in preparation, we will run it in Blureon's infrastructure and take care of updates and maintenance. The core features are the same; what differs are the implementation requirements, maintenance and the responsibilities of each party.

You describe in plain language what should happen with calls — departments, opening hours, what happens if nobody answers. The agent generates the configuration: voice menu, time conditions, call queues, destinations and exception rules. The flow appears in the visual editor, where you review it, modify it and publish it. The configuration only goes live after you approve it.

Yes. You bring them in through your current operator's SIP trunk. From January 2027, expected, you can also port them to Blureon; we coordinate the porting procedure.

They are agents that answer the call, can collect basic information and can handle repetitive requests: appointments, status checks, routing to the right team. They are built into the call flow, and the call audio goes in real time to OpenAI, with your key. They are different from the agent that builds the configuration.

Yes. Each company’s data is kept separate, and white-label puts your brand on the web interface. Each company’s administrator makes the routine changes (users, extensions, numbers, voice menus, schedules, queues) from the same interface and sees only their own company; the companies, licences and phone system settings stay with you.

For routine flows, an administrator can make changes from the visual editor, starting from a natural-language description. Complex configurations — integrations, scenarios with many exceptions, specific routing requirements — may need technical validation, and that is where our team steps in.

For calls configured for analysis: the transcript, the summary, the tone of the conversation and the topics discussed; the topics report brings them all together. The recording or the text goes directly from the phone system to the AI provider you chose, with your key. It depends on the account configuration and on consent for recording.

Yes. SMS goes out through your own gateway (GSM, SMPP or HTTP). WhatsApp can only send messages for now, not receive them.

Request a test PBX; we set it up ourselves, after a short talk. If you want to use it with real customers before the commercial release, you join the early access programme: we look at what you use now, give you the licence and set it up together.