A collections conversation that works in one country cannot simply be translated into another. The structure travels well; the identity check, the register of politeness, the language of consequences and the rules around the call do not, and those are the parts the customer actually hears.

We run early collections for banks in Poland, Austria and Germany, in two languages and under three national frameworks. If you asked us whether the processes differ, the honest answer would be: less than you might expect in shape, more than you might expect in detail. This piece is about the detail, and about who owns it when the content belongs to a bank.

The skeleton that travels#

In every market the call follows the same broad path. The bank’s analysts decide which accounts in early delinquency are assigned to us, by portfolio, by bucket (a band of days past due) and by debtor category. We then run the contact and report back, case by case.

  1. A schedule of attempts suited to the type of arrears.
  2. Identity verification, before anything about the debt is said.
  3. Establishing the payment status: paid already, will pay, cannot pay, disputes.
  4. Negotiating a date within the acceptable horizon for a promise to pay (PTP).
  5. Information about the amount and how to pay.
  6. A business status the bank’s systems can act on the next morning.

The segmentation logic travels too. The number of days past due shapes the base conversation: urgency, consequence language and negotiation logic. Behaviour history adjusts it further, so a customer who previously promised and did not pay hears a different conversation, in which the broken promise is named. Separate dialogue paths for different customer groups run in parallel inside one deployment. None of that needs reinventing per country.

Verification is set by law, not by taste#

The biggest real difference between markets is authentication. Banking law, and the responsibility it places on a bank’s management, differ between Poland, Austria and Germany, and the identity check before a collections conversation follows from them.

So verification is configured per deployment rather than hard-coded: how many factors, which data (for example name, date of birth, postal code or an instalment amount), how partial or badly formatted answers are handled, and what happens when verification fails. It also differs by product and between consumer and business accounts. In one market a failed check may lead to a transfer; in another, to a hard stop and a retry later. What does not change anywhere is the rule underneath: debt details are never disclosed before identity is verified, and that is enforced by the platform, not by a line in a script.

The sentence that asks for verification is also one of the most sensitive in the call. It has to sound like a bank protecting the customer, not like a stranger collecting personal data, and what sounds reassuring depends on what customers in that market are used to hearing from their own bank.

Politeness is grammar as well as tone#

Polish and German both have formal registers built into the grammar: “Pan” and “Pani” in Polish, “Sie” in German. That sounds like a small matter of translation until you write a negotiation. The formal register changes sentence length, the way a request is softened, and how directly a date can be proposed without sounding like an order.

Austria and Germany share a language but not a phone manner. A greeting, a closing formula or a turn of phrase that sounds natural in Vienna can sound slightly foreign in a German city, and the reverse. In a sales call that costs a little warmth. In a collections call, where the customer is already looking for a reason to end the conversation, sounding like an outsider costs continuity.

This is also why we treat voice as part of localisation. We choose the speech engine that performs best for each language and record studio voices where they win. A voice that is technically correct but carries the wrong accent for the market is a sentence the customer has already judged before hearing its content.

Consequence language is the hardest part to move#

Every collections conversation at some point tells the customer what happens if they do not pay. That sentence has to be true, proportionate and legally safe in the market where it is said, and it changes as days past due increase.

What a bank may say about next steps, how firmly, and at what stage of delinquency, depends on local law, local regulators’ expectations and the bank’s own policy in that country. A sentence that is an accurate, measured statement of next steps in one market can be read as undue pressure in another, or as so vague that it means nothing. This is not something a supplier should improvise, and it is not something that survives translation. It is written for the market, approved by the bank’s people in that market, and versioned.

What travels between markets and what is set per market
ElementTravelsSet per market
Conversation path and segmentation logicYesThresholds and horizons
Identity verificationThe rule: nothing before verificationFactors, data, failure handling
Register and phrasingPrinciples of clarity and brevityFormal address, idiom, greeting, closing
Consequence languageProportionality to days past dueExact wording, approved locally
Calling windows, attempt limits, retry intervalsSystem enforcementThe values themselves
Recording consent and exception pathsThe list of exceptionsTransfer, hard stop or referral per case

Based on Vee’s early-collections operations in Poland, Austria and Germany.

The rules around the call#

Some of the most important differences are never heard by the customer. Calling windows, the maximum number of attempts, the intervals between retries and the handling of recording consent are configured per market and enforced at system level, not left to campaign settings that someone could change on a busy day. We do not run shared defaults across the three countries.

Exception paths follow the same pattern. A request for a human, a failed verification, a withdrawal of recording consent, a death or legal dispute, a data erasure request or a declared financial hardship each map to a defined outcome: a live transfer, a hard stop or a referral. Which outcome applies is configured per deployment and per market, because the bank’s obligations and its local teams differ.

Portfolios also differ. Cards, cash loans, instalment loans, car loans and overdrafts appear in different mixes in each country, and the same contract can come back to us several times within a month under the bank’s allocation strategy. A conversation that is right for a returning customer on a car loan is not the one for a first-time late payer on a card.

A result in one market is a hypothesis in the next#

Running the same kind of process in three countries gives us something a single-market operator does not have: a constant stream of comparisons. A change to the opening, the negotiation or the messaging around the call that helps in one market is an obvious candidate for the others. It is a candidate, not a rule.

We treat every cross-market idea as a hypothesis to be tested on the new market’s own base, with the bank’s agreement, against a comparator on the same buckets and portfolios. Sometimes the finding carries over almost unchanged. Sometimes it reverses, because the customers, the products or the bank’s own letters and reminders around the call are different. The discipline is to resist the shortcut of copying what worked, however convincing the first market’s numbers look.

Listening is part of that discipline. Our quality team listens to selected calls every day in every project, and in a new market the unusual calls are the most instructive: the customer who asks the same question twice, the pause after the consequence sentence, the hang-up during verification. Those moments tell you which words have not yet arrived in the new country.

When the content belongs to the bank#

In collections the words are not ours. We design, propose and test them, but the bank owns the content, approves it, and answers for it to its regulator. In a multi-market group that means more than one owner: the group may set principles, while compliance and collections teams in each country approve what is said in their market.

Our standard path into a new market reflects that. We configure market compliance first, then the verification flow, then the scripts, then reporting and data exchange, infrastructure and file integration. Scripts come third on purpose: they are written inside the frame the market sets, not translated and then corrected. In regulated set-ups every content change is versioned and approved, so the bank can show which wording any given customer heard.

Our first foreign project started in 2023. Since then foreign processes have become a significant part of our business: in October 2026 they accounted for 25.27% of our contact-process revenue (excluding implementation fees, additional services and one-offs). Each new market has confirmed the same lesson: the conversation travels, the words do not.

What to ask a supplier who says “we can do your other markets too”#

  • Is identity verification configured per market, product and customer type, and is the no-disclosure-before-verification rule enforced by the platform?
  • Who writes the consequence language for each market, and who at our local entity approves it?
  • Are calling windows, attempt limits and retry intervals set per market and enforced by the system?
  • How are exception paths, such as hardship, disputes and erasure requests, configured differently per country?
  • Is the script written in the local language or translated from a master version?
  • Which voice and speech engine do you use for each language, and why?

A supplier who answers these with “it is the same platform everywhere” has told you something true and something incomplete. The platform should be the same. The conversation your customer hears in Vienna should not be the one they hear in Warsaw.

Follow The First Second

Occasional issues on the mechanics and economics of AI-powered customer contact. No noise, no vendor news.

Follow via RSS