Jump to content

FuturePBX: Difference between revisions

From Wiki 7Kas
Rename product Tucloud PBX -> FuturePBX (public brand launch 2026-08-03); API surface unchanged
 
Renew FuturePBX product page (brand launch): rebuilt from the published article + real product screenshots
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
[[File:FuturePBX-bird.svg|right|120px|link=|FuturePBX]]
[[File:FuturePBX-bird.png|right|130px|link=|FuturePBX]]
= Description =
'''FuturePBX''' is our new cloud PBX. Not a rename and not a refresh of the old control panel: a new service, built around one idea that changes everything — '''you manage your phone system by talking to it'''.
Help for FuturePBX.


= Programming Manual =
We believe it is the most advanced virtual PBX you can buy today, and you don't have to take our word for it: '''our code is published'''. We write the engine that runs the calls, we maintain it ourselves, and anyone can read it.
Description of everything that can be configured in our FuturePBX.


== Main Menu ==
[[File:fpbx-ai-assistant.png|thumb|center|900px|The FuturePBX AI Assistant: ask in plain language, it does the work.]]


[[File:NTuclud inicio.gif|link=''|600px|caption]]
== Talk to your phone system instead of configuring it ==
=== Extensions ===
For thirty years, administering a PBX has meant the same thing: learn a panel, remember which tab holds what, fill in forms. FuturePBX ships with an '''AI Assistant''' that breaks with all of it. You type what you need, in Spanish or English, in ordinary words:
[[File:NExtensiones.gif|link=''|1000px|caption]]


In this menu you configure everything related to extensions. Once inside, choose the extension to configure.
* ''"Create a support queue and add the three admin agents."''
* ''"Show me the extensions that aren't registered."''
* ''"Put the reception agent on pause."''


* Extension: the extension number; this is the number to dial to reach it.
And it does it. That is what separates it from a chatbot: the assistant '''doesn't just answer, it acts'''. It is wired straight into the platform's real functions and uses them as tools. When you ask for information it answers immediately; when your request changes something create, edit or delete — it '''always asks for confirmation''' before touching anything. Nothing changes on your PBX that you did not approve.
* Name: change the extension name; it is shown when calling other extensions in the system.
* Phone: choose from the drop-down which phone number you identify with when placing a call.
* Microsoft Teams: in the drop-down, choose how the extension works — as traditional VoIP, tied to Microsoft Teams (a licence is required), or both.
* Pickup group: sets the pickup group, linked to code *33. You can make all extensions in a department (e.g. Accounting) share the same group so you can pick up any ringing extension with *33.
* SIP user: the text to enter in the "User" field of your softphone or IP phone.
* Forward: in the drop-down choose how incoming calls to this extension behave.
* Forward phone: the number calls are forwarded to according to the option chosen above.
* Email: the e-mail address where the system sends voicemail recordings.
* Extension to monitor: used to enable the Backup number. Indicate the link extension, with the device where the extension is registered directly (for example a SecureSIP).
* Ring time: time in seconds the extension rings before hanging up (one ring tone is about 3 seconds).
* Record outgoing: in the drop-down choose whether to record calls; this service has an additional cost.
* Int. Mobile:
* Teams number: the number used when using Microsoft Teams.
* Send to: in the drop-down choose where incoming calls to this extension go. You can send all your calls to another extension useful if you have a local PBX.
* SIP password: the password used to register your softphone or IP phone.
* Show caller: in the drop-down choose whether caller information is displayed.
* Voicemail: in the drop-down choose whether this extension has voicemail; recorded messages are sent to the e-mail configured above.
* Backup number: called when the extension is not registered. Can be used with remote devices where the extension registers directly (for example a SecureSIP).
* Note: any information can be added here; it has no effect on the programming.


=== Hop Group ===
It also replies with '''interactive cards''': ask about an extension and you get that extension's card with an ''Edit'' button — click it and you edit right there, inside the conversation. The assistant is available as a full page and as a floating helper on every screen, resizable and maximisable.
[[File:NGrupoSalto.gif|link=''|1000px|caption]]


In this menu you configure everything related to hop groups: how the call behaves when it enters a hop group and which extensions make it up.
== A new portal — fast, and out of your way ==
* Group: the hop group number.
The portal has been rebuilt from scratch as a modern web application: navigation is instant, with no page reloads. A single data grid and a single form component are reused across the whole product, so everything behaves the same way wherever you are. '''Dark mode''' is included on every screen.
* Name: the group name, so you can identify it correctly.
* Hop 1
** Extensions: the extensions that ring first when calling.
** Ring time: how long the selected extensions ring before moving to the next hop. Enter the number in seconds or use the slider below.
** The two checkboxes select or clear the selection of all extensions.
    [[File:GrupoSalto001.gif|link=''|400px|caption]]
* Hop 2, Hop 3, Hop 4 and Hop 5: same as Hop 1; these hops run in order once the previous one has finished.


=== Locutions ===
<gallery mode="packed" heights="240px">
File:fpbx-dashboard.png|Dashboard: the state of your PBX at a glance
File:fpbx-dark-dashboard.png|The same dashboard in dark mode
</gallery>


[[File:NLocuciones001.gif|link=''|1000px|caption]]
== Your PBX in your pocket ==
FuturePBX is '''fully mobile-responsive'''. Not a cut-down version, not a separate app: the same complete portal, with a slide-in menu and forms and tables that reflow for a small screen. You can add an extension, check the call log or pause an agent from your phone, standing up, anywhere.


In this menu you manage everything related to locutions. Once inside, choose the locution to manage by clicking the [[File:Lapiz.gif|link=''|30px|caption]] icon, or click the 'Play' button [[File:Locuciones002.gif|link=''|200px|caption]] to listen to that locution.
<gallery mode="packed" heights="300px">
File:fpbx-mobile-dashboard.png|Dashboard on a phone
File:fpbx-mobile-menu.png|Slide-in menu
File:fpbx-mobile-ai.png|The AI Assistant on mobile
</gallery>


=== Locution editing ===
== Extensions and QR provisioning ==
[[File:NLocuciones003.gif|link=''|1000px|caption]]
Create, edit and delete extensions with everything you'd expect — plus '''QR-code provisioning''', so setting up a softphone no longer means reading credentials down the phone. Scan it, done.
* Number: locution number, to identify it.
* Name: a name for your locution.
* Wait for extension: in the drop-down, choose whether the caller can dial an extension number while the locution plays and be transferred to that extension.
* Locution: click the [[File:Cargar.gif|link=''|80px|caption]] icon to open a window where you choose an audio file to play for this locution. The audio file must be: WAV format, mono, 16 bit, 8 kHz.
* Route options
** For each key, choose in the drop-down what happens when the caller presses that phone key during the locution (the choices are Call Routes).


=== Call Route ===
[[File:fpbx-extensions.png|thumb|center|900px|Extension management.]]
[[File:NRutaLlamadas.gif|link=''|1000px|caption]]


In this menu you configure everything related to call routes and how a call behaves when it enters a route.
== A call log that tells you the direction ==
* Name: the route name, so you can identify it correctly.
The call detail record (CDR) now shows the '''direction''' of every call — inbound, outbound or internal — as a column of its own. A small thing you appreciate every single day when you're hunting for one specific call.
* Note: any reminder; it has no effect on the programming.
* Actions
** First press the [[File:AnadirOpcion.gif|link=''|100px|caption]] button to add a new line to the group; then click the [[File:Lapiz.gif|link=''|30px|caption]] icon to edit it.


  [[File:AnadirOpcion001.gif|link=''|1000px|caption]]
[[File:fpbx-cdr.png|thumb|center|900px|Call log with the Direction column.]]


** Priority: the order in which the line runs; numbers cannot repeat, go from lowest to highest and cannot skip.
== Routing, IVR, schedules and announcements ==
** Action: in the drop-down choose what to do, e.g. call an extension, a group, a locution…
Everything you'd expect from a professional phone system, plus one genuinely unusual tool: a '''call simulator''' that draws the path a call would take through your rules, step by step. You see the flow before a real customer has to live through it.
*** Extension action: set the extension number in 'Extension' and, below, the time it rings on that extension.
*** Group action: set the call group the call is passed to.
*** Locution action: set the locution to use.
*** Go to Priority action: jumps to the priority number you specify (use carefully to avoid loops that block the PBX).
*** Hang up action: hangs up the call (should be the last option in the call route).
*** Voicemail action: set the extension voicemail to use.
*** Jump to Route action: set which call route to go to.
*** Calendar action: choose the calendar to use from that point.
*** Schedule action: choose the schedule to use from that point.


=== Schedules ===
<gallery mode="packed" heights="240px">
[[File:NHorarios.gif|link=''|1000px|caption]]
File:fpbx-routes.png|Inbound routes and IVR
File:fpbx-simulator.png|The simulator: the call's journey, step by step
</gallery>


In this menu you configure everything related to schedules.
Alongside those: ring groups, calendars and time-based routing, announcements and voicemail, music on hold, blacklists, contact directories, and outbound rules with caller-ID selection.
* Name: the schedule name, so you can identify it correctly.
* Monday to Sunday: set each day's schedule; if a day has no schedule (e.g. weekends) leave everything at 00:00:00.


** Time A: start of the working day.
<gallery mode="packed" heights="220px">
** Time B: first programming change (e.g. midday break start).
File:fpbx-schedules.png|Schedules and calendars
** Time C: next programming change (e.g. afternoon start).
File:fpbx-locutions.png|Announcements and voicemail
** Time D: next programming change (e.g. afternoon end).
File:fpbx-music.png|Music on hold
** Time E to L: next programming changes.
</gallery>


=== Calendar ===
== Queues and agents: rolling out ==
[[File:NCalendario001.gif|link=''|1000px|caption]]
FuturePBX brings '''call queues with automatic call distribution (ACD)''': inbound calls are shared out across a team of agents using the strategy you pick — ring everyone, longest idle, fewest calls, round robin and more. Agents log in, pause and check their status with short codes from their own handset; callers hear hold music and wait announcements; and if nobody answers in time, the call is forwarded on. The system only rings phones that are actually registered and free, and configuration changes apply to live calls without restarting anything.


In this menu you configure everything related to calendars; here you can set holiday dates.
{{Note|Being straight with you: managing queues and agents from the portal already works, but '''running queues over real live calls is in its final rollout phase'''. We're telling you now because it is part of what's coming, not because you can use it today. We'll announce the date once the rollout is complete and verified.}}
* First press the [[File:AnadirOpcion.gif|link=''|100px|caption]] button to add a new line to the calendars; then click the [[File:Lapiz.gif|link=''|30px|caption]] icon to edit it.


  [[File:Calendario002.gif|link=''|500px|caption]]
<gallery mode="packed" heights="240px">
File:fpbx-queues.png|Call queues with automatic distribution
File:fpbx-agents.png|Agent management
File:fpbx-dark-queues.png|Queues in dark mode
</gallery>


* Calendar: the calendar number to edit.
== Underneath: an API that does everything ==
* Start Month / Start Day / Start Time: when the holiday starts.
The portal is not the product; it is a client of the product. Underneath sits our own '''REST API''' with close to 140 functions across some 28 areas, covering '''100% of PBX management'''. Anything you can do with a mouse you can do over the API — including the AI Assistant itself, which is simply another client of that same API.
* End Month / End Day / End Time: when the holiday ends.
* Destination: the call route the call goes to.
* Keep: in the drop-down choose whether it repeats every year or only once.
* Note: annotations; no effect on the programming.


=== Numbering ===
If you want to wire FuturePBX into your CRM, your ERP or your own tooling, the door is open and documented. The platform is '''multi-tenant''' from day one: every PBX is isolated from every other, and every request is key-authenticated and scoped to the role that makes it. Full reference: [[TuCloudAPI]].


[[File:NNumeracion001.gif|link=''|1000px|caption]]
== And you can drive it from outside: automation platforms and AI agents ==
You don't have to be the one operating it. The API is standard HTTPS with JSON responses and key authentication, so '''any automation platform can drive it with a plain HTTP module''' — Make.com, n8n, Zapier, Power Automate, or whatever you already use. Nothing to install, no connector to write.


In this menu you manage everything related to the numbering registered in this FuturePBX. Once inside, choose the number to manage by clicking the [[File:Lapiz.gif|link=''|30px|caption]] icon.
What that gets you, in practice:
* A deal closes in your CRM and the PBX creates the new rep's extension by itself.
* Someone joins in your HR system and their phone is provisioned before day one.
* At a given hour — or when your calendar says it's a public holiday — the PBX switches the routing to night mode.
* Your helpdesk flags a ticket as urgent and reorganises the queue that answers it.


[[File:NNumeracion002.gif|link=''|1000px|caption]]
And the next step, where this gets genuinely interesting: the PBX is '''built to be operated by an AI'''. The API describes itself — close to 140 functions with their parameters, types and real examples, queryable live — which is exactly what a language model needs to discover them and use them as tools. Your own AI agent can run your phone system: query it, decide, and act. This isn't theory: our own AI Assistant works precisely that way, as another client of that same public API.


* CLI: the number being configured.
Every API key is scoped to its own PBX — one customer's automation cannot see or touch another's — and keys can be issued read-only when all you need is to look.
* Record received calls: in the drop-down choose whether incoming calls are recorded (this service has an additional cost).
* Calendar: choose the calendar for this number.
* Schedule: choose the schedule for this number.
** Time A to L: choose the Call Route that runs when each 'Time' starts.


* Schedule options
== Simultaneous translation: everyone speaks their own language ==
** Default route: call route used if there is any inconsistency in the programmed schedules.
FuturePBX integrates '''simultaneous, automatic call translation''': each person speaks their own language and hears the other in theirs, while the conversation is happening. Nothing to install, nothing to press, no waiting your turn.
** Forced route: call route used ignoring the time programming.
** Forced time: forces the chosen time, ignoring the PBX schedule.


* Note: any data; not used for the programming.
The difference is in how we do it: '''we work directly from voice to voice'''. The conversation is never turned into text — it is not transcribed, that text is not translated, and nothing is read back aloud. That detour through text is exactly what makes conventional solutions sound slow and robotic. Because we skip the text, the translated voice arrives while the conversation is still alive, and it sounds like a conversation, not a dictation.


=== Incoming Routing ===
The system also '''detects the language by itself''' — nobody configures anything before calling, and if both people already speak the same language, the translation steps aside. It can be used directly as a service and is fully integrated into FuturePBX, so switching it on for an extension, a route or a queue is just another option in your phone system.


[[File:NEEntrante.gif|link=''|1000px|caption]]
== The engine: our own software, in the open ==
Almost every cloud PBX on the market is the same old PBX with a different logo on top. Ours isn't. We develop and maintain our own telephony platform, '''GabPBX''' — an open-source fork of Asterisk — and our own SIP engine, '''chan_sofia'''. All of it published as free/open-source software under the GPL.


In this menu you configure how the PBX behaves based on an incoming number.
chan_sofia is the component that handles every call, every registration and every message, built on the proven sofia-sip stack as a drop-in replacement for the legacy telephony driver older systems still run. In practice: your existing SIP phones and providers keep working, and you gain '''calling straight from a web browser (WebRTC)''' with nothing to install, transport encryption end to end (TLS/WSS and SRTP/DTLS), video, presence and busy-lamp (BLF) keys, and several devices registered to one account — desk phone, softphone and browser, all at once.


* First press the [[File:NUEVO.gif|link=''|60px|caption]] button to add a new incoming-routing line.
Published code is the difference between being able to check what the system you pay for actually does, and having to trust a brochure. You can audit it, your team can study it, and you are not betting on one company continuing to exist.


  [[File:EEntrante001.gif|link=''|500px|caption]]
== Open documentation ==
The whole platform is documented, function by function, on this wiki — parameters, call examples and real responses, in Spanish and English. No sign-up, nothing asked in return. Start with '''[[TuCloudAPI]]''' (the REST API reference) and its self-discovery endpoint '''[[TuCloudAPI help]]'''.


* Source number: the number for which you set an exclusive programming.
<gallery mode="packed" heights="240px">
* Called number: in the drop-down, the number the call came in through.
File:fpbx-wiki-index.png|The wiki: every function documented, with parameters and examples
* Priority: the order in which the programming is placed; you can have several programmings for the same number, run from lowest to highest.
File:fpbx-wiki-aichat.png|Public API documentation
* Note: any data; no effect on the programming.
</gallery>


=== Call Detail ===
== Availability ==
 
FuturePBX is on the home straight. We are finishing the production rollout and it is '''expected to go on sale in September'''. We have spent years rewriting this platform layer by layer — FuturePBX is the piece that was missing on top: the one that finally puts all of that work within reach of anyone who can describe what they need.
[[File:NDetalleLlamadas.gif|link=''|1000px|caption]]
 
In this menu you can see the calls made and received. Choose Year, Month and Day and it shows a list of calls for that date.
 
[[File:NDetalleLlamadas001.gif|link=''|1000px|caption]]
 
After pressing 'Search' the call list is shown; it can be modified, exported, printed…
 
* Fields:
: [[File:NDetalleLlamadas002.gif|link=''|1000px|caption]]
: Choose which fields are shown in the list.
 
* Sort by:
: [[File:NDetalleLlamadas003.gif|link=''|1000px|caption]]
: Choose which field(s) to sort the list by. You can choose several; the list is sorted in the order you pick them.
 
* Export:
: [[File:NDetalleLlamadas004.gif|link=''|1000px|caption]]
: Choose what to do with the list — export it in several formats or print it.
 
* Advanced search:
: [[File:NDetalleLlamadas006.gif|link=''|1000px|caption]]
: A search with more options than the initial one.
 
* Dynamic search:
: [[File:NDetalleLlamadas007.gif|link=''|1000px|caption]]
: Filter the list you already have to refine the search further.
: [[File:NDetalleLlamadas008.gif|link=''|1000px|caption]]
: A button [[File:DetalleLlamadas009.gif|link=''|100px|caption]] appears to add a field that, once filled in, filters the list by that new data.
 
=== Contacts ===
 
[[File:NContactos001.gif|link=''|1000px|caption]]
 
In this menu you manage a contacts directory; you can call with the code assigned, and when the contact calls their name appears on the phones.
* First press the [[File:NUEVO.gif|link=''|80px|caption]] button to open a new contact card. If it already exists, click the [[File:Lapiz.gif|link=''|30px|caption]] icon to edit it.
 
  [[File:Ncontactos002.gif|link=''|500px|caption]]
 
* Name: the contact name; shown on phones when they call.
* Phone: the phone number.
* Short code: a number to call the contact quickly.
 
=== PBX Password ===
 
[[File:NContra.gif|link=''|1000px|caption]]
 
In this menu you set the PBX password.
 
* Password: the new password to use.
* Note: any data; no effect on the programming.
 
= Feature Codes =
Codes you can use directly from the phone to enable or disable FuturePBX features.
 
== Anonymous call ==
*31* + Destination No.
Lets you place a call with a hidden number. Note: on some devices such as Grandstream, feature codes must be disabled, as they conflict.
 
=== Group pickup ===
*33
Picks up the call ringing on any extension.
 
=== Directed pickup ===
*33 + Extension No.
Picks up the call ringing on a specific extension, whether or not it belongs to a group.
 
=== Pickup group ===
*34 + Group
Picks up the call ringing on any extension within an assigned pickup group.
 
== Locutions and Voicemail ==
 
=== Listen to and record locutions ===
*40 + LOCUTION No.
To listen to one of the locutions recorded in your FuturePBX, press *40 + LOCUTION No. and choose option 1. To record a new locution, press *40 + LOCUTION No. and choose option 2.
 
=== Voicemail ===
*69
Listen to the messages left in your voicemail, change the mailbox greeting and other options.
 
== Change time programming ==
*5X
 
In the PBX you can customise the incoming-call route for each of the "times" you define. From your phone you can force all calls to enter through the route matching "time X" simply and immediately. It is in automatic mode by default, and is switched quickly with these codes:
 
* *500 + DDI number — automatic time
* *501 + (DDI number or Schedule) — time A
* *502 + (DDI number or Schedule) — time B
* *503 + (DDI number or Schedule) — time C
* *504 + (DDI number or Schedule) — time D
* *505 + (DDI number or Schedule) — time E
* *506 + (DDI number or Schedule) — time F
* *507 + (DDI number or Schedule) — time G
* *508 + (DDI number or Schedule) — time H
* *509 + (DDI number or Schedule) — time I
* *510 + (DDI number or Schedule) — time J
* *511 + (DDI number or Schedule) — time K
* *512 + (DDI number or Schedule) — time L
 
Where the DDI number is the assigned number and Schedule is the schedule to activate, e.g. 01 = Schedule 1, 02 = Schedule 2, 03 = Schedule 3, …
 
== Disable forwards ==
* *700: disables ALL forwards (internal and external)
* *710: disables ONLY external forwards
* *720: disables ONLY internal forwards
 
To enable forwards, the format is *7XYdestination where:
 
X sets the scope:
* 0: affects both (internal and external)
* 1: affects external calls only
* 2: affects internal calls only
 
Y sets the forward type:
* 1: unconditional forward
* 2: forward if busy
* 3: forward if no answer
* 4: forward if busy or no answer
 
Examples:
* *701900123456: unconditional forward for ALL calls to 900123456
* *711900123456: unconditional forward for EXTERNAL calls only to 900123456
* *721100: unconditional forward for INTERNAL calls only to extension 100
* *703900123456: forward if no answer for ALL calls
* *713900123456: forward if no answer for EXTERNAL calls only
 
Backward compatibility with the old format: the old codes still work and affect both call types:
* *70: disables all forwards
* *71destination: unconditional forward for all calls
* *72destination: forward if busy for all calls
* etc.
 
The function now automatically determines the scope from the dialled code format and updates only the necessary database fields accordingly.
 
== Group calls ==
*6XX
 
From your phone you can call any group knowing its code, where 'XX' is the group code. For example:
* *601 call to group 1
* *602 call to group 2
 
== Callback ==
30
 
'Callback' is a useful function that sets up an automatic call when the destination could not originally be reached. It triggers in two common cases:
# Busy signal
# No answer
 
== On-demand recording ==


[[Category:FuturePBX]]
[[Category:FuturePBX]]

Latest revision as of 14:04, 3 August 2026

FuturePBX
FuturePBX

FuturePBX is our new cloud PBX. Not a rename and not a refresh of the old control panel: a new service, built around one idea that changes everything — you manage your phone system by talking to it.

We believe it is the most advanced virtual PBX you can buy today, and you don't have to take our word for it: our code is published. We write the engine that runs the calls, we maintain it ourselves, and anyone can read it.

The FuturePBX AI Assistant: ask in plain language, it does the work.

Talk to your phone system instead of configuring it

For thirty years, administering a PBX has meant the same thing: learn a panel, remember which tab holds what, fill in forms. FuturePBX ships with an AI Assistant that breaks with all of it. You type what you need, in Spanish or English, in ordinary words:

  • "Create a support queue and add the three admin agents."
  • "Show me the extensions that aren't registered."
  • "Put the reception agent on pause."

And it does it. That is what separates it from a chatbot: the assistant doesn't just answer, it acts. It is wired straight into the platform's real functions and uses them as tools. When you ask for information it answers immediately; when your request changes something — create, edit or delete — it always asks for confirmation before touching anything. Nothing changes on your PBX that you did not approve.

It also replies with interactive cards: ask about an extension and you get that extension's card with an Edit button — click it and you edit right there, inside the conversation. The assistant is available as a full page and as a floating helper on every screen, resizable and maximisable.

A new portal — fast, and out of your way

The portal has been rebuilt from scratch as a modern web application: navigation is instant, with no page reloads. A single data grid and a single form component are reused across the whole product, so everything behaves the same way wherever you are. Dark mode is included on every screen.

Your PBX in your pocket

FuturePBX is fully mobile-responsive. Not a cut-down version, not a separate app: the same complete portal, with a slide-in menu and forms and tables that reflow for a small screen. You can add an extension, check the call log or pause an agent from your phone, standing up, anywhere.

Extensions and QR provisioning

Create, edit and delete extensions with everything you'd expect — plus QR-code provisioning, so setting up a softphone no longer means reading credentials down the phone. Scan it, done.

Extension management.

A call log that tells you the direction

The call detail record (CDR) now shows the direction of every call — inbound, outbound or internal — as a column of its own. A small thing you appreciate every single day when you're hunting for one specific call.

Call log with the Direction column.

Routing, IVR, schedules and announcements

Everything you'd expect from a professional phone system, plus one genuinely unusual tool: a call simulator that draws the path a call would take through your rules, step by step. You see the flow before a real customer has to live through it.

Alongside those: ring groups, calendars and time-based routing, announcements and voicemail, music on hold, blacklists, contact directories, and outbound rules with caller-ID selection.

Queues and agents: rolling out

FuturePBX brings call queues with automatic call distribution (ACD): inbound calls are shared out across a team of agents using the strategy you pick — ring everyone, longest idle, fewest calls, round robin and more. Agents log in, pause and check their status with short codes from their own handset; callers hear hold music and wait announcements; and if nobody answers in time, the call is forwarded on. The system only rings phones that are actually registered and free, and configuration changes apply to live calls without restarting anything.

Being straight with you: managing queues and agents from the portal already works, but running queues over real live calls is in its final rollout phase. We're telling you now because it is part of what's coming, not because you can use it today. We'll announce the date once the rollout is complete and verified.

Underneath: an API that does everything

The portal is not the product; it is a client of the product. Underneath sits our own REST API with close to 140 functions across some 28 areas, covering 100% of PBX management. Anything you can do with a mouse you can do over the API — including the AI Assistant itself, which is simply another client of that same API.

If you want to wire FuturePBX into your CRM, your ERP or your own tooling, the door is open and documented. The platform is multi-tenant from day one: every PBX is isolated from every other, and every request is key-authenticated and scoped to the role that makes it. Full reference: TuCloudAPI.

And you can drive it from outside: automation platforms and AI agents

You don't have to be the one operating it. The API is standard HTTPS with JSON responses and key authentication, so any automation platform can drive it with a plain HTTP module — Make.com, n8n, Zapier, Power Automate, or whatever you already use. Nothing to install, no connector to write.

What that gets you, in practice:

  • A deal closes in your CRM and the PBX creates the new rep's extension by itself.
  • Someone joins in your HR system and their phone is provisioned before day one.
  • At a given hour — or when your calendar says it's a public holiday — the PBX switches the routing to night mode.
  • Your helpdesk flags a ticket as urgent and reorganises the queue that answers it.

And the next step, where this gets genuinely interesting: the PBX is built to be operated by an AI. The API describes itself — close to 140 functions with their parameters, types and real examples, queryable live — which is exactly what a language model needs to discover them and use them as tools. Your own AI agent can run your phone system: query it, decide, and act. This isn't theory: our own AI Assistant works precisely that way, as another client of that same public API.

Every API key is scoped to its own PBX — one customer's automation cannot see or touch another's — and keys can be issued read-only when all you need is to look.

Simultaneous translation: everyone speaks their own language

FuturePBX integrates simultaneous, automatic call translation: each person speaks their own language and hears the other in theirs, while the conversation is happening. Nothing to install, nothing to press, no waiting your turn.

The difference is in how we do it: we work directly from voice to voice. The conversation is never turned into text — it is not transcribed, that text is not translated, and nothing is read back aloud. That detour through text is exactly what makes conventional solutions sound slow and robotic. Because we skip the text, the translated voice arrives while the conversation is still alive, and it sounds like a conversation, not a dictation.

The system also detects the language by itself — nobody configures anything before calling, and if both people already speak the same language, the translation steps aside. It can be used directly as a service and is fully integrated into FuturePBX, so switching it on for an extension, a route or a queue is just another option in your phone system.

The engine: our own software, in the open

Almost every cloud PBX on the market is the same old PBX with a different logo on top. Ours isn't. We develop and maintain our own telephony platform, GabPBX — an open-source fork of Asterisk — and our own SIP engine, chan_sofia. All of it published as free/open-source software under the GPL.

chan_sofia is the component that handles every call, every registration and every message, built on the proven sofia-sip stack as a drop-in replacement for the legacy telephony driver older systems still run. In practice: your existing SIP phones and providers keep working, and you gain calling straight from a web browser (WebRTC) with nothing to install, transport encryption end to end (TLS/WSS and SRTP/DTLS), video, presence and busy-lamp (BLF) keys, and several devices registered to one account — desk phone, softphone and browser, all at once.

Published code is the difference between being able to check what the system you pay for actually does, and having to trust a brochure. You can audit it, your team can study it, and you are not betting on one company continuing to exist.

Open documentation

The whole platform is documented, function by function, on this wiki — parameters, call examples and real responses, in Spanish and English. No sign-up, nothing asked in return. Start with TuCloudAPI (the REST API reference) and its self-discovery endpoint TuCloudAPI help.

Availability

FuturePBX is on the home straight. We are finishing the production rollout and it is expected to go on sale in September. We have spent years rewriting this platform layer by layer — FuturePBX is the piece that was missing on top: the one that finally puts all of that work within reach of anyone who can describe what they need.