Yuboto PBX

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.

What you need before you start

• 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.

What you enter

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.

First setup

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.

What it can do

• 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.

Troubleshooting

Connect says Invalid Yuboto PBX domain or API key

Enter only the first part of the PBX address in Domain, without .vpbx2.yuboto.com or https://. Check the API key with Yuboto, and that it belongs to the same PBX.

Calls end on the PBX but nothing appears 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.

The call is listed but has no transcript or summary

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

Next Steps

Get an integration working - connections and agent tools.→Workflows - build what happens after each call.→Carriers - connect the agent to Yuboto as a trunk or vPBX extension.→Call results - what the agent extracts from each call.→