Turning a TCPA Crisis Into an Enterprise Consent Strategy

A Lawsuit, Then a Regulator

A top-tier national bank had relied on PossibleNOW for marketing preference management for years. After a TCPA lawsuit, the bank’s federal deposit insurer added TCPA compliance to its audit procedures and made clear the bank’s insured status was at stake.

Active litigation plus a regulator with that kind of leverage turned compliance from a marketing operations issue into a board-level priority. The bank faced a build-versus-buy decision under real pressure.

Why PossibleNOW

PossibleNOW had stayed close to the bank for years before the lawsuit and had raised DNCSolution as a fit for exactly this exposure. When the crisis hit, the decision came down to building in-house or bringing in PossibleNOW.

PossibleNOW made the case that automated APIs and managed registration would get the bank compliant faster and keep it there. Managed registration services, with PossibleNOW handling all registrations, were a major factor.

Automated Compliance, Then Enterprise Consent

DNCSolution was deployed with fully automated, API-driven scrubbing and managed registration services, about four months from signed contract to full deployment.

• A new fraud-alert use case. The bank screens against the Reassigned Numbers Database to make sure fraud alerts reach the right customer. When a number has changed hands, the bank holds the alert and finds another way to reach the customer.
• Enterprise expansion. Adoption spread to additional teams and business units after launch.
• A path to enterprise consent. The bank is moving to PossibleNOW’s newest consent platform and plans to make PossibleNOW its consent master across the enterprise over the next several years.