Skip to content

Regulatory DNC Suppression List Interoperability

Description

Integrates ExpertFlow contact lists natively with internal Do-Not-Contact registers and external regulatory suppression lists — including TCPA (US), TPS/CTPS (UK), and GDPR opt-out stores — before any dial attempt is initiated. Suppression is enforced at list-load time and again at dial time, so newly registered opt-outs are honoured within the enforcement window without requiring a batch re-export. Compliance evidence (suppression check timestamp, list version, match reason) is recorded per dial attempt for audit purposes.

Canonical use case

A UK financial services firm runs outbound call campaigns subject to TPS and CTPS regulations. Before each campaign window, the platform checks the loaded contact list against the current TPS register and removes matching numbers. At dial time, a second real-time check catches any numbers that registered since the batch import. Compliance officers can export a per-campaign audit trail showing each suppressed number, the suppression source, and the timestamp — removing the need for a separate TCPA/TPS compliance layer such as Acqueon or NobelBiz.

Open Items

  • [ ] Axiom opportunity — axiom-018 (queued, not yet authored): "List management interoperates with TCPA/TPS DNC lists (collapses Acqueon/NobelBiz value proposition)". Run bmad-axiom-elicitation when ready. Seed: ExpertFlow list management interoperates natively with internal + public DNC suppression lists for TCPA/TPS compliance, before any dial attempt. This collapses the exact value proposition Acqueon and NobelBiz sell as a standalone compliance layer into the platform.
  • [ ] Secondary domain note — TCPA/TPS/GDPR compliance framing also touches security domain; ammara.bokhari (core-objects) should align with zaryab.baloch (security) on whether a separate security-domain feature is needed for the audit-trail / data-retention aspects
  • [ ] Dependency assessment — set dependencies_assessed: true after SA confirms the full chain (e.g. whether efv-security-NNN audit logging is a hard dependency)
  • [ ] Effort estimate — replace 0 with rough engineering days; note external registry API integration complexity (TPS registration download, TCPA Wireless Block checking)
  • [ ] implementation_stack — populate: TPS/CTPS API connector, TCPA wireless block list feed, internal opt-out store adapter
  • [ ] Pattern membership — add efv-core-objects-012 to efv-sol-011 (Outbound Campaign Management) features_included
  • [ ] funding_track — populate when backlog prioritisation occurs