How a Philippines virtual assistant can screen scam calls

Why a scam-call lane belongs in the script

A busy phone line makes people rush. A caller may claim to be a bank worker, software vendor, delivery company, public office, senior leader, or angry customer. The assistant needs a calm way to pause the request without starting an argument.

The risk is not small. In data released in March 2025, the Federal Trade Commission said consumers reported more than 12.5 billion dollars lost to fraud in 2024, which was 25% more than the year before. The same release says phone calls were the second most common contact method in 2024.

The FBI saw the same pressure online. Its 2024 Internet Crime Complaint Center report lists 859,532 complaints and 16.6 billion dollars in reported losses, a 33% rise from 2023. These reports cover many kinds of crime, so they do not tell you how many bad calls will reach one business.

They do show why a small team needs a repeatable stop point. Your Philippines-based assistant should not approve a payment, reset an account, share a code, or change customer records because a caller sounds sure of themselves. The assistant can be warm while still saying, "I need to verify this through our normal contact path."

The five facts an assistant may collect

Keep the first note short. Ask for the caller's name, company, callback number, reason for calling, and the person or account they say they know. Do not ask for a password, one-time code, full card number, or copy of an identity document.

A caller who refuses basic details may be a problem, but a willing caller is not proven safe. The assistant should repeat the request in plain words and tell the caller that a manager will use a saved number or known channel to respond. That step breaks the pressure without making an accusation.

NIST calls this kind of work fraud mitigation: detect, respond to, and prevent access through a false identity. Its identity proofing guidance also points to data minimization. For a phone team, that means collecting the least information needed to route the request.

A call-screening table for the first queue

Start with the requests that can cause the most harm. The assistant should know the safe action before the first live call, and the manager should keep every final decision.

Use a pause, verify, route process

The assistant does not need to prove that a caller is a scammer. They need to notice a risky request and move it into a safer path. The process below keeps that path easy to remember during a loud or rushed call.

Scripts a Filipino assistant can say without sounding rude

Short words work best when a caller applies pressure. The assistant should not debate the claim or explain every company rule. A calm repeat is safer than a long answer that gives the caller more details.

CISA tells people to watch for urgent or emotional language and requests for personal or financial information. Those signs were written for phishing messages, but they also make a useful listening check on a call. A sign should trigger the safe process, not an instant claim that the caller is guilty.

What the manager must keep

A Philippines-based assistant can gather safe facts, end a risky call, and send a clean note. The manager keeps control of account recovery, payment changes, remote access, customer record edits, bank calls, public agency calls, and reports to law enforcement. This line protects the assistant from being pushed into a decision they cannot verify.

Give one person ownership of the scam-call queue each shift. If nobody owns it, odd calls sit in a shared inbox until the details are forgotten. The owner should check the claim through a saved contact, label the result, and tell the assistant what to do if the pattern appears again.

The FTC's 2024 data says government imposter scam losses reached 789 million dollars, up 171 million dollars from 2023. That is the third dated figure worth putting in manager training because authority claims can sound official. Your assistant should never use a number supplied by the incoming caller to verify that same caller.

Build the first training set

Use six sample calls: a real vendor update, a fake code request, a customer asking for a record change, an upset caller, an unknown software caller, and a leader asking for an urgent task. Let the assistant practice the stop line, note fields, and route for each one. Then compare the note with your written rule.

Score the call on facts, safety, tone, and next step. Do not score the assistant on whether they guessed the caller's intent correctly. The goal is to protect the business while giving real callers a clear path back.

Add the final script to your assistant onboarding checklist, and connect each risky request to the right call support service. Review a small call sample every week during the first month. Replace vague coaching such as "be careful" with one sentence the assistant can use on the next call.

Questions business owners ask