7 Signals: Detecting Deepfake in Conversations — Sales Checklist
Deepfake is no longer just about videos. In B2B sales, attacks happen over the phone, video, and direct messages. Here’s a simple checklist of 7 signals and procedures you can implement today—without new tools or coding.
Key takeaways
- Don't rely solely on your ears. Respond with a process: team password, control question, callback.
- Any change in bank account: dual approval and confirmation from the client's domain.
- Add risk fields and tags in CRM, and reminders in VoIP/calendar to your checklist.
- Simple automations (Zapier/Make/n8n) send alerts and block risky steps.
- New detectors are helpful, but a consistent team procedure works best.
Deepfake (forged voice or video created by AI) can trick you into changing account details in just one conversation. In sales, this happens over the phone, video, and direct messages (DM). The industry is discussing detection on phones, like the announced Scam.ai–Qualcomm partnership. Don’t wait. You can implement this today—without purchases or coding.
7 Signals in Conversations and Quick Tests
First, let’s look at what you can do during a call. Each signal has a simple test and a ready-to-use phrase. The goal is not to judge by ear but to confirm identity in a predictable way.
- Voice or pace doesn’t match the known person. Use a team password (an agreed word or question known only to you). Say: Before we proceed, please provide our verification password.
- Strong pressure for time or a request to switch channels (e.g., from email to WhatsApp/DM). Pause and callback (return the call to a known number from your company directory). Say: I’ll call you back in 2 minutes on your
- known number.
- Lack of small details from shared history. Ask a control question (a small fact not found online). Say: Please remind me, what color is the reception area in our office?
- Request to change bank account or payment details during the conversation. Activate the four-eyes principle (dual approval). Say: Such a change requires confirmation from two people; we’ll get back to you via email.
- Video looks 'too perfect': little blinking, eyes looking away from the camera, unnatural lighting. Do a gesture challenge (ask for a quick, specific movement). Say: Please move the camera to the left and touch your left耳
Channel and Money Rules That Stop Most Attacks
Simple channel and authorization rules cut off the most common attempts. When known to everyone, the pressure of the moment loses its effect.
- Callback only to known numbers. New number or alias? Require confirmation from a company email or through another known person on your side.
- Dual approval for any change in bank account, credit limit, and payment recipient. Minimum: salesperson and finance/manager.
- Email confirmation template from the client: brief, with the new account number and tax ID. Accept only from the client’s company domain.
- 24-hour rule for significant changes. Exception only after verifying the decision-maker through another channel (e.g., separate callback).
- Blacklist of high-risk phrases in notes: account change, urgent transfer, new beneficiary. If mentioned—pause the conversation and verify.
CRM, VoIP, and Calendar: Implement This Today
CRM is a system for managing contacts and contracts. VoIP is phone service over the internet. With a few simple fields and reminders, you can turn your checklist into team action.
- CRM (e.g., HubSpot, Pipedrive, Salesforce): add fields for Team Password, Safe Numbers, Last Verification Date, and High-Risk Checkbox (deepfake).
- Task/note templates: Request for account change – paused; Callback completed; Verification of 2 people – required. This standardizes the team’s language.
- VoIP (e.g., Twilio, RingCentral): list of safe numbers and a quick tag for Callback to known number. Shortcut for SMS: I’ll call back to the known number in 2 minutes.
- Calendar (Google/Microsoft): short reminder 2 minutes after the call starts – Check team password. Helps when under time pressure.
- Legal note: if you record calls, always inform the other party and check local data protection laws.
No-Code Automations: Zapier/Make/n8n in Practice
Zapier, Make, and n8n are tools for connecting applications without programming. Simple rules are enough for alerts and blocks to work automatically.
- Alert on risk: when you mark High Risk in CRM, the tool sends a notification to Slack/Teams, creates two tasks for approval, and changes the opportunity status to Paused.
- Callback with checklist: after a call from an unknown number, the system sends an SMS/email to the caretaker with 7 signals and a button to Callback to known number. It works based on call logs.
- Account change = block: saving a new account in the CRM field automatically creates a task for finance and sends a request to the client for confirmation from the company domain.
Deepfake in sales is a real risk today, but it doesn’t require expensive tools. Implement a team password, callback to a known number, and dual approval for account changes. Then add fields in CRM and simple automations. Want ready templates and support for implementation in your CRM/VoIP? Schedule a short consultation—we’ll tailor the checklist to your process.
Frequently asked questions
Will deepfake detectors solve the problem for me?
They can help, but they are not infallible. The industry is discussing device solutions (like the announced Scam.ai–Qualcomm partnership), but the best protection comes from clear procedures: callback, control questions, and dual approval.
How do I establish a good team password?
Choose a simple, non-public password or question known only to both parties. Avoid data from the internet (dates, names). Change it every 1-3 months and keep it in the CRM field. Decide when and who will say it during the conversation.
Will additional verification offend the client?
Most clients understand security issues. Use a neutral message: For the protection of both parties, we will confirm this with a short callback to the known number. It will take up to 2 minutes.
Will these steps slow down sales?
They usually add a minute or two to the conversation, but they protect against very costly mistakes. A clear procedure shortens discussions under pressure and standardizes team actions.
Does this work in DMs and messaging apps too?
Yes. If the request came in a DM, move the verification to a known channel: callback to the saved number or email from the company domain. Treat links and files in DMs cautiously until identity is confirmed.