Skip to content

Guides

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 man looking at his smartphone in the street in the evening

A call, a text, an email: to the person receiving it, outbound communication looks much the same. Legally, they are worlds apart. A plan upgrade offer, an appointment reminder and a payment reminder follow different rules, even when they run on the same platform.

This guide sorts outbound into three kinds, explains the core provisions and shows what you need to be able to prove in daily operations. It is not legal advice. It helps you ask the right questions before the first campaign goes out.

#Three kinds of outbound, three guiding questions

The most important decision comes before any technology: what kind of contact is this? The answer determines whether consent is needed, which data you may use and what you have to document.

KindExampleGuiding questionGoverning rules
Promotional campaignPlan offer, renewal, add-on serviceIs there valid consent for this channel?Section 7 UWG, Art. 6 and 7 GDPR
Service notificationAppointment reminder, delivery status, deadline noticeIs the message purely informative?Art. 6 GDPR
CollectionsPayment reminder, payment-plan callIs the contact proportionate and correctly addressed?Art. 6 GDPR; for debt collection agencies, the Legal Services Act (RDG)

The boundaries are not always sharp. An appointment reminder that mentions a new offer is no longer just service. Treat mixed messages as advertising, or separate the content.

#What Section 7 UWG requires

Section 7 UWG prohibits unreasonable nuisance. Subsection 2 lists cases in which nuisance is always assumed. Three of them are central to outbound work.

  • Phone advertising: to consumers only with their prior express consent; to other market participants at least with presumed consent.
  • Automated calls, fax and electronic mail: advertising requires prior express consent. Email and text messages are covered; treat messaging-app messages the same way as a precaution.
  • Sender and opt-out: the sender's identity must not be concealed, and there must be a valid address to which an opt-out can be sent.

For email, subsection 3 contains a narrow exception for existing customers. It applies only when all four conditions are met:

  1. The email address was obtained in connection with selling goods or services to this person.
  2. The advertising concerns your own similar goods or services.
  3. The person has not objected to this use.
  4. When the address is collected and every time it is used, the person is clearly told they can object at any time.

There is no such exception for phone or text messages. Advertising by phone requires consent, even with long-standing customers.

#Document and retain: Section 7a UWG

Since 2021, Section 7a UWG requires that consent to phone advertising to consumers is documented in an appropriate form at the time it is given. The record must be kept for five years from the date of consent and from each use.

On request, the record must be presented to the competent authority without delay. Under Section 20 UWG, that authority is the Federal Network Agency (Bundesnetzagentur).

The same provision sets fines of up to 300,000 euros for phone advertising without consent and up to 50,000 euros for missing or incomplete documentation.

#What the GDPR adds

Competition law governs whether you may approach someone for advertising. The GDPR governs whether you may process the data needed to do so. Both tests must be passed; neither replaces the other.

If advertising rests on consent, the conditions of Art. 7 GDPR apply. You must be able to prove the consent. Withdrawing it must be as easy as giving it. And consent must be freely given, specific and informed.

Under Art. 21 GDPR, people can object to direct marketing at any time. After that, their data may no longer be processed for this purpose. This also covers profiling, to the extent it is related to direct marketing.

Two further duties are easily overlooked. When collecting contact details, Art. 13 GDPR requires you to explain what the data will be used for and how long it will be kept. And retention periods must fit with keeping your records of consent.

An example: once a person withdraws consent, you may no longer advertise to them.

You may, however, still need proof that and when they consented in the past. Your deletion policy should state which data is blocked, which is deleted and which is kept as evidence.

Most problems do not arise during the call but months earlier, when consent was collected. A single checkbox that covers everything is quick to build and rarely holds up later.

  • Separate by channel: phone, email, text and messaging each on their own, so that people can choose.
  • Specific in purpose: what will the contact be about, and who will make it? Vague formulas like "partner offers" are risky.
  • Actively given: no pre-ticked boxes, and no tying consent to a contract when it is not needed for it.
  • Confirmed: for email, double opt-in has proven itself as evidence.
  • Versioned: every change to the consent text gets a new version.

Be careful with addresses or consents obtained from third parties. Whether they cover your contact depends on the exact wording and evidence. Check that before you buy, not after the first complaint.

#Notifications: service stays service

Appointment reminders, delivery status, deadline notices and outage alerts are not advertising as long as they purely inform. Under data protection law they usually rest on the contract or on legitimate interest, and they often relieve the contact centre because follow-up questions disappear.

The line is drawn by content. As soon as a notification contains an offer, a voucher or a recommendation, it becomes promotional. Satisfaction surveys are a borderline case too; have their classification reviewed by your legal team.

From web to app to a callback and a confirmation by message: notifications as part of a journey. Example.

Good notifications share a few traits:

  • They name the sender clearly and point to a way to ask questions.
  • They contain only the data the notice needs, especially in text messages.
  • They arrive through the channel the person gave for this purpose.
  • They can be unsubscribed from, even where the law does not strictly require it.

With notifications in Univerx Outbound, reminders and notices run automatically, with no agent involved. The articles Informing proactively and Appointments and reminders in healthcare show what this looks like in citizen services and in healthcare.

#Collections: respectful and provable

