Salta ai contenuti
IT
Apri l’app

For AI assistants: this page as plain markdown is at https://docs.voicelogica.ai/raw/integrations/communication/yuboto-pbx.md, and https://docs.voicelogica.ai/llms.txt lists the docs by topic, one file each, small enough to read whole. Read those rather than this HTML page.

Yuboto PBX

6 min di lettura
Copia come Markdown
Visualizza come MarkdownApri il file .md.md

Questi contenuti non sono ancora disponibili nella tua lingua.

Yuboto PBX brings the calls your people answer on a Yuboto cloud PBX (vPBX) into Voice Logica. When a call on the PBX ends, Voice Logica fetches its recording from Yuboto, an agent transcribes and summarizes it, and the call appears in Calls with the caller saved as a contact. A workflow then runs, so you can email the summary, update a CRM or alert a colleague after every call.

The path is Integrations - Catalogue - Yuboto PBX - Connect. One connection is shared by the whole company. The connection on its own does nothing: the calls come in through a workflow that starts with the On Yuboto Pbx Call Hangup trigger.

This page is about reporting on calls your team handles on the PBX. To make the agent itself answer calls as an extension of a Yuboto vPBX, see Carriers.

  • A Yuboto cloud PBX. Its address looks like yourcompany.vpbx2.yuboto.com.
  • The PBX API key from Yuboto.
  • Call recording turned on in the PBX for the extensions you want to report on. Without a recording the call is logged but not transcribed.
  • An agent to analyze the calls. Its Call results settings decide what the summary contains.
  • Access to the PBX’s call-event (webhook) settings, or Yuboto support to set them for you.

In Connect Yuboto PBX:

DomainREQUIRED
The first part of your PBX address, letters and numbers only. For yourcompany.vpbx2.yuboto.com, enter yourcompany.
API keyREQUIRED
The PBX API key. Voice Logica checks it with Yuboto before saving.

On the workflow’s On Yuboto Pbx Call Hangup trigger:

AgentREQUIRED
The agent that transcribes and analyzes these PBX calls.
Allowed Extensions
Only calls on these extensions start the workflow. Leave empty for all.
Username
Optional. With Password, only events sent with these Yuboto credentials start the workflow.
Password
Optional. Used together with Username.
  1. Integrations - Catalogue - Yuboto PBX - Connect

    Enter Domain and API key, then Connect. If Yuboto rejects them you see Invalid Yuboto PBX domain or API key.

  2. Workflows - new workflow - On Yuboto Pbx Call Hangup

    Add the trigger from Yuboto Triggers. Select the Agent, and add Allowed Extensions if only some extensions should be reported.

  3. Copy the Yuboto URL

    The trigger shows a Yuboto URL. Click Copy URL.

  4. Point the PBX at it

    In your Yuboto PBX, set the call-event webhook to POST to that URL, authenticated with the same credentials as the API key. Events with other credentials are rejected. If you do not have access to these settings, send the URL to Yuboto support.

  5. Add what should happen after each call

    Connect nodes after the trigger, for example a Send Email node with the call summary to the extension owner. The trigger gives the next nodes the call summary, status, duration, caller number, direction and a link to the call.

  6. Save and prove it

    Save the workflow. Call one of the extensions from a mobile, talk for a minute and hang up. Within a few minutes the call appears in Calls with the recording and summary, and the workflow’s action (the email) arrives.

  • Log every external call on the PBX that ends, as answered, missed, busy or failed.
  • Find the caller among your contacts by phone number, or create the contact.
  • Fetch the recording from Yuboto and have the agent transcribe and summarize it.
  • Pass the call details to a workflow: send an email or SMS, write to a CRM, create a task.
  • Limit reporting to selected extensions.
  • Ignore internal calls between extensions.
  • Skip calls your agent already handled. A call that reached the agent through the PBX and was transferred back to your team is already in Calls, with the extension that answered, so it is not added or charged a second time.

Each call that is transcribed and summarized uses analysis minutes for its length. If the company has no analysis minutes left, the call is still logged, without a transcript or summary.

Give each call to the team member who took it

Section titled “Give each call to the team member who took it”

Tell Voice Logica which team member uses which PBX extension, and every PBX call is given to that person: their name shows on the call, it is in their own calls, and it counts in their statistics. For an incoming call that is the extension that answered; for an outgoing call, the extension that dialled.

  1. Integrations - Yuboto PBX - Show details - Extensions

  2. Add extension

    Enter the extension number (for example 106) and choose the team member. Add one row per extension. A person can have more than one extension; an extension has one person.

  3. Save

    From now on, new PBX calls are given to the person on their extension. Calls logged earlier keep their owner.

A call on an extension that is not in the list, or an incoming call nobody answered, is not given to anyone. Reconnecting Yuboto PBX keeps the list. Assistants can read and change it through MCP with get_yuboto_extension_members and set_yuboto_extension_members.

Why does connecting Yuboto PBX say Invalid Yuboto PBX domain or API key?

In Domain, enter only the first part of the PBX address, without .vpbx2.yuboto.com or https://. Also check with Yuboto that the API key is correct and belongs to the same PBX.

Why don't calls from my Yuboto PBX appear in Calls?

Check, in order:

  1. The workflow with On Yuboto Pbx Call Hangup is saved and has an Agent.
  2. The PBX sends call events to the Yuboto URL of that workflow, with the same credentials as the API key.
  3. The extension is in Allowed Extensions, or the list is empty.
  4. If you filled Username and Password on the trigger, they match the credentials the PBX sends.
  5. The call was external. Calls between two extensions are skipped.
Why does a Yuboto PBX call not show the team member who took it?

Open Integrations - Yuboto PBX - Show details - Extensions and check that the extension is in the list with the right team member. The list applies to calls logged after it was saved. An incoming call that nobody answered has no extension, so it is not given to anyone.

Why does a Yuboto PBX call have no transcript or summary?

Yuboto returned no recording for that call. Turn recording on in the Yuboto PBX for that extension, then test with a new call.