The Week Refunds Doubled: What 38 Phone Calls and One Meeting Already Knew

On Thursday afternoon, the refund count was 71.

The week before it had been 29. Nora, who runs customer operations at Brightline, a home-internet provider with about 80 people, saw the number in the finance report and did what everyone does: she opened the billing system and filtered by refund reason.

Most of them said Other.

Brightline is a made-up company, but the week is a familiar one. The reason for the refunds wasn’t in the billing system. It had been said out loud, dozens of times, on the phone — and once, before any of it happened, in a meeting.

A phone system that does its job, and nothing more

Brightline runs 3CX on its own server, like thousands of companies that set up an open PBX years ago and never had a reason to change it. The support floor uses desk phones; everyone else uses the 3CX softphone on their computer. Calls connect, voicemail works, and the system can record.

What it doesn’t do is understand. There are no transcripts, no summaries, nothing that can tell you what customers were calling about this week. The recordings that do exist sit on the server, and nobody has time to listen to them.

That’s not a 3CX problem. It’s the normal state of business phones:

• Open and on-premises PBXs — 3CX, FreePBX and other Asterisk-based systems — route calls; they don’t analyse them.
• Long-lived desk-phone systems from Mitel and Avaya are the same.
• Cloud systems such as RingCentral and Zoom Phone now add notes and a summary to each call — useful, but one call at a time.

Brightline wasn’t going to replace a phone system that works just to get AI. And even a phone system’s own AI only sees what happens on that platform. Brightline’s account managers meet business customers on Microsoft Teams, and sometimes in person. None of that goes through 3CX.

The question, asked once

A few weeks earlier, Brightline had started capturing its calls and meetings with ActiveLens. So on Thursday Nora opened Ask Anything and typed the question exactly as she’d have asked a colleague:

The answer came back as a chart, with the evidence underneath:

• 71 refunds this week, up from 29.
• More than half came from one issue: customers charged twice after Tuesday’s billing update — 38 of them.
• The rest were spread across late deliveries, the wrong plan on renewal and damaged equipment.
• Quotes from the calls themselves: “I was charged twice this month, right after you changed the billing…”

She clicked Show these 38 calls. They were all there — from the desk phones on the support floor and the softphones in billing — each with its transcript and summary, and each one dated after Tuesday.

Then she asked the obvious follow-up: what changed on Tuesday? The answer pointed to a meeting, not a call: Monday’s Teams call with the billing vendor, where the update was scheduled for Tuesday morning and someone asked, almost in passing, whether existing payment methods would be charged again. Nobody had followed up.

The fix was already moving. One of the calls had produced a task on the Active Board, Fix duplicate charge after billing update, assigned to Tech Support. By the time Nora found it, its status had changed to In progress.

The whole thing took a few minutes. The week before, it would have taken a meeting, a spreadsheet and a guess.

Why it worked: nothing had to change on the phones

The clever part isn’t the chart. It’s that every one of those conversations was captured in the first place, on a phone system with no AI and no integration, without asking anyone to change how they work.

Softphones: captured on the computer

ActiveLens records on the computer, not inside the phone system. It recognises when a call starts and ends in the 3CX softphone — or any other softphone or dialer — and captures the number on the other end, with nothing to press and no IT project.

Desk phones: the ActiveLens device

On the support floor, a small ActiveLens device sits between each desk phone and its handset and passes the call audio to the computer. Pick up the handset and recording starts on its own. The phone system never knows it’s there, which is why it works the same on 3CX, FreePBX, Mitel or Avaya. How phone capture works.

Meetings: in the same place as the calls

Teams, Zoom and Google Meet meetings, and meetings in the room, land in the same record as the calls. That’s what let one question connect 38 customer calls to a vendor meeting on Monday. Meetings in ActiveLens.

Mobile calls: the one place you need an integration

Brightline’s field technicians call customers from their mobiles, and those calls don’t pass through a computer. Capturing mobile calls takes a phone-system integration. ActiveLens connects to RingCentral, Zoom Phone, Quo (formerly OpenPhone) and Phone.com, and on those systems mobile calls are captured through the account, with nothing installed on the phone.

What about the phone system’s own AI?

If you’re on RingCentral or Zoom Phone, you already get notes and a summary for each call. That’s useful, and it’s where ActiveLens starts, not where it ends. A summary tells you what happened on one call. It couldn’t have told Nora why refunds doubled.

What Brightline’s week actually needed was everything around the summary:

• Questions across every call and meeting, answered with a chart and the calls behind it, not one call at a time.
• Meetings from every platform — Teams, Zoom, Google Meet, in the room — in the same record as the calls.
• Tasks with an owner on the Active Board, which anyone in the company can take, even people who never take calls.
• The follow-up work drafted: the email, the next meeting and the CRM update, waiting for approval.
• Answers during the call from your own documents, with Call Intelligence.
• An agent for the calls nobody answers, which hands off instead of guessing.

That’s why ActiveLens connects to RingCentral, Zoom Phone, Quo and Phone.com rather than replacing them: the calls come in through the account, and everything above is added on top.

Friday, 9:42 PM

The fix shipped on Friday afternoon. But customers who’d been charged twice kept calling, including after hours, when nobody was there to answer.

This is the part of the story that’s still new. Brightline was one of the first teams on the ActiveLens AI Call Agent, which is rolling out in early access. The agent answers routine calls the way your best reps would, because it learns from the calls and meetings your team has already had. It works with any phone system that can forward a call — including 3CX — so Brightline pointed its after-hours calls at it.

When a customer called on Friday night asking for a refund for the double charge, the agent didn’t invent an answer or promise money nobody had approved. It told the caller that someone from billing would call back in the morning, and created a task with the summary, the transcript and the caller’s history attached.

On Saturday morning, the billing team had a list of exactly who to call back, and why. Nothing fell between the cracks.

What to take from Brightline’s week

1. 1The reason is usually in the conversations. Billing and CRM fields record what happened; calls and meetings record why.
2. 2You don’t need a new phone system to get AI. A PBX that only routes calls is fine, as long as the calls are captured.
3. 3Calls and meetings belong in one place. The cause was in a meeting; the effect was on 38 calls.
4. 4Every answer should lead to a task with an owner. Knowing why is only useful if someone fixes it.
5. 5After-hours calls deserve the same care. An agent that knows when to hand off is worth more than one that always answers.

If you’re evaluating tools

• Does it work with the phone system you have — 3CX, FreePBX, Mitel, Avaya, RingCentral or Zoom Phone — without replacing it?
• Does it capture desk phones and softphones, not just video meetings?
• Do calls and meetings land in one record you can question in plain language?
• Does every answer show the calls and meetings behind it, so you can check?
• Do promises and problems become tasks with an owner?
• If an AI answers your phones, does it hand off instead of guessing?

Consent before you record

Bottom line

Nora’s refund report said Other because the reason never reached a form. It was on 38 phone calls and in one Monday meeting, on a phone system that was never going to analyse either, waiting for someone to ask.

Capture the calls and meetings you already have, on the phones you already use, and the answer is one question away. See Active Insights.