Customer hotline and support in SaaS

SaaS providers who sell to consumers not only face a support issue when it comes to hotlines, but also a clearly defined legal requirement under consumer law. A “chargeable customer hotline” is not prohibited per se in the B2C context, but it becomes legally problematic the moment it is used as a communication channel “for an existing contract”. The benchmark is not the internal classification as “support”, but the objective contractual reference of the request: termination, billing, faults, access to the digital service, complaints or other declarations regarding the execution of the contract.

National model: Section 312a (5) BGB as a market conduct rule and risk of warnings

The central point of reference in German law is Section 312a (5) BGB. The standard stipulates that consumers may not pay more than the mere cost of using the telecommunications service when using a telephone line provided by the entrepreneur for questions or explanations regarding a concluded contract. This covers models that are above the “normal” telephone charge – i.e. typically value-added services, service charges, minute-based premium rates or other structures that make the call more expensive than a normal call.

Two things are relevant for the practice of SaaS providers. Firstly, the standard is not linked to whether the telephone is offered “voluntarily”. As soon as such a channel exists and can be used for contract-related matters, the price limit applies. Secondly, infringements are not only risky under civil law in the customer relationship (invalidity of the fee agreement, claims for repayment), but also regularly under competition law, because Section 312a (5) BGB acts as a market conduct rule within the meaning of Section 3a UWG. This results in a classic warning profile, which quickly becomes a reality, particularly in the case of visible website information on the “service hotline”.

In the SaaS context, the contractual reference is also particularly broad: in the case of digital services, technical usability is often at the heart of the performance obligations. “Account not working”, “Payment stuck”, “Feature blocked”, “Downgrade not working”, “Cancellation to be confirmed” are not just cult topics, but regularly part of the contract performance. This is precisely why B2C SaaS models should not attempt to shift the cost burden to consumers via telephone.

EU legal background

§ Section 312a (5) BGB was not created in isolation, but implements the requirements of the Consumer Rights Directive 2011/83/EU. The Directive contains the well-known “basic rate” requirement: If a trader operates a telephone line for contacts in connection with a concluded contract, the consumer may not pay more than the basic rate. The ECJ has confirmed this guiding principle in its case law and clarified the regulatory logic: The aim is not to discourage consumers from exercising contractual rights or clarifying issues relating to the performance of a contract by increasing telephone costs.

For SaaS providers, this has two legal consequences that are often underestimated when drafting contracts. Firstly, the interpretation is in line with EU law, i.e. tends to protect consumers. “Basic tariff” is not understood as a historical term, but in the light of real market conditions. In a world of flat rates and included minutes, any additional cost architecture is particularly quickly assessed as “above basic rate”. Secondly, the EU requirement is function-related. A number that is actually also used for communication with existing customers cannot be “saved” by labeling it as “premium” or formally as “general information”.

This makes the dividing line between pre- and post-contractual matters legally central. Pre-contractual communication (sales/initiation) is not subject to the same “basic rate” restriction. However, as soon as a number channel is actually or typically used for contractual matters, the requirements apply. In practice, the evidence and attack surface is less legally abstract than simply factual: website wording, FAQ texts, contact pages, CRM routing and support processes determine whether a number is provided “for contractual matters”.

3. room for maneuver

It does not follow from the above that a telephone must be offered. Information obligations under consumer law require that existing means of communication are stated transparently; however, they do not automatically establish a general obligation to operate a hotline at all. In practice, B2C SaaS can be legally compliant with email/ticket support, contact forms and in-app communication if the channels are functional and the exercise of rights is not made more difficult. The choice of channel is less critical than the “hurdle constructions”: termination, revocation, complaints or billing issues must not end up in a structure that actually discourages or delays.

“Paid support” remains possible – but only as a genuine additional service. Paid services that go beyond the statutory and contractual minimum are typically permitted: guaranteed response times (SLA), prioritization, a dedicated contact person, onboarding, migration, training or configuration advice. The model becomes inadmissible where the chargeable service replaces access to basic contractual issues. A “billing call only for a fee” or “termination only by telephone via premium number” is legally contestable because it makes the exercise of contractual rights more expensive. The legal standard of review is not whether there is any alternative channel, but whether the consumer can realistically clarify their contractual concerns without incurring additional costs.

A legally robust architecture has been established for concrete implementation in SaaS operations: Ticket-first as standard, supplemented by callback or video session as an escalation stage. This model creates documentation, account identification and prioritization without shifting the cost burden to consumers. Telephone remains possible, but it is used as a process module, not as a gateway subject to a charge.

Conclusion

Ultimately, the legal situation in B2C SaaS is relatively clear: fee-based hotlines are problematic the moment they are used for contract-related communication. This is not only a question of the customer relationship, but also typically a competition law issue with the potential for warning letters due to Section 3a UWG. Under EU law, the direction of travel is clear: contract communication must not be devalued by increased telephone costs. Nevertheless, there is room for maneuver – above all through clean channel architecture, clear separation of pre-sales and existing customer communication as well as premium services that offer genuine additional quality without pricing access to basic rights.

If desired, a version ready for publication for itmedialaw.com can be built directly from this (with meta description, subheadings, clean citation of standards and a short section on the typical warning constellation for contact pages/cancellation policy) – still as continuous text and legally focused.

Author: Marian Härtel

Marian Härtel ist Rechtsanwalt und Fachanwalt für IT-Recht mit einer über 25-jährigen Erfahrung als Unternehmer und Berater in den Bereichen Games, E-Sport, Blockchain, SaaS und Künstliche Intelligenz. Seine Beratungsschwerpunkte umfassen neben dem IT-Recht insbesondere das Urheberrecht, Medienrecht sowie Wettbewerbsrecht. Er betreut schwerpunktmäßig Start-ups, Agenturen und Influencer, die er in strategischen Fragen, komplexen Vertragsangelegenheiten sowie bei Investitionsprojekten begleitet. Dabei zeichnet sich seine Beratung durch einen interdisziplinären Ansatz aus, der juristische Expertise und langjährige unternehmerische Erfahrung miteinander verbindet. Ziel seiner Tätigkeit ist stets, Mandanten praxisorientierte Lösungen anzubieten und rechtlich fundierte Unterstützung bei der Umsetzung innovativer Geschäftsmodelle zu gewährleisten.