The controls are applied before the call, not audited after it.
A suppression list that gets checked once a week isn't a suppression list. Everything here is applied at the moment a call would be placed, which is the only moment it can stop anything.
Most systems tell you afterwards.
Suppression lists get uploaded and then drift out of date. A TPS screen is done once at import and never again, while new leads keep arriving behind it. Someone removes a block for a good reason and nobody records why.
None of that is visible on a normal day. It becomes visible when a complaint arrives, and by then the only question is whether you can prove what you did.
What gets checked, and when
Each of these blocks or records something at the point it matters — before a call is placed, not in a report next month.Do Not Call
Add a number and nothing rings it again — any campaign, any agent, whoever imports it next, permanently.
Your own suppression lists
Past customers, complainants, a client's exclusions. Upload them and they're enforced at dial time.
TPS screening
A screen counts for 28 days. We tell you how old yours is and how many leads have arrived since — a stale screen is the failure nobody notices.
Consent, kept with the lead
Where their permission came from and when. If someone complains, the answer is on the record rather than in somebody's memory.
Marked DNC mid-call
An agent can mark a number Do Not Call in one action while the customer is still asking — not afterwards, from a settings page, if they remember.
Pause and resume
Agents pause recording while card details are read out, then resume. Both sides stop, and every pause is logged with who did it and when.
Retention you set
Recordings are deleted automatically after the period you choose. Keeping call audio forever is a liability, not an asset.
An audit trail
Every call, outcome, pause, review and released block, with a name and a time against it. A question about a call six months ago is a lookup, not an investigation.
Where your data actually sits.
Three plain statements, not a row of badges. We hold none of the usual attestations and won't imply otherwise.UK-hosted data
Your leads, calls and recordings are stored in the UK. Nothing is moved offshore for processing.
Recordings encrypted at rest
Call audio is encrypted in storage and served through short-lived signed links, never a public URL.
GDPR-aligned handling
Retention periods you set, deletion on request, and an audit trail of who accessed what.
This doesn't make you compliant, and we won't pretend it does.
Dialspace gives you the controls to run your calling within the rules you operate under. What you're obliged to do depends on where you are, what you sell, how you got your data and what your customers agreed to. Those obligations are yours, and nothing here is legal advice.
Any supplier telling you their software makes you compliant is selling something that doesn't exist. Take your own advice, and use these controls to do what it tells you.