data protection

Verifying identity on the phone before sharing personal data

AA
Aurum Avis Labs Author
7 min read

Verifying identity on the phone before you disclose personal data

Verifying identity on the phone is the step reception, support and HR take before they read out order status, salary figures or reset a password. Swiss law expects appropriate technical and organisational measures (Art. 8 FADP); it does not publish one mandatory question list for every sector. Fraud reports to the National Cyber Security Centre included 719 CEO fraud cases in 2024 and 971 in 2025 (BACS figures, not our survey). This guide is for owners and desk staff in SMEs of about 20 to 250 people without a dedicated data protection team.

Consent for photos on the site is a different job; see staff photos on the website. Routine mail habits sit in sending personal data by email.

  • RuleNo cold trust

    Caller ID can be spoofed. A familiar voice is weak proof on its own.

  • MethodCallback

    Use the number already stored for that person or account, not the one on the display.

  • DataMinimum

    Answer the question asked, not the whole dossier.

  • LogOdd calls

    Note pressure, secrecy demands and failed callbacks.

What to do on an inbound call

Start with what they need and which customer, employee or supplier record it touches. Use two independent checks where you can: something from your file (contract number, date of birth on record, last invoice total) plus a callback to the mobile or direct line in CRM or HRIS. Read out full addresses, IBANs or health details only after both checks look plausible.

Password resets belong to your IT process, not to a verbal claim of seniority. Finance should treat payment instruction changes like the patterns in CEO fraud in Switzerland, even when the story arrives by phone.

Callers who pose as your IT provider or as a «new finance contact at a supplier» get the same callback rule: the number comes from the contract or the ticket, not from the call. Never hand out credentials over the phone, not even «just to verify». If your IT partner really needs something, they will call you back on the line stored in the contract.

Reasonable checks

  • Callback to the number in CRM, not the inbound display
  • Two data points that are not on the company website
  • Named supervisor before exporting a full HR or client dossier

Weak checks

  • «They knew our address»
  • Name plus company name only
  • WhatsApp voice note with no callback

Callback in practice

  1. Pause the read-out

    Say you will call back on the number you hold. Do not argue on the line.

  2. Look up the stored number

    CRM, HRIS or the signed contract. Do not save a new number from this call first.

  3. Call and confirm

    Ask them to state the request again. Match account or employee ID.

  4. Disclose the minimum

    One fact or one document path. Offer a portal if the file is large.

If nobody answers the callback, stop. A secure channel (portal message, post to the known address, in-person with ID) beats a partial guess.

HR, payroll and former employees

HR lines attract calls about balances, references and «quick confirmations». Treat them like customer data: callback to the number on the personnel file, not the mobile that called in. For a former employee, check whether your retention rules still allow the disclosure before you read anything aloud. Application dossiers kept too long are covered in how long to keep job applications in Switzerland.

Managers sometimes ask reception to «just tell the caller» a salary figure. Send them back to HR with a ticket ID. Reception should not browse full HR screens while a stranger waits on hold.

Large exports and file shares

When someone asks for «everything on the account» or a spreadsheet by phone, treat it as an export, not a status update. Name a portal upload or a channel from sharing files that contain personal data. Read out single fields only after callback. If the caller refuses callback, refuse the export.

  • Date and time of call
  • Number shown on the display (not trusted as proof)
  • Account or employee ID discussed
  • Action taken: disclosed, refused, escalated
  • Initials of the person who handled the call

Store the log where your team already keeps security notes. Six months is a practical default unless litigation needs longer.

Outbound calls and «call me back» e-mails

When you dial out, confirm you reached the right person before health, debt or disciplinary topics. Voicemails should not carry sensitive detail. If someone writes «call me urgently about payroll», verify through HR’s usual channel before you read balances aloud.

Temporary reception staff need the same script and the same CRM fields as permanent colleagues. Leased desks should not show full dossiers on screen.

What this is not

Not a guide to law-enforcement warrants (follow counsel). Not a product comparison of helpdesk tools. Not the workflow for e-mail sent to the wrong recipient. Access rights under Art. 25 FADP still require a lawful basis; the phone script does not replace that check.

A made-up example: the urgent supplier list

A made-up example: a 50-person wholesaler in St. Gallen. Reception gets a call «from the CFO» on a mobile, demanding a customer list for a «same-day audit». The caller knows the CFO’s name. The agent offers callback to the CFO’s extension; the caller hangs up. The agent logs date, displayed number, request and initials, then alerts finance. The real CFO confirms no request. The firm adds a one-page phone script and rehearses it in the next team slot.

  • HR and a former employee

    Caller asks for a reference letter by phone. HR calls back the number on the application file and sends only what policy allows.

  • Support and order detail

    Ticket ID plus callback to the account mobile before reading payment history.

  • Partner «new finance contact»

    Match the e-mail domain on the contract; do not add a wire number from the call alone.

Report odd calls internally

When someone applies pressure, demands secrecy or hangs up after you offer callback, treat it as a signal, not an awkward customer moment. Tell finance or a named manager the same day, with the log line from the checklist. Repeat attempts belong in the same note. You do not have to prove fraud on the spot. You show the firm refused disclosure until identity was plausible.

Insurer questionnaires often ask whether desk staff know how to handle personal data on the phone. A one-page script plus ten minutes in the yearly team slot is enough for many SMEs if CRM numbers stay current.

Who can keep it light

Two people who always answer the same customers may agree on callback and keep a paper log until volume grows.

A shared hotline with rotating temps needs written scripts, role-based CRM and a monthly five-minute review of logged odd calls.

May we ask for a copy of an ID by e-mail?

Only when necessary, on a secure channel, with retention defined. For routine status questions, callback plus two account facts is often enough.

Does one correct answer prove identity?

No. Social media and old leaks make single facts cheap. Pair callback with file data, and escalate unusual export requests.

A live privacy awareness session walks through phone scenarios with your real roles, in one to two hours, with a short follow-up conversation a few weeks later.

data protection phone identity fadp switzerland
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.