Contact Center Authenticaion
summary
Research calls to about 45 contact centers reveal most systems use phone, email or DOB to identify customers but rarely authenticate them; several ask for Social Security numbers. Helpful implementations include Netflix’s six-digit service code, Amazon’s contextual SMS 2FA, and American Express’s one‑time fraud codes; dangerous failures include agents giving or changing another customer’s phone number (e.g., Cathy Robinson). Recommendations: require real authentication like one‑time passcodes or in‑app verification, perform silent risk checks, and limit exposed data and agent privileges.
AI-written summary · about
chapters (10)
- 0:00Introduction to contact center authentication
- 3:12Research methodology and call examples
- 8:52Authentication methods used by companies
- 13:06Companies doing authentication well
- 15:32High-risk phishing vulnerabilities
- 19:45Accidental phishing incident
- 20:46Recommendations for better security
- 28:48Future of call center authentication
- 29:49Key takeaways and call to action
- 30:52Q&A session begins
related talks
26mThe Forgotten
30mAuthentication Strategies to Protect Your Customers and Your Brand from Sophisticated Attacks
25mAuthentication Beyond SMS
29mAuthentiCall: Efficient Identity and Content Authentication for Phone Calls
39m2FA, WTF?
42mChallenges in User Authentication: Balancing Security & User Experience
15mTransforming security and experience with digital identity
24m2FA in 2020 and Beyond