API Key Compromised
Scenario overview
Customer's API key was exposed publicly
What the caller is dealing with
Customer accidentally committed their API key to a public GitHub repo. Needs immediate key rotation.
How to practice this scenario
Open this scenario inside Call Flow's AI role-play, choose voice or chat, and Call Flow's AI plays the customer using the temperament, tech level, and budget posture above. Every session is graded instantly across rapport, discovery, objection handling, and closing technique, so reps know exactly what to fix before the next attempt. See the full feature set or start a $1 team trial.
Skills you'll build
- Identity verification
- Walking through MFA setup
- Calming security anxiety
- Following lockout policy
- Documenting incidents
More scenarios in Account Security
Account Takeover Report
hardCustomer believes their account was hacked
Compliance Audit Request
hardBusiness customer requesting security audit information
Data Export After Security Incident
hardCustomer wants all data after a security breach
Employee Access Revocation
mediumManager needs to revoke a terminated employee's access
Identity Verification Failure
hardCustomer can't pass identity verification
Locked Out After Security Update
mediumCustomer locked out after security policy change
Malware Warning on Account
mediumCustomer seeing malware warnings when accessing account
Password Reset After Breach
easyCustomer wants to secure account after data breach news
Phishing Email Report
hardCustomer received phishing email impersonating company
Recovery Email Change
hardCustomer needs to update recovery email for security
Security Question Reset
mediumCustomer forgot security questions
Session Hijacking Report
hardCustomer suspects their active session was hijacked