Skip to content

Use case

Collections

Payment reminders that stay respectful: tiered notices by SMS, email, messaging and call, payment plans in the conversation or in self-service, call windows, suppression lists and consent checks through Univerx Outbound and Journeys.

Flow

From first contact to resolution.

The flow in a few steps. Every step runs on the same platform, without switching systems.

  • 01 · Due dateA payment is overdue. The event comes from your billing system and starts a tiered journey.
  • 02 · A friendly noticeFirst a reminder by SMS, email or messaging, with a link to pay or to a payment plan.
  • 03 · Check before callingBefore every call, Outbound checks call windows, suppression lists and stored consents. Anything that does not fit is not dialled.
  • 04 · ConversationA service agent or an AI agent discusses the situation and offers a payment plan. The context is already there.
  • 05 · AgreementThe payment plan is confirmed and written to the billing system. Further reminders follow only according to plan.

What the platform adds

What carries this flow.

The qualities that count day to day – for customers as much as for the teams.

  • Tiered, not relentless

    Journeys define when which channel follows. Anyone who pays receives no further reminder.

  • Consent checked

    Call windows, suppression lists and consents are checked before every contact, following rules you store.

  • Payment plan in self-service

    Via a link, the customer picks a payment plan herself, within the limits you set.

  • Conversations with context

    The agent sees the claim, previous contacts and commitments. The conversation starts factually, not with pressure.

  • Channels that reach people

    SMS, email, messaging and calls from one list. Replies land in the same queue as every contact.

  • Traceable

    Every contact attempt, every check and every agreement is logged.

#Reminding without annoying

An unpaid bill is rarely ill will. Mostly it is forgotten; sometimes the money is short right now. Reacting equally harshly in both cases loses customers who actually want to pay.

Univerx relies on tiered, respectful contact. First a friendly notice, then an offer, then a conversation. Anyone who pays hears nothing more.

A collections journey: notice, reminder, payment plan offer, conversation. Each stage only if the previous one was not enough.

#The journey instead of the dunning list

With journey orchestration, the dunning list becomes a sequence with rules. Every stage has a channel, an interval and a condition.

StageChannelContent
NoticeSMS or emailFriendly reminder with a payment link
ReminderMessaging or emailOffer of a payment plan in self-service
ConversationCall, checked beforehandClarify the situation, agree a payment plan
AgreementConfirmation by messagePlan, dates, contact person

Notifications run without an agent. Calls are planned by Univerx Outbound in the dialler modes that suit your team.

#Checking before every contact

Before a call or a message goes out, lists & consent checks what you have stored: call windows, suppression lists, consents, maximum attempts. If something does not fit, nothing is dialled.

For marketing calls and messages, German competition law (§ 7 UWG) requires prior consent. Payment reminders rest on other bases. Your legal team decides which applies to your contacts; Univerx puts the rules into practice.

#The conversation, when one is needed

When it comes to a conversation, the agent sees the claim, previous contacts and earlier commitments. She starts factually and offers solutions. An AI agent can agree simple payment plans itself, within the approved limits.

In cases of hardship, the AI agent hands over to a person at once. More on this part of Outbound is described under collections.

#A typical start

  1. Workshop: define stages, channels, rules and payment plan limits.
  2. Pilot: one type of claim with notice, reminder and self-service payment plan.
  3. Rollout: calls with prior checks, AI agent for simple agreements.

#What goes with it

The guide Outbound with consent in Germany explains the framework, with sources. For utilities, the page Utilities & telecoms describes the link to instalments and bills.

Building blocks

The capabilities behind it.

These capabilities and add-ons carry the solution. Each one is described on its own – with flow, use and rules.

  • Univerx Outbound

    Collections

    Respectful payment reminders and payment-plan conversations: reminders in the right tone, self-service for simple cases and well-prepared conversations for everyone who needs a solution.

    Learn more
  • Univerx Outbound

    Lists & consent

    Contact lists, call windows, suppression lists and consent checks per channel, with every check documented. The basis for campaigns and notifications reaching only people who may be reached.

    Learn more
  • Univerx Outbound

    Notifications

    Automated reminders and notices with no agent involved: appointment confirmations, delivery status, deadlines, outage information. By SMS, email, messaging or voice message, with a way to reply.

    Learn more
  • Univerx Outbound

    Campaigns

    Voice campaigns with preview, progressive and predictive dialling, plus SMS, email and messaging campaigns from the same contact list. One campaign, several channels, one consent check.

    Learn more
  • Univerx Journeys

    Journey orchestration

    Journey orchestration triggers the next best action in real time when a journey reaches a certain point: a chat offer, a callback, a message, or a hint for the agent who is on the call right now.

    Learn more
  • Univerx AI

    AI Agents

    AI agents understand the request, act in connected systems and hand over to people with context. On the phone as a voicebot, in chat as a text agent, always disclosed as AI.

    Learn more

Industries

Where this flow often starts.

Industries in which this use case is often the first step – each with its own rules and add-ons.

  • High-voltage pylons in the morning haze

    Utilities & telecoms

    High volume, many routine requests: AI agents for meter readings, tariffs and bills, outage communication at peak times, payment reminders with consent checks. Documents for your NIS2 obligations on request.

    • AI agents for routine
    • Outage communication
  • An advisor in conversation with a client

    Banking & financial services

    Service on every channel, advice with a shared view and a signature inside the conversation, onboarding with the online ID card as a goal. Plus documents for your ICT third-party risk management under DORA on request.

    • DORA documents
    • Onboarding with the online ID
  • A lit boutique window in the evening

    Retail & e-commerce

    Order and returns service via messaging, chat and phone, proactive delivery notices, help in the shop at the right moment and accessible customer interfaces as a goal under the European Accessibility Act.

    • Messaging & web messaging
    • Proactive delivery notices

Frequently asked questions

Does German competition law (§ 7 UWG) apply to payment reminders?

§ 7 UWG mainly governs marketing contact. Payment reminders rest on other legal bases. Clarify what applies to your contacts with your legal team; Univerx checks what you store as rules.

Can AI agents agree payment plans?

Within the limits you approve, yes. The agent is disclosed as AI, offers only the stored options and hands over to a person in cases of hardship.

How do we avoid too many contacts?

With journeys that define intervals, channels and maximum attempts, and with suppression lists. Anyone who pays or agrees a plan drops out automatically.

Can Univerx connect to our billing system?

Yes, through connectors or open APIs. Due dates trigger journeys, and agreements go back into the system.

Further reading

  • A man looking at his smartphone in the street in the evening
    Guides2 November 2026 · 11 min read

    Outbound with consent in Germany

    Campaigns, notifications and collections within German competition law and the GDPR: which rules apply to which kind of contact, how to obtain consent that holds, and how to prove it in daily operations. With sources.

  • A train passing a platform at night
    Guides2 November 2026 · 11 min read

    Journey orchestration: a playbook

    From analytics to the next best action: how to pick a customer journey, settle data and triggers, choose the right channel, and run it all with clear governance and honest measurement.

  • A hand signing a document
    Europe & regulation2 November 2026 · 4 min read

    Consent in outbound: what German competition law means for campaigns

    Consent first, contact second. What German law requires and how a campaign keeps to it every day.

  • A tram on a city street at night
    Customer experience strategy1 November 2026 · 4 min read

    Journey first, not channel first: another way to plan service

    Nobody wants to "use the chat". People want to move house, switch tariffs or understand a bill. Plan service along those paths and you see breaks no channel report shows.

See Univerx on your own example.

In a demo we show the platform along your channels and requests, from AI agents to video, workforce scheduling and analytics.

Online, in German or English, with no preparation on your side.