Data Soap
Back to blog

AI ransomware warning for UK firms: 5 customer data hygiene checks to do this week

DSData Soap·3 min read·20 November 2026
AI ransomware warning for UK firms: 5 customer data hygiene checks to do this week

Where does your customer data live—and how many copies are still in use?

The National Cyber Security Centre’s 3 November 2026 warning says AI-powered malware is highly likely to feature in a ransomware attack against UK critical national infrastructure by 2028. It also calls on organisations to address longstanding security weaknesses.

Data Soap helps reduce messy-data risk and wasted outreach. It is not a ransomware prevention tool. These checks support better customer data management alongside your organisation’s cyber security work.

For CRM managers, marketing teams, agencies and call centre operations, there is practical work you can start this week.

1. Find duplicate customer list copies

Start with one active campaign or customer segment. Trace its journey from the CRM to shared drives, inbox attachments, agency folders and old dialler exports.

Record where each copy lives, who owns it, why it exists and whether anyone still uses it. Identify the authoritative source and make sure everyone knows which version to use.

An old export can contain outdated contact details or miss a recent opt-out. Cleaning the CRM will not fix those disconnected copies.

This week’s action: Create a simple inventory for one customer list. Agree which copies should remain available and which need review under your retention policy. Preserve suppression records and anything subject to a retention requirement.

2. Validate phone and email data before the next upload

A correctly formatted phone number may no longer be active. An email address that worked last year may now bounce.

Before the next campaign or dialler upload, run the checks relevant to each contact channel. HLR mobile validation provides mobile-network information, while email validation helps identify invalid addresses and other quality concerns.

Keep inconclusive results separate for review rather than treating every failed lookup as proof that a record is unusable. Record when each check ran so colleagues can assess how current the result is.

Validation does not establish identity, guarantee delivery or give permission to send marketing.

This week’s action: Validate the list scheduled for your next campaign and review the results before uploading it.

3. Screen calling lists against TPS, CTPS and your own suppression list

Before restarting a calling campaign, check the actual list going into the dialler—not just an earlier CRM version.

Screen against the Telephone Preference Service (TPS), the Corporate Telephone Preference Service (CTPS) and your organisation’s own do-not-call records.

For B2B campaigns, both registers matter: some businesses use TPS and others use CTPS. The ICO’s B2B marketing guidance explains these requirements.

A clear screening result alone does not establish permission to call. Respect previous objections and assess any consent exception against current ICO guidance. Email, SMS and automated marketing calls have separate rules.

This week’s action: Give one person responsibility for confirming screening and suppression checks before the next dialler upload.

4. Replace repeated spreadsheet fixes with a repeatable process

If every campaign involves repairing phone formats, copying corrected columns and emailing another “final” spreadsheet, fresh mistakes can enter at every handover.

Choose one recurring problem and agree a consistent correction rule. Apply it through a controlled import, a repeatable cleansing process or an integration. Keep the customer record identifier attached so results return to the right CRM record.

Review record counts before and after processing, retain the reasons for changes and avoid overwriting good data with uncertain results.

This week’s action: Replace one repeated manual fix with a documented process that another colleague can follow.

5. Validate new data before it spreads through the CRM

Cleaning an existing database helps. Checking new records as they arrive reduces the amount of repair work waiting next month.

Use the Data Soap API documentation to explore validation within your forms, applications or CRM workflows.

Give people a chance to correct obvious entry errors. Route uncertain results for review, and define what happens if a validation service is temporarily unavailable. Store the check result and timestamp separately from marketing preferences.

Validation and permission to contact someone answer different questions. Your workflow needs to preserve both.

This week’s action: Pick one high-volume capture point and map the checks it needs before a new record reaches downstream systems.

Start with the next list you plan to use

You do not need to overhaul every system this week. Start with one list, one owner and one repeatable workflow: find its copies, validate its contact details, apply the relevant suppression checks and improve how new records enter.

Try a live sample with Data Soap’s £4.99 starter pack (+VAT), or request a quick workflow review through the pricing page. The starter offer is available to new customers once.

Put clean data to work on your own list.

£100 of credits for £4.99. New customers, once.