Marketing Consent and Dormant Trader Outreach

A trader who registered in 2021, deposited once and hasn't logged in since still sits in your CRM with a marketing checkbox ticked next to their name. Whether that checkbox still counts as dormant trader marketing consent for an AI voice call is the question every compliance desk has to answer before a reactivation campaign dials. And the answer depends on four things: what the trader ticked, which legal entity collected it, which country the number is in, and whether the voice on the call is a person.

This guide covers what counts as consent for a dormant trader, what the FCC and the UK ICO say about AI voices, where the line between account servicing and marketing sits, how to audit a list before the first dial, and what has to happen the moment a trader says stop.

Key Takeaways

• FCC ruling 24-17, adopted February 2, 2024, confirms that AI-generated voices are "artificial" voices under the TCPA, so US marketing calls with an AI agent need prior express consent.
• Under 47 CFR 64.1200, a telemarketing call using an artificial voice needs written consent that names the seller, the number and the fact that an artificial voice will be used.
• The UK ICO says general marketing consent, "or even consent for live calls, is not enough" for automated marketing calls; the consent has to cover that call type.
• GDPR Article 21(3) is absolute: once a trader objects to direct marketing, "the personal data shall no longer be processed for such purposes."
• Topcalls charges $0.35 a minute all-inclusive, so a two-minute reactivation call costs $0.70, and every name the audit suppresses is $0.70 not spent on a call you couldn't defend.

1. What counts as dormant trader marketing consent?

Dormant trader marketing consent is a record showing the trader agreed to receive marketing from your brokerage, by phone, through the legal entity that will call, in wording you can still produce. Three things have to be true at once: the form text exists, it covers a call rather than just email, and the trader hasn't withdrawn it since. A yes/no flag in the CRM proves none of the three.

Most dormant lists split into three buckets once you look at the evidence behind the flag:

• Explicit marketing consent: a ticked box on a dated registration form, with the form version and the wording filed. This is the only bucket that supports a marketing call without a further argument.
• Existing client relationship: a funded account with trade history but no marketing tick, or a tick nobody can find the wording for. Account servicing is fine here. Marketing depends on the country.
• None found: a lead who filled in a web form, never passed the deposit page, and agreed to a generic "contact me" line. Weak under GDPR, and nowhere near the US bar for an AI voice.

The UK gives brokers one route that doesn't need a tick. The ICO's guide to telephone marketing says you "can also make live calls without consent to a number if it is not listed on the TPS, but only if that person hasn't objected to your calls in the past." The same page closes the obvious loophole: TPS numbers are off limits "even if they are an existing customer." So the TPS screen isn't optional, and a funded account doesn't override it.

Consent also belongs to a legal entity. Brokers move clients between entities when a licence changes or a new jurisdiction opens, and consent collected by the old entity may not carry over to the new one. Ask counsel before assuming it does. The existing UK PECR guide covers the TPS and CTPS mechanics in more depth.

2. Does old registration consent cover an AI voice call?

Often not. The consent a trader gave for "calls" three years ago was written with a human dialer in mind. In the US, FCC ruling 24-17 says AI-generated voices are "artificial" under the TCPA, which puts a marketing call into the prior-express-written-consent tier. In the UK, the ICO says consent for live calls "is not enough" for automated marketing calls. The wording has to name the method, and most registration forms don't.

The FCC's declaratory ruling of February 8, 2024 is short and direct: "callers must obtain prior express consent from the called party before making a call that utilizes artificial or prerecorded voice simulated or generated through AI technology." The ruling adds that where the message "includes or introduces an advertisement or constitutes telemarketing, it must also offer specified opt-out methods for the called party."

What "prior express written consent" means is spelled out in 47 CFR 64.1200. It's an agreement in writing, bearing the signature of the person called, that authorizes the seller to deliver telemarketing messages "using an automatic telephone dialing system or an artificial or prerecorded voice," names the telephone number, and tells the person they aren't required to sign as a condition of buying anything. A registration form's "I agree to be contacted" line fails that test on at least three counts.

The UK rule for recorded-message calls is stricter still. The ICO writes: "You must not make an automated marketing call, that is, a call made by an automated dialling system that plays a recorded message, unless the person has specifically consented to receive this type of call from you. General consent for marketing, or even consent for live calls, is not enough." A conversational AI agent isn't a recorded message, and whether an interactive AI call sits under regulation 19 or regulation 21 is a question for your counsel. The safer planning assumption is the stricter one.

One shortcut applies to many CFD brokers: if your licence doesn't permit soliciting US residents, suppress every +1 number and the TCPA analysis disappears with them. The TCPA guide for financial services calls covers the case where you do call US numbers.

