Using Yeastar? How to evaluate every call your PBX already records with AI
Yeastar P-Series records your team's calls. Connected to BRIGGS through the official API, every recording is transcribed and scored against your own scorecard.
Short answer
If your company runs a Yeastar P-Series PBX, whether Cloud Edition, Software Edition or Appliance Edition, your calls are probably already being recorded. The recordings sit on the PBX, organized by extension and date, waiting for someone to listen. In most operations, almost nobody does.
BRIGGS connects to Yeastar's official API and fetches those recordings on its own. Every few minutes it picks up new calls, downloads the audio, transcribes it and evaluates each one against your company's scorecard. Managers can then see:
- the score for each extension on every call, with the reasoning behind each criterion;
- the contact reasons and what drives the most complaints;
- the customers who talked about canceling, complaining or going to Procon (Brazil's consumer protection agency);
- what to coach each person on, with the exact moment in the conversation.
Nothing is installed on the PBX, and agents keep working exactly as they do today.
What Yeastar already gives you, and what's missing
Yeastar handles the telephony side well: queues, extensions, IVR, inbound numbers (DIDs) and recording. The call log, known as Call Detail Records (CDR), shows who called, which extension answered, how long the call lasted and whether it was recorded.
That data answers volume questions. How many calls the queue received, when the peak hit, which extension took the most calls. It doesn't answer questions about what was said:
- Did the agent confirm the customer's details before moving on?
- Did they explain the timeline and the next step?
- Did the customer hang up with the problem solved?
- Did anyone promise something the company can't deliver?
For that, someone has to listen. That's the part BRIGGS takes over.
How the integration works
The connection uses the API Yeastar itself provides on the P-Series. The setup is short and happens once:
- The PBX administrator goes to Integrations → API in the Yeastar web portal and creates a Client ID and a Client Secret. The official documentation describes this in the API authorization rules.
- Those two credentials are entered in BRIGGS.
- BRIGGS uses them to request an access token from the PBX, following the OAuth 2.0 standard, and starts querying recordings and CDR.
There's no agent to install on the server, and no change to the agent's extension or phone. On your side, the only thing to allow is access to the PBX API. No other port needs to be opened.
Whoever manages your Yeastar, whether in-house staff or your reseller, can usually do this quickly.
The extension becomes the person being evaluated
In Yeastar, each agent usually has their own extension. BRIGGS uses that link: the extension that answered the call identifies the employee who gets the score. The evaluation reaches the right person without any manual tagging on each call.
That lets supervisors follow each person's progress week over week, compare the team on the same criteria and see whether last month's training changed anything.
A scorecard for each type of call
The same PBX usually handles very different situations: sales, support, collections, scheduling. Grading all of them with the same checklist makes no sense.
In BRIGGS, queues, DIDs and extensions can each have their own scorecard. In practice:
- whoever answers the sales number is evaluated on understanding the need, handling objections and proposing the next step;
- whoever answers the support queue is evaluated on solving the problem and confirming the fix with the customer;
- whoever answers collections is evaluated on following the mandatory script and negotiating within the rules.
Each scorecard is written in plain language, using the criteria the company already applies in manual monitoring.
Only the calls that matter
Not every call deserves an evaluation. A ten-second call that dropped, or an internal call between two colleagues, would only pollute the metrics. So in the integration settings, the company can:
- skip short calls below a minimum duration;
- skip internal calls from extension to extension;
- pick a cutoff date, meaning the point from which recordings start coming into BRIGGS.
You can also start with one queue or one team and expand later, as managers get used to the reports.
What changes in the management routine
The whole operation, not a sample
In manual monitoring, the supervisor picks a few calls per person and listens when there's time. With BRIGGS, every recorded call in scope is evaluated a few minutes after it reaches the PBX. The monthly score no longer depends on which calls someone happened to choose.
Feedback with evidence
Every failed criterion comes with the reasoning and the excerpt from the conversation. Feedback stops being an impression and points to the exact moment: "here the customer asked about the timeline and got no answer."
Why people call, without listening one by one
Beyond the score, each call gets a contact reason and a reading of the customer's sentiment at the start and at the end. Managers see which topics grew during the week and open only the calls that matter. We cover this in detail in speech analytics with Yeastar.
Calls and WhatsApp in one place
If the team also serves customers on WhatsApp, those conversations can come into the same BRIGGS account, with chat-specific criteria. Agents are evaluated on all of their work.
Frequently asked questions
Do I need to switch PBXs? No. BRIGGS uses the recordings and call records Yeastar already produces.
Does it work with Yeastar in the cloud and on our own server? The integration uses the P-Series API, available in the Cloud, Software and Appliance editions. What needs to be allowed is BRIGGS's access to that API.
Will agents notice any difference? No. Nothing changes on the phone, in the app or in the way they handle calls.
Can we evaluate only some queues? Yes. You choose which queues, DIDs or extensions are included, and you can change that later.
Does the call need to be recorded? Yes. BRIGGS evaluates the audio, so only calls Yeastar recorded are included. Recording is still configured on the PBX, as it is today. Learn more in call recording on Yeastar.
To go deeper: speech analytics with Yeastar, quality monitoring with Yeastar and call recording on Yeastar.
Using Yeastar and want to see your calls evaluated? Talk to us.