BizLedger’s customers manage their finances in its dashboard and expect help the moment they need it. Cypher V now answers their calls instantly, and Cypher N keeps the team informed.
Challenges
Financial questions don’t keep office hours
BizLedger is a financial management dashboard for growing businesses, and its customers call about invoices, reports and account settings at exactly the moments those things go wrong — often at month-end, often late in the evening, and often against a deadline they can’t move.
A small support team couldn’t staff a phone line around the clock, and customers working against a closing deadline didn’t want to leave a voicemail and wait until morning for a callback, especially when the question blocking them was often something simple to answer.
Month-end in particular brought a spike in calls that the team’s normal staffing simply couldn’t absorb, which meant the busiest, most deadline-sensitive days of the month were also the days customers were most likely to be kept waiting.
Every call still needed the full picture
Many calls weren’t simple yes-or-no questions — customers wanted help understanding a specific report or reconciling a specific invoice, which meant whoever answered needed account context, not just a general FAQ answer.
And some calls ended with a customer wanting to settle an outstanding balance right then, which meant a purely informational support line still left a step unfinished — the customer had to go somewhere else to actually pay, and some simply didn’t get around to it afterwards.
BizLedger also serves customers across different time zones, which meant the gap between when a question came in and when someone could answer it varied a lot depending on where a customer happened to be calling from.
For a product that handles something as sensitive as a business’s finances, every unanswered call carried a bit more weight than a typical support question would, since customers calling about their books tend to be more anxious than a customer calling about a minor software bug.
Solution
Setting up Cypher V from the dashboard
BizLedger trained its Cypher V agent on its help articles and product guides directly from the Cypher LM dashboard, then connected its support phone number and set call rules for which questions the agent should handle on its own versus hand to a person.
The team tested the agent against real support questions pulled from past tickets before going live, checking that explanations of reports and account settings matched what the support team itself would say.
Call rules were tuned specifically for sensitive situations — anything touching a dispute or an unusual account change was routed to a person automatically, so the agent only ever answered the kinds of questions it had clear documentation to support.
The team also built in a clear escalation path for anything involving an irregularity a customer flagged in their own records, since that is exactly the kind of call where a customer needs to feel they are talking to a person who can actually investigate, not just explain a feature.
An agent trained on the product, not a script
The agent walks customers through common tasks, explains reports in plain language, and recognises when a question is specific enough — a disputed line item, an account-level issue — that it needs a person rather than a general answer.
Because it answers from BizLedger’s own documentation, customers get the same accurate explanation whether they call at ten in the morning or ten at night, instead of a different answer depending on which support rep happens to pick up.
Customers calling from a different time zone no longer notice a difference in how quickly or how well their question gets answered, which had previously been one of the more inconsistent parts of the support experience.
Handovers with full context
When a call needs the team, Cypher N passes along a summary with the customer’s question, relevant account details and what has already been tried on the call, so the follow-up starts exactly where the call left off instead of from scratch.
Support staff reviewing a handover can see in seconds what the customer actually needs, which cuts out the first few minutes of most follow-up calls that used to go into re-explaining the problem.
That has mattered most on the calls customers care about most — a reconciliation issue or a report that doesn’t look right — where getting straight to the problem instead of re-explaining it from scratch makes the difference between a quick fix and a frustrated customer.
Payments handled on the call
With Cypher P, customers can settle an outstanding invoice during the conversation itself, without being redirected to another page or waiting for a payment link to arrive by email after the call has already ended.
That single change closed a gap the team had lived with for a while: a customer who called specifically to pay no longer has a reason to hang up and forget, since the payment happens inside the same call.
Results
Every call answered, every time
BizLedger’s customers now reach help the moment they call, including at month-end and after hours, instead of leaving a message and waiting for the next business day.
The support team starts every follow-up with full context from Cypher N instead of a voicemail and a guess at what the customer needed, which has made handovers noticeably faster to work through.
Fewer dropped threads, fewer unpaid invoices
Customers who called specifically to pay an outstanding balance can now do it without a second step, which has removed one of the more common reasons a simple support call used to turn into an unresolved open item.
The support team has also found that month-end, once its busiest and most strained period, is now the period where Cypher V absorbs the most repetitive volume, leaving the team free for the calls that genuinely need a person.
A support line that scales with the product
As BizLedger adds new features to its dashboard, the team updates the Cypher V knowledge base alongside the product release, so the agent is answering questions about a new report or setting from the day it ships rather than weeks later.
That has turned what used to be a pure support cost — staffing a phone line that got busiest exactly when the team could least afford it — into something closer to a product capability that improves every time the underlying documentation does.
Looking ahead, the team expects the same setup to keep paying off as the customer base grows, since answering more calls doesn’t require hiring more support staff in step with it the way a purely human phone line would.
BizLedger’s support lead has also noticed a change in how customers talk about calling in: a task that used to come with a bit of dread, wondering how long the wait might be, now tends to be something customers mention doing without any particular concern, which is its own kind of sign that the line is working the way it should.
The team has also begun tracking which questions Cypher V answers most often each month, using that pattern to prioritise which parts of the product documentation and in-app guidance most need improving next.
Customers who previously avoided calling altogether, choosing instead to sit with a confusing report until someone happened to help them in person, now call in more readily, which the team sees as a sign that the line itself has become a more trusted part of using the product rather than a last resort.
The product team now reviews the most common Cypher V questions each quarter alongside its own roadmap discussions, treating the call line as an ongoing, unfiltered source of what customers actually find confusing rather than relying solely on support tickets or survey feedback.
BizLedger’s support lead says the biggest shift has been in how the team spends its attention: less of it goes toward simply being available for whoever calls next, and more of it goes toward the handful of calls each week where a customer genuinely needs a person to dig into something unusual.
Looking back at the rollout, the team’s main piece of advice to other finance-adjacent businesses considering the same setup is to be explicit, from the very first call rule, about which situations always go to a person — getting that boundary right early is what made customers trust the agent with everything else.
A year into using Cypher LM, BizLedger describes the support line less as an add-on and more as part of the product experience itself — something customers notice and rely on in the same way they rely on the dashboard being accurate, rather than a separate channel they only think about when something breaks. It is now a reference point the team brings up when onboarding new hires into support.
Ready to answer your customers around the clock? Start your 7-day free trial of Cypher LM today. Start your free trial.