The AI Calling Compliance Planning Checklist for Brokers walks through consent and lawful basis, US TCPA setup, MiFID II recording, data retention and cross-border rules, with a blank for the named approver on each section.

3. Is a reactivation call marketing or account servicing?

A call is servicing when the trader needs the information whether or not they ever trade again: a KYC document about to expire, a dormancy fee falling due, a balance that will be swept. It becomes marketing the moment the script says come back and trade, mentions a bonus, or points at a new instrument. Servicing sits under the account terms. Marketing needs marketing consent. Get the classification in writing before the script is written.

The trap is the mixed script. "Your inactivity fee is due on the 30th, and by the way, gold has moved 8% this month" turns a servicing call into a promotion, and the whole call now needs the higher consent bar. Keep the two campaign types apart: separate lists, separate scripts, separate lawful basis, separate approver. KYC reminder calls are the cleanest example of a servicing call, and they're the right first campaign for a list where marketing consent is thin.

Disclosure applies either way. FCC 24-17 restates that "all artificial or prerecorded voice messages must provide certain identification and disclosure information for the entity responsible for initiating the call." So the opening line names the brokerage, says the voice is an AI agent, and states why it's calling, on a servicing call as much as on a marketing one.

4. How do you audit consent before a reactivation campaign?

Pull the consent record for every account, split the list by lawful basis and by country, remove every opt-out from any channel, then set a maximum consent age and apply it with no exceptions. Budget at least a working day for a list of a few thousand accounts. The output is three lists: call with the marketing script, call with the servicing script, don't call. Only the first two ever reach the dialer.

Two decisions in that table are policy, not law. The maximum consent age has no single legal number, so set one with your compliance officer and apply it to every list the same way, so nobody argues about a 2019 lead halfway through a campaign. And the channel-neutral reading of an opt-out (an email unsubscribe means no calls either) is the safer one under GDPR's right to object, which is why the table treats it as final.

The audit pays for itself before the first call connects. At Topcalls' rate of $0.35 a minute all-inclusive, a two-minute reactivation call costs $0.70. If the audit removes 1,800 accounts from a 5,000-name list, that's $1,260 of dials that would have gone to people who can't lawfully be marketed to, plus the complaints those dials would have produced. Run the surviving segment through the dormant trader revenue calculator to see what the call-eligible list is worth before you commit a budget.

5. What happens when a dormant trader objects mid-call?

The call ends, the number is logged, and nothing dials it again. GDPR Article 21(3) says that once a person objects to direct marketing, "the personal data shall no longer be processed for such purposes." The ICO says to "keep your own 'do not call' list of people who object or opt out, and screen against that as well." Test the path by saying "stop calling me" on a test call and checking the CRM.

Article 21(2) makes the right available "at any time," and there's no balancing test: the broker can't weigh its interest in reactivation against the objection. That's different from most GDPR rights, and it's why an AI agent's objection handling has to be a hard stop rather than a rebuttal branch. The agent confirms the request, says it'll be actioned, ends politely, and the number should be suppressed before the next dial attempt, not after a nightly sync.

For US numbers, FCC 24-17 requires telemarketing messages with an artificial voice to offer "specified opt-out methods for the called party to make a request to stop calling that telephone number." Topcalls' compliance posture covers TCPA, TSR, DNC and GDPR, and the secure infrastructure page describes how recordings, transcripts and suppression are handled. The consent records and the list are still yours.

Suppression is only as good as the sync behind it. A trader who objects on a Tuesday and gets a second call on Wednesday because the CRM export was pulled Monday night is the complaint pattern to design against in customer reactivation campaigns. The do-not-call screening guide covers how to wire suppression so it applies before every dial, and the GDPR guide for AI voice calls covers the data-subject rights beyond objection.

6. When this doesn't fit

A consent audit and a dormant reactivation campaign aren't the right move for every list. Four situations where you should stop and change the plan:

• The form wording is gone. If the CRM holds a yes/no flag and nobody can produce the registration form text, you can't defend a marketing call on that consent. Run a re-permission email first, or restrict the campaign to servicing calls.
• Your licence bars the market. A CFD broker that can't solicit US residents shouldn't be reading the TCPA section at all. Suppress the segment. The same logic applies to any country where your entity isn't authorised to promote.
• The list is a few hundred names. Below that size a human agent working from a checklist costs less than building segmentation. The audit is still mandatory; the automation isn't.
• A regulator has an open inquiry into your marketing. Don't launch a new outbound channel while one is running. Get counsel to clear it, in writing, first.

A consent audit is the least glamorous part of a reactivation campaign and the only part a regulator will ask to see. If you'd like a second pair of eyes on your list structure and which segments can go live first, book a 30-minute call and bring the consent form versions with you. For more on how the rest of the compliance picture fits together across jurisdictions, the GDPR outbound calling guide is the next read.