The 5 AI Tools Every VA Should Know Cold, and How to Test for It

I hired a VA once off her resume alone.

She’d worked with three agencies before us. Her resume said “AI-fluent, tool-savvy, automation-ready” in almost those exact words. I didn’t ask her to show me anything; I figured three years of placements spoke for themselves. I put her on a client account that ran on a CRM, a Notion workspace, and a handful of Zaps stitching the two together.

Three weeks later the client called, and it wasn’t good news. Leads were sitting in the wrong pipeline stage. A Zap had failed quietly, and nobody caught it for days. When I sat her down and asked her to walk me through what had broken, she froze. She could open the tools. She couldn’t fix them, and she couldn’t tell me why they’d failed in the first place.

That’s the day I stopped hiring off resumes and started hiring off tests.

That client stayed with us, but it cost me something to keep them. It cost the VA her placement, too, and I’ve thought about that more than once. She wasn’t dishonest. She’d used every one of those tools before, just never past the surface. Nobody had ever asked her to go deeper, so she never had to find out where her own limits were until it mattered.

What Stayed with Me

I’ve been doing this for fifteen years, and here’s what I’ve learned: a resume claim costs nothing to write. “AI-fluent” and “automation-ready” have turned into filler words, the way “team player” used to be. They don’t tell you what happens when a workflow breaks, and the founder isn’t around to bail someone out.

I’ve read hundreds of these resumes by now, and they all start to sound the same after a while. The words that are supposed to signal skill have become the words that signal nothing at all, because everyone learned to use them.

Resume Genius’s 2026 Job Seeker Insights Report confirms it isn’t just my read: AI fluency has become one of the most commonly exaggerated skills on resumes across the board, not just in staffing.

Source: Resume Genius, 2026 Job Seeker Insights Report

A credential tells you someone showed up somewhere. It doesn’t test VA AI tool knowledge, and it doesn’t tell you they can operate once they’re in the seat.

The Real Problem

“Knows AI tools” is a meaningless line on a resume until you define what fluency actually looks like, tool by tool. Skill is the true currency here, not the agency someone came from, not the phrase on their LinkedIn, but what they can actually do when something breaks and nobody’s watching.

That gap matters more this year than it did two years ago. VA Masters’ 2026 industry data shows AI-tool adoption is now near-universal among working virtual assistants, which means resume claims of fluency are more common, and less differentiated, than they used to be.

Source: VA Masters, Virtual Assistant Industry Statistics 2026

This is the same principle behind every hire we make at Simpalm: hire the fluency, don’t try to become it yourself, and don’t take someone’s word for the fluency either. This is exactly why I built a short, specific list of the AI tools a virtual assistant must know cold before I’ll call them fluent, and a set of AI-ready virtual assistant interview questions, one per tool, that a resume claim can’t fake.

ChatGPT / Claude

Fluency isn’t “I use ChatGPT for emails.” Real virtual assistant ChatGPT skills mean knowing how to prompt for a specific outcome, editing what comes back instead of forwarding it wholesale, and knowing exactly when not to trust the output at all.

This tool carries the highest stakes of the five, because the mistakes it produces sound confident even when they’re wrong. Anyone can generate a paragraph. Not everyone can tell you why they’d hold it back.

Notion

Anyone can make a Notion page. Fewer people can build a database a team actually depends on. Fluency means treating Notion as an operating system, not a scratchpad.

The tell here is whether someone talks about the workspace as something they built, or something they just filled in.

HubSpot or an Equivalent CRM

A CRM is only as good as the hygiene behind it. Fluency is pipeline discipline: knowing when a deal should move stages, catching stale or duplicate records, building follow-up sequences that don’t need a founder’s nudge.

A messy pipeline doesn’t just cost time. It costs deals that never get followed up on, and a founder rarely notices until a client asks why a lead went cold.

Zapier / Make

This is where resumes fall apart fastest under questioning. Building a Zap is the easy part. Monitoring it and fixing it without calling the founder is the actual skill.

A broken automation doesn’t send an alert. It just quietly stops doing the job, and the first sign is usually a client asking why nothing’s happened in days.

Google Workspace and Scheduling Tools

This one gets skipped because it feels too basic to test. It isn’t. Every VA touches Docs, Sheets, and Calendar daily, and it’s the foundation everything else sits on.

hireva.org’s 2026 hiring-trends analysis points to the same shift across the board: ChatGPT, Zapier, Make, and Notion AI are actively reshaping what founders expect a VA to already know on day one.

Source: hireva.org, Virtual Assistant Hiring Trends in the US for 2026

Takeaway

A founder who tests real fluency once will never trust a resume claim again. It’s rare for someone to lie, and most people just don’t know the difference between using a tool and owning it. The test shows you which one you’re actually hiring.

I still think about that VA sometimes. She wasn’t a bad hire in the way people usually mean it. She was a hire nobody had actually tested, and that gap was on the process, not on her. It’s the reason I don’t skip this step anymore, no matter how strong the resume reads.

If you’re figuring out how to hire an AI-fluent VA, this is the answer: stop asking, start testing. I built our staffing process around exactly that; every candidate gets tested against the tools the role actually needs, not just asked to list them on a form.