Some of our clients have worked with us for many years, and we still meet most of them every week. That is not a sign that something is wrong. It is how a telephone process stays good after the launch photographs have been taken, and it is the clearest difference between buying a tool and buying a service that someone runs with you.
The common assumption in automation is that the hard work ends at go-live: build it, test it, switch it on and let it run. Our experience since 2012, through IVRs, early speech recognition, studio voices, synthesis and now large language models, says the opposite. The process you launch is the first version. The one that delivers results for years is the hundredth, and someone has to make the ninety-nine changes in between.
We are not a typical technology company that leaves the client with software and tells them to cope alone. – Dawid Wójcicki, Founder & CEO of Vee
Why a working process still needs attention#
A telephone process is not a piece of code that either works or does not. It is a conversation with a changing population, under changing rules, inside a business whose priorities move. Every one of those things drifts.
- The base changes. A collections portfolio this quarter is not the portfolio of last quarter. New customers arrive, others leave, payment behaviour shifts with the economy.
- The calendar changes. Holidays, salary dates, school terms and summer absences move reach and willingness to talk in ways that repeat, but only if someone is watching for them.
- The market changes. In the third quarter of 2026, for example, the National Bank of Poland's lending survey showed Polish banks tightening consumer-credit criteria, which directly changed the economics of sales processes built around confirming interest in a loan. A process designed in a different credit climate needs to be looked at again.
- The rules change. Since 2 August 2026, the transparency obligations of Article 50 of the AI Act have applied. Openings had to be reviewed against them, as did every process built before that date.
- The business changes. A client decides to pass a new bucket, a new lead source or an entirely new process. Each one is a small project in its own right.
None of this is visible from a dashboard of minutes and call counts. Counting minutes and records is not business analytics. Analytics means knowing the base, the buckets and the seasons well enough to change the next call, and that knowledge lives in a conversation between people who understand the client's business and people who understand the process.
From the hot start to a steady rhythm#
The rhythm changes over the life of a process, and it should. Treating year three like week one wastes everyone's time; treating week one like year three is how launches go wrong.
| Phase | What happens | Typical cadence |
|---|---|---|
| Hot start | Both sides watch Vee Analytics in real time: records touched, attempts, outcomes, conversations, business statuses. Our quality team listens to unusual calls. | Daily contact; meetings after the first days to decide on the next base |
| Stabilisation | Corrections from the pilot are applied, larger bases are loaded, the comparator settles. | Several meetings a week, falling as the process steadies |
| Managed production | Results reviewed against agreed KPIs, tests proposed and agreed, exceptions discussed. | Weekly; monthly for very simple processes, with e-mail and phone in between |
| Development | A new bucket, portfolio, lead source, process or market is prepared. | Workshops alongside the regular rhythm |
Cadence is agreed per client and per process; these are typical patterns, not a contractual standard.
The aim after launch is that a weekly meeting is enough. For a very simple process, a monthly meeting may be enough, supported by day-to-day e-mail and phone contact. What we avoid is the opposite extreme, in which the only contact between supplier and client is the invoice.
Two kinds of meeting, and why we keep them apart#
We run two kinds of meeting with clients, and mixing them makes both worse.
Status meetings#
These look back. What happened last week or last month, how a portfolio performed over the year, where the KPI ladder moved and why. Reach first, because without reaching the customer there is nothing else. Then continuation, the inverse of people hanging up after hearing the company name. Then the key information the conversation exists to obtain, and finally the business effect measured in the client's systems. A good status meeting ends with a short list of hypotheses to test, not with a slide deck that nobody reopens.
In collections, a status meeting typically sets our results against the comparator on the same buckets and portfolios, separates promises to pay from payments that actually arrived and asks where the difference came from. Did reach fall because of the time of year or because an outbound number started being screened? Did continuation drop after a change of wording? Did promises hold less well in one segment than in another? The point is not to defend last month's numbers. It is to find the incremental effect, the part of the result the process actually added, and to decide what would add more.
Workshops#
These look forward. Every new base gets one, and so does every new element of a process. A new collections bucket is not the old bucket with a different file name: debtors further into delinquency react differently, the conversation has to reflect their history, and the exception paths may need to change. A new lead source carries a different level of intent. A new country brings different identity verification, different politeness conventions and different call windows. We sit down with the people on the client's side who know that population and design for it before the first call, not after the first complaints.
Two owners on our side, named owners on yours#
Every project at Vee has a tandem of owners. The business owner is responsible for whether the process is profitable for both sides and for the wider partnership: what else could be done, where the relationship should go next. The operations owner is responsible for delivery: stages, schedules, coordination of the team and deadlines. One thinks in quarters and years, the other in days and weeks. A client always knows whom to call about which question.
| Vee | Client |
|---|---|
| Business owner: profitability of the process, scope of the partnership | Process owner and its business goals |
| Operations owner: stages, schedule, team coordination, deadlines | Budget owner: the last and most important approval of changes |
| Dialogue designers, voice studio, telecom and integration engineers | Approval of conversation content and flow; input data and legal basis for contact |
| Quality team: daily listening in every project | Friends-and-family testing and feedback at each new stage |
| Analysts: correlations, hypotheses, A/B tests | Own analysts: allocation strategy, meaning which accounts, when |
| Incident team with technical and business specialisms, working under SLA | Sales or service team receiving transfers |
Roles as defined in Vee's delivery model.
The right-hand column matters as much as the left. A process with no named owner on the client's side drifts as surely as one with no owner on ours. We also respect a boundary that experience has taught us: the allocation strategy, meaning which accounts are assigned, when and to whom, stays with the client's analysts. Our job is to understand the client's reality and run the contact inside it as effectively as possible, not to take over decisions that belong to the business.
Shared documentation, many channels#
Long partnerships produce a great deal of knowledge, and knowledge that lives in one person's inbox is lost the day that person changes jobs. So we give clients access to a shared documentation space where the process, its versions, the agreed rules and the decisions are written down. We set up a mailing group with people from both teams, so that nobody is left out of a thread that turns out to matter. For quick matters there is often a messaging group: a base arriving a little later than planned, a request to look at a particular call. And there is always the telephone.
This sounds mundane, and it is. It is also what allows a process to survive staff turnover on both sides, an audit, a change of budget owner or a move into a new country. In regulated sectors it is more than convenient. When a bank or an insurer asks how a conversation was configured on a given date and who approved that configuration, the answer has to be on paper, not in someone's memory.
What happens between the meetings#
Meetings are where decisions are taken. Most of the work happens between them.
A typical week in a mature process looks unremarkable from the outside, and that is the point. Bases arrive through the agreed data exchange and are validated before the first attempt. Calls go out within the windows set for each market, retries follow the spacing that depends on the previous outcome, transfers reach the client's team during its working hours. Behind that routine, people are reading statuses, listening to recordings and comparing segments, so that by the next meeting there is something specific to propose rather than a general impression.
- Daily listening. Part of quality is measured automatically: diagnosis, benchmarks, status checks. The rest is human. Every day, in every project, our people listen to a sample of recordings, especially suspicious and unusual ones, to judge what technology still hears badly: emotion, whether a sentence was understood, whether speech recognition had a fair chance of mishearing, whether something interrupted the line.
- Analysis. Our analysts look for correlations between contact parameters and results, form hypotheses and, with the client's agreement, test them: wording, tone, voice, hour, the method of identity verification. Optimisation cycles run in days, not weeks.
- Incident response. We monitor most failures that can occur and work under SLAs, basic or extended, which set our times for reaction, repair and communication.
- Data in both directions. The final business result is the hardest information to obtain, because it is not in our systems. We ask clients for it periodically with contract or lead numbers we can match, as monthly statistics or, best of all, automatically after each closed base. We also ask for richer input data, because the more we know at the start, the better the hypotheses we can test.
One property of how we work makes this rhythm unusually productive. Vee employs no call agents; the conversations are executed by our AI. When a meeting agrees a change, there is no retraining of a hundred people across three shifts. Once approved and tested, the change reaches every live conversation at once. A weekly meeting with a call centre produces intentions. A weekly meeting with us produces a different process the following day.
The maintenance phase is often a development phase#
In long partnerships, the line between maintenance and new work is blurred. A process in steady production very often has elements of development running alongside it: a sub-process, a modification, a migration, a new bucket. In collections that may be a new bucket for an existing portfolio, or an entire new portfolio. In lead qualification it may be a new lead source. It may be a retention process, such as contracts coming up for renewal or a cross-sell question after a purchase. And sometimes it is something different altogether: a client with an outbound process that works well asks for a small inbound line next to it.
The initiative comes from both sides. Sometimes the client reaches a point of operational readiness and decides to pass us a new category of base. Sometimes we see the results and ask: are there other situations like this one that you would like handled the same way? Neither would happen without the regular rhythm. Ideas for the next process rarely come up in a quarterly business review; they come up in the fortieth weekly meeting, when both sides know the current process well enough to see what is missing around it.
The same rhythm carries a relationship across borders. Large groups run similar processes in several countries, and when a first process works in one market, the natural next question is whether it can work in another. That step is never a copy. Language, identity verification, call windows and consequence language all change, and the people on the client's side change too. What carries over is the method: the workshop before the first call, the sample before the whole base, the tandem of owners and the weekly review. A partnership that has kept its rhythm at home is far better prepared to keep it abroad.
We are not a software house. We don't build a process, switch it on and say: now it will fly by itself. – Dawid Wójcicki, Founder & CEO of Vee
The gap after deployment, and who closes it#
What the market says#
The industry is beginning to measure what happens after go-live, and the numbers point the same way as our experience. Two caveats first: both studies below are vendor-sponsored or vendor-commissioned, and they cover contact centres broadly rather than telephone automation specifically.
- TELUS Digital's “Enterprise CX AI: 2026 Global Survey – Optimized or just deployed?”, a vendor-sponsored study prepared with Ryan Strategic Advisory among 815 leaders in 12 countries in the first quarter of 2026, reports that only 32% have AI-powered quality assurance and coaching, and describes deployment outpacing optimisation.
- CallMiner's vendor-commissioned “CX Landscape Report 2026”, based on 700 CX leaders in six markets, reports that 99% use automation, but only 23% say they are both highly automated and consistently optimised using CX insights.
Read together, they describe an industry that has learned to switch automation on but not yet to keep improving it. That is not a technology problem. It is an operating-model problem, and an operating model is mostly a calendar: who meets whom, how often, with what data and with what authority to change things.
Is the rhythm an extra?#
A fair question from any CFO is whether all this attention is a hidden cost. Listening, analysis and optimisation are part of running the service, not a stream of separate orders the client has to remember to place. How the service is scoped is set out in the agreement; what matters here is that the weekly meeting is where improvement is decided, not where it is sold.
Where clients choose a performance layer in the commercial model, such as a KPI incentive that moves the monthly invoice up or down as agreed indicators change, the incentive becomes explicit. We invest work in improvement because improvement shows up in the following invoices. That is one reason we prefer such models to billing by the minute: a minute rewards long calls, and the weekly meeting is often about making calls shorter and more effective.
What to ask a supplier about life after launch#
If you are choosing a partner for automated customer contact, the launch plan will look good in every proposal. Ask about year two instead.
- Who are the named owners on your side after launch, for the business and for operations, and will they still be there in a year?
- How often will we meet in steady production, and what is on the agenda?
- What happens when we pass you a new base, bucket or lead source? Is there a workshop, and who attends?
- Who listens to recordings, how often, and how do their findings change the process?
- Where is the process documented, and can we see every version and every approval?
- How fast does an agreed change reach live conversations?
- Which outcome and input data do you need from us, and how will it flow?
- How is the ongoing work paid for, and what in your commercial model rewards you for improving our results?
The answers will tell you whether you are buying software with a support contract or a process someone will run with you for years. We built Vee to be the second: a service that stays at the client's side long after launch, still meeting every week and still finding the next thing worth changing.
Follow The First Second
Occasional issues on the mechanics and economics of AI-powered customer contact. No noise, no vendor news.
Follow via RSS