The message comes in through Slack. A manager needs a number removed from the calling lists. DNC request — customer called back, asked to be removed, compliance requires it.
Before the tool existed, that message meant a task.
Log into each system. Find the number. Remove it. We run Zoom Phone, Zoom Contact Center, three Convoso campaigns, and five Telesero servers each carrying one to three campaigns of their own. One at a time. While the manager waited.
If I was in the middle of something else, they waited longer. If it was busy, it stacked. On a heavy day, DNC requests could sit for an hour before anyone touched them. That’s a compliance window. Every minute a flagged number stays active is a minute of exposure.
—
The tool collapses that process to three seconds.
Manager types the number into a Slack slash command. Hits send. The request goes to a Cloud Run service, which fans out across all active systems simultaneously — Zoom Phone, Zoom Contact Center, Convoso, Telesero — logs every result to cloud storage, and returns a confirmation to the channel. Done before they’ve switched back to the call they were on.
Twenty requests a week. Zero manual steps. An audit trail in cloud storage for every removal, timestamped, with each system’s response logged separately.
That’s the version that’s running now. Getting there was a lesson in why compliance automation needs verification, not just automation.
—
For several weeks after the tool deployed, I had confidence it was working. The Slack confirmations were coming back clean. Everything appeared to be running.
Then I went into the deployment configuration.
The Convoso API token was not there. It had never been there. The tool had been hitting every system except Convoso since it went live. The confirmation messages were returning clean because the code was handling the missing credential silently — continuing past the failure instead of surfacing it.
Every DNC request submitted during that period had been processed everywhere except one of the primary dialers.
The fix was one line. The lesson was architectural: compliance tools need to fail loudly, not gracefully. A system that reports success when it’s skipping a step is more dangerous than one that throws an error. I added explicit validation — if any system returns a failure, the tool reports failure, not partial success. The audit log now surfaces each system’s confirmation individually on every request.
The silent failure period required a remediation pass. We identified every affected number and reprocessed them.
—
The tool now handles DNC compliance the way it should have from day one. Managers don’t think about DNC requests as tasks anymore. They submit the number and it’s done.
The exposure window — which used to stretch to an hour on busy days — is now three seconds.
If your contact center handles DNC requests through a manual process, the architecture is straightforward to build and the cost of not building it isn’t theoretical. It shows up in audit logs, in compliance reviews, in the call you get when a number that should have been removed two hours ago got dialed again.
The intake form is at rfditservices.com/intake.html. The first conversation is free.
Leave a Reply