Yes, GDPR applies to telemarketing whenever the call reaches a named person, even on a business line. GDPR only governs the data, though. A second law decides whether you may place the call at all. In the UK that law is PECR. In EU countries it is national law, such as section 7 of Germany's unfair competition act (UWG).
The data check asks whether you may hold and use this person's details. The call check asks whether this number may receive a marketing call.
On a UK list, the call check means screening every number against two registers and your own suppression list. The Corporate Telephone Preference Service (CTPS) protects companies. The Telephone Preference Service (TPS) protects individuals and sole traders. Show caller ID on every call, and stop the moment someone objects.
My position first: we run outreach in writing, on email and LinkedIn. We do not cold call or staff dialing floors. Phone is an optional add-on, and only for warm contacts: people who replied, showed interest or opted in. I am an operator, not a lawyer. Every legal point below comes from a published legal or regulator source, linked in place. This is not legal advice.
Does GDPR apply to phone calls to businesses?
GDPR protects people, and companies sit outside it. Recital 14 of the GDPR says the Regulation does not cover the processing of personal data that concerns legal persons, including the name, form and contact details of the legal person. Data about a named individual at a company is still personal data.
What matters is who the details describe. Contact details held for the company itself, under the company name, are data about a legal person. The direct line of a named procurement manager describes a natural person, so GDPR applies. UK law takes the same view: the ICO's B2B marketing guidance says UK GDPR applies once you hold a business contact's name and number.
The phone rules sit on top of that. The ICO's guide to PECR says the rules do apply to B2B marketing, but marketing to companies is treated less strictly. Sole traders and some partnerships count as individuals and get the stronger protection.
| Layer | What it decides | UK | EU |
|---|---|---|---|
| Data layer | Whether you may hold and use a named person's details, and on what lawful basis | UK GDPR | GDPR |
| Call layer | Whether this number may receive a marketing call at all | PECR, regulation 21 | National law, for example section 7 UWG in Germany |
A TPS number stays off limits even with a perfect legitimate interest record.
Who can you legally call in the UK? A decision table
Regulation 21 of PECR is the rule for live marketing calls. The Data (Use and Access) Act has prompted a review. The ICO is updating its B2B guidance. Check the page before each campaign. The ICO's B2B guidance applies it to business numbers like this:
| Who you are calling | May you make a live marketing call? | What must be true | Source |
|---|---|---|---|
| Limited company or LLP, number on CTPS | No | Only if that business has told you it consents to your calls | ICO B2B guidance |
| Sole trader or some partnerships, number on TPS | No | Same rule; PECR treats them as individuals | ICO B2B guidance, ICO guide to PECR |
| Business number on neither register | Yes | The line has never told you to stop, you show caller ID, and you have a UK GDPR lawful basis if a named person sits behind it | PECR reg 21 |
| Any line that told you to stop | No | Applies whatever the register status | PECR reg 21(1)(a) |
| Number on a register for less than 28 days | The register bar does not apply yet | Your next screening run must catch it | PECR reg 21(3) |
| Registered number whose subscriber told you they do not object to your calls | Yes, until they withdraw | Only the named caller may call, and the subscriber can withdraw at any time | PECR reg 21(4) and (5) |
| Automated or recorded call to any business | Only with consent | Consent from that business, whatever the subscriber type | ICO B2B guidance |
The 28-day row sets your re-screening rhythm: a list screened weeks ago can now hold numbers the registers protect.
Decision rule: if you cannot tell whether a number belongs to a limited company or a sole trader, treat it as TPS-protected. Do not call it until it passes both checks. The register checks follow the UK rules on cold calling businesses.
What must you do on every B2B marketing call?
- Show your number. Under regulation 21(A1), every direct marketing call, solicited or not, must show caller ID or a line on which you can be contacted.
- Say who you are and how to reach you. In its notice on the Energy Prices Direct fine, the ICO sets out what callers must do: say who they are and give contact details or another way to get in touch.
- Take a stop on the spot. When someone says "don't call again", log it against the line that day. Suppress it everywhere, so it never returns in a later campaign.
- Own the calls you outsource. The ICO's guide to PECR says that if you pay someone else to call, you are still responsible, because you are "instigating" the calls. Put the screening duties in a written contract, as the ICO advises.
If you are weighing an outside provider, compare what telemarketing companies actually do before you hire one.
An example opening that covers duty 2 (invented for illustration, not a client call):
Good morning, this is Tom Hale from Northline Software in Leeds. We build scheduling software for logistics firms. You can call me back on the number on your screen. Do you have two minutes now, or would you rather I did not call again?
Can you rely on legitimate interest for B2B call lists?
For the data layer, usually yes, with one hard limit. The ICO's legitimate interests guidance says legitimate interests can cover direct marketing only where PECR does not require consent. No legitimate interests assessment (LIA) can make a call to a CTPS or TPS number lawful without consent.
For numbers PECR lets you call, run the ICO's three-part test on the list itself:
- Purpose. You want to sell to businesses your product fits. The ICO lists direct marketing among the purposes UK GDPR mentions.
- Necessity. Do you need this particular person's number? Keep the people whose job matches what you sell. Drop generic titles such as Assistant, Manager or Associate, and anyone else who could not buy from you. Look at who actually signed your past deals, and keep those titles.
- Balancing. The ICO says the use should be proportionate, have minimal privacy impact, and not surprise people or be something they are likely to object to. A call to a logistics director's work line about warehouse software passes far more easily than a call to an assistant's personal mobile about the same product.
The ICO says to keep a record of your LIA. Write one per campaign type, date it and store it with the list.
Two duties come with this basis. Anyone may object to being marketed to, and that right is absolute. When someone objects, you stop.
Timing is the other one. The ICO's B2B guidance gives a deadline for the notice: if you got the data from a third party, tell the person within a reasonable period and at the latest one month after you collected it, unless an exception applies. The legitimate interests guidance adds that the notice must say you rely on legitimate interests and explain them.
What happens when you call from a bought list?
In May 2026 the ICO fined Energy Prices Direct GBP 160,000 for more than 700,000 unsolicited marketing calls to numbers on the TPS and CTPS. The calls ran from January 2024 to January 2025 and drew more than 30 complaints.
The company had bought the data without checking whether anyone had screened it against either register. For some records it could not even say where the data came from.
| What went wrong | Layer it broke | What would have prevented it |
|---|---|---|
| Bought numbers never screened against the TPS or CTPS | Call layer | Screening every row before the first dial, with the date logged |
| The source of some records unknown | Both layers | A source field on every record, filled in at import |
| Calls kept going for a year, through more than 30 complaints | Call layer | Treating each complaint as a trigger to pause and re-screen the list |
The AFK Letters case shows the consent side. The calls went to consumers, but the lesson carries over. In April 2025 the ICO fined AFK GBP 90,000 for 95,277 marketing calls made between January and September 2023 to people registered with the TPS.
The supplier's consent statements never named AFK. AFK's privacy policy mentioned email and said nothing about calls. AFK deleted customer data after three months, yet could not produce consent records even for calls inside that window.
Consent someone else collected covers you only when it names your company. That holds whatever data providers say about GDPR. The penalties are real: GDPR fines in cold outreach span email, LinkedIn and phone.
I do not buy cheap lists from freelancers. On email they bring weak open rates and high bounces. On phone the same problem shows up as rows nobody can trace, as the Energy Prices Direct notice describes.
How do the rules change in Germany and the EU?
The UK works with registers and objections. EU markets build on GDPR and add their own phone rule, and some set the bar much higher.
| Market | B2B live call rule | What to check before dialing | Primary source |
|---|---|---|---|
| UK | Allowed unless the number is on the CTPS or TPS without consent, or has told you to stop; UK GDPR covers the named person | CTPS, TPS, your own do-not-call list | PECR reg 21, ICO B2B guidance |
| EU, GDPR baseline | GDPR covers named people and leaves out data about legal persons (recital 14) | A lawful basis for each named contact, then the national phone rule | GDPR |
| Germany | Phone advertising to a business needs at least presumed consent; to a consumer it needs prior express consent | Whether you can show at least presumed consent from this business | Section 7 UWG |
Germany has the highest bar in this table. Section 7 UWG requires prior express consent for automated calling machines and for email advertising, and it does not spell out when consent can be presumed for B2B calls.
The courts fill that gap. IHK Nord Westfalen cites two BGH rulings: the test is whether the caller could reasonably assume the company expected or would welcome the call (I ZR 27/08), and a general link between your offer and that company's services is not enough (I ZR 191/03).
So plan as if the bar is high.
Most of what we run goes to the USA, the UK and some of Europe, in English. We have no particular focus on Germany. When a client needs it, we hold ourselves to stricter house rules and lean on LinkedIn. Cold email to Germany, Austria or the Czech Republic stays switched off unless a compliant basis exists. Anyone who opts out goes on an exclusion list for every channel.
What should you document before anyone dials?
A regulator will ask where each number came from and why you called it. Your records should answer:
- Data source per record. Name the supplier or the place you found it, plus the date. "Bought list, 2025" is not enough.
- Screening date per record. When each number was checked against the CTPS, the TPS and your internal do-not-call list.
- Re-screening before every campaign. Run it again even on a list you already screened, so the 28-day window above never catches you out.
- Subscriber type. Limited company, LLP, sole trader or partnership. Where you are unsure, record it as a sole trader.
- Your LIA. Dated and linked to the campaign that relies on it.
- Privacy information. When you sent it and which notice version.
- Objections. Logged the day they happen, with the date, and suppressed across every channel.
- Consent records, if you rely on consent. Wording that names your company and the channel, with the date and method.
My team keeps every lead in one CRM. Any CRM works, as long as nothing lives outside it. Every field above sits there, so a stop on a call also stops the email sequence and the LinkedIn messages to that person. One named person reads every reply on our campaigns, because short answers can hide objections and a stop request should never sit unread.
A single record might look like this:
| Field | Example |
|---|---|
| Contact | Logistics director, named, direct line |
| Subscriber type | Limited company |
| Source | Supplier X, delivered 3 November |
| Screened (CTPS, TPS, own list) | 4 November, all clear |
| Lawful basis | Legitimate interests, LIA v2 |
| Privacy information sent | 6 November, notice v3 |
| Objection | None |
If you outsource the calling, get four answers before you sign:
- Which registers do you screen against, and how often?
- Where does each record come from, and can you show it per row?
- Who logs objections, and how fast do they reach our CRM?
- Does the contract state these duties in writing?
Should a B2B team cold call at all?
For most founder-led B2B teams, cold calling is the hardest channel to keep compliant. A call to a stranger has to clear the data rules and the call rules at once, on a number that has never heard of you. Add volume and every extra dial multiplies that risk.
The list problem carries over too: a row you cannot trace back to a source is the phone version of a bounce. No script fixes a bad list or a weak sender. And if a funnel does not convert at small numbers, more dials will not make it convert at big ones.
What I can show is the written alternative. A US business consulting firm we worked with got 204 sales calls in 4 months from LinkedIn outbound and content. Its connection rate was 39% (38 of 98 requests). Every one of those meetings was booked in writing.
Writing also fits how outbound really works. One or two messages never get it done. Plan at least 5 or 6 touches, ideally across channels. Every one of those touches leaves a written trail, so consent and objections sit on each contact's record.
In our campaigns, the third follow-up usually works best, and it needs real time between the messages.
Conversations come first. Calls come out of conversations. So if a client wants phone, the warm list gets the calls. By then the person knows you, and you can ask in writing whether a call is welcome and keep that answer on file. The number still gets screened. If you want the email and LinkedIn side run for you, this is how my team approaches B2B lead generation.
This week, open your current call list and count the rows where you can name the source and a screening date. That count is the part of the list you could defend if a regulator asked.
Unsure whether a bought call list is safe to dial in the UK or Germany? Ask me how I would check it before anyone dials, on a call.
Questions founders ask about GDPR and sales calls
Does GDPR apply if all my customers are in the US?
If you sit outside the EU and UK and call no one there, GDPR does not govern your calls. A seller established in the EU stays under GDPR wherever its contacts live, because Article 3(1) of the GDPR ties it to processing linked to an EU establishment.
For US numbers, the FTC says most calls to a business that aim to sell to that business are exempt from the Do Not Call provisions, though a request not to call must still be honored. For consumer numbers, sellers must sync with the registry at least every 31 days.
Can I call a mobile number I found on a prospect's website?
A named person's mobile is personal data wherever you found it, and publishing it online does not change that. The bigger PECR risk is that a mobile on a small firm's site often belongs to a sole trader. Sole traders count as individuals and may be on the TPS. Screen the number, and log the page and date you took it from.
Do I need consent to record a B2B sales call?
Consent is one possible basis. A recording creates new personal data about a named person, so it needs its own lawful basis, and the person must be told. Recital 39 of the GDPR puts transparency first: people should know who holds their data and why. Say at the start of the call that you record and why, and offer to stop.
Who is responsible under GDPR when an agency makes the calls?
Usually you stay the controller, because you decide who gets called and why. A calling provider that works only on your instructions is normally a processor. Sign a written agreement that sets out its instructions, how it protects the data and what happens to the data when the work ends. Your PECR duty as the instigator stays with you either way.