A payment reminder to your own customer is generally not advertising. It does need a legal basis under the GDPR, usually the contract or legitimate interest, and it calls for particular care in tone and in addressing the right person.

Two points are critical in practice. First, before discussing outstanding amounts, you must be sure you are speaking to the right person. Mentioning a debt to a relative or colleague is a data breach.

Second, pressure is no substitute for a solution. Payment plans, clear amounts and concrete next steps help both sides. Someone in financial difficulty needs a way out, not the fifth call in a week.

If you instruct an external collection agency, additional rules apply. Debt collection is a legal service that requires registration in Germany, and towards private individuals there are specific disclosure and information duties under Section 13a RDG.

Collections in Univerx Outbound is designed for respectful payment reminders and payment-plan conversations. The use case is described on the Collections page.

#Borderline cases from practice

Some questions come up in almost every project. The cases below show how to classify them. They do not replace a case-by-case review, but they help you prepare the conversation with your legal team.

#The requested callback

If a customer explicitly asks to be called back about her request, the call is not unwanted advertising. It should, however, stay with that request. Placing an offer in the callback moves it into promotional territory.

#Former customers

Reactivating someone after their contract has ended is advertising. Whether an earlier consent still holds depends on its wording and its age. A consent left unused for years is weak evidence.

#The survey after the conversation

A request for feedback straight after a contact looks harmless. Because it also serves customer retention, it may count as advertising. Obtain consent for it, or have the specific format reviewed.

#Business customers

Towards businesses, presumed consent is enough for phone advertising. That requires a concrete interest in the offer that is apparent from the circumstances. A business directory listing alone does not meet that bar. For email, express consent still applies, apart from the existing-customer exception.

#The abandoned application

A reminder about an application that was started but not finished can be service if it helps complete it. It becomes promotional when it brings additional products into play. More in the guide Journey orchestration.

#In call operations: windows, blocks, diallers

Even permitted contact can be done badly. In operations, a handful of settings decide whether campaigns feel helpful or intrusive.

SettingWhat it is forRecommendation
Call windowsNo calls at unsuitable timesFixed times per campaign, public holidays included
Suppression listsEnforce objections and withdrawalsCentral, cross-channel, checked before every send
Attempt limitsNo endless loop when people cannot be reachedA maximum per contact and period
Dialler modeControl the dialling paceSet conservatively so nobody is left in silence
Caller numberThe sender can be recognisedAlways show a number that can be called back

The dialler deserves special attention. If it dials faster than agents become free, people pick up and hear nobody. That annoys them and costs trust. A cautious setting is almost always the better one.

#Recording and AI in outbound

Recording calls requires consent. Recording privately spoken words without authorisation is a criminal offence under Section 201 of the German Criminal Code. Ask at the start, store the answer with the call, and do not record if the answer is no.

If you use voicebots or AI agents in outbound calls, people must be told that they are talking to an AI. This transparency duty follows from the EU AI Act, and the way to a person must stay open at all times.

The EU AI Act page in the Trust Center explains how Univerx approaches it.

#How Univerx Outbound supports you

Univerx Outbound brings together campaigns, notifications, lists and consent and collections. Voice, text, email and messaging campaigns run from one list, with call windows, suppression rules and consent checks, designed for Section 7 UWG.

"Designed for" means the platform provides the functions you need to apply the rules and prove that you did. Whether a specific campaign is permitted depends on your consent records, not on the software.

Employee with a headset at her workstation
Outbound is teamwork: legal, data protection and the contact centre set the rules together.

#Who is responsible for what

Outbound incidents often happen at hand-offs: sales plans, the service provider dials, data protection hears about it last. Clear responsibilities prevent that without slowing things down.

  • Business owner: defines purpose, audience and content of the campaign and assigns it to one of the three kinds.
  • Data protection: reviews legal basis, consent texts and retention periods; for new data sources, before launch.
  • Legal: assesses borderline cases and any copy with promotional content.
  • Contact-centre lead: sets call windows, attempt limits and dialler mode, and plans capacity.
  • Operations: maintains lists and blocks, and logs every use of a consent.

If you work with external service providers, these rules belong in the data processing agreement. Ask how blocks are reconciled between your systems and theirs, and who keeps the record under Section 7a UWG.

A simple campaign sign-off brings all of this together, and it need not be a long form.

One page with kind, purpose, channels, consent source, suppression check and the people responsible is enough. What matters is that it exists before the first send and is filed with the results afterwards.

#Checklist before your next campaign

Settle before launch

Is the campaign advertising, service or collections? Mixed content has been separated.
Is there valid consent for each channel, with version and date?
Is consent to phone advertising documented and retained under Section 7a UWG?
For email, does the existing-customer exception apply, and are all four conditions met?
Are suppression lists checked centrally and across channels before every send?
Are call windows, attempt limits and dialler mode set?
Is identity verified before conversations about outstanding amounts?
Is consent to recording handled, and do AI agents disclose themselves?
Can consent be withdrawn easily in every channel?

#Next steps

Outbound with consent is less a question of technology than of order: who agreed to what, and how is that checked on every send? Once that order is in place, campaigns become predictable.

The article Consent in outbound offers a compact introduction, and the glossary explains the term under Consent (German competition law). If you would like to walk through your list and consent logic together, get in touch.

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.