Last week, I talked about the risks of relying on blacklists to protect your call center environment. This week, I’d like to discuss the reverse of blacklisting, a process called whitelisting.
Much in the way blacklists are designed to block specific phone numbers from entering a system, whitelists recognize devices or phone numbers that have been approved by a trusted source. For example, when a device or number is added to a whitelist, it can automatically ring through to a live telephone agent. On the flip side, any number that’s not on the list isn’t allowed into the system, period. It’s as simple as that.
However, building a whitelist and relying on it to determine which calls can or cannot be trusted is — much like blacklists — a risky proposition. Based on your experience with a phone number, you can almost be sure which numbers you can trust to allow into your system. What’s not so clear is the real-time status of those numbers, and the impact whitelist dependency can have on the security of your call center and your overall customer experience.
Here are a few areas where whitelists can fall short in protecting your customer environment:
We know managing a call center is a daily challenge. Call centers are constantly deploying different authentication tools to validate inbound calls and help curb fraud. The bottom line is, when you rely on blacklists or whitelists to determine which calls are good or risky, you’re essentially using yesterday’s information to identify today’s callers.
The modern day call center can’t afford to put all its trust in what it knew yesterday. Criminals are too smart for that. Only passive, real-time authentication that doesn’t rely on sensitive customer data can provide up-to-the-minute caller verification on every call to deliver a more secure, seamless environment for their customers.