Customer query handling

Questions to ask before setting escalation rules with a provider

Before hiring a virtual assistant for customer queries, ask these four questions about escalation rules. Hear what strong answers sound like and why vague ones.

When your virtual assistant or customer query handler will field requests on your behalf, you need clarity on when and how they escalate issues back to you. Escalation rules separate a seamless handover from chaos—the difference between a customer getting a same-day resolution and a critical issue buried in someone else's inbox. Before you sign on with a provider, sit down and ask the four questions below. Listen not just to what they say, but how they answer. Evasiveness or vagueness here will cost you.

What counts as an escalation in your eyes?

This is the foundation. Ask your prospective provider to walk you through three recent client scenarios—a customer complaint, a request outside standard scope, a time-sensitive query—and tell you which they'd escalate to you. A good answer is specific and shows they understand your business. For example, a property manager's assistant might say: "Any maintenance emergency or tenant threatening to break lease—those go straight to you. A rent query or viewing request I handle myself." An evasive answer sounds like: "Anything I'm not sure about," which is too broad and wastes your time.

Why it matters: if your provider escalates everything, you've gained nothing. If they escalate nothing and miss a crisis, you've lost control. The sweet spot is when they know your boundaries before they start.

How fast will you hear about it?

Ask what their escalation notification looks like. Do they message you, email you, call you? How long between receiving the query and flagging it to you? A strong answer includes a timeframe: "Anything urgent—complaint, safety issue, legal mention—I send you a WhatsApp and email within 15 minutes, with the full customer message in both." A weak answer is: "I'll let you know when I can," or "It depends." It always depends on something; the question is whether they've thought through what.

Why it matters: you need to know when you'll be forced into your email, not just hope it arrives sometime today. Slow escalation defeats the entire point of outsourcing; you're still firefighting, just with lag.

What information do you include when you escalate?

Don't assume they'll copy-paste the customer's original message. Ask them to give you an example of an escalation they'd send. A quality provider includes the customer's name, the exact query, what they've already said or tried, and a brief note on urgency or context. For instance: "Sarah Jones (0781234567, email) asked about a refund on order #4521. I checked our returns policy; it's outside the 30-day window. Flagging because she sounds upset and mentions a social media review. What's your call?" Contrast that with: "Customer wants a refund. FYI."

Why it matters: poor escalation data means you're starting from scratch every time, defeating the efficiency you hired them for. Good escalation includes enough detail that you can make a decision without needing to ask five follow-up questions.

Can you give me examples of issues you've left unescalated that you now wish you'd flagged?

This one catches experience. A genuine provider will admit to a miss—a complaint they downplayed, a request they misunderstood, a tone they misjudged. They'll describe what they learned. If they insist they've never made a judgment call they regretted, they're either overconfident or underselling how often they actually think. A strong answer sounds like: "I once reassured a customer about a shipping delay without realising it had been sitting in our mailroom for two weeks. Now I check status on anything mentioning time-sensitivity, even if I think it's fine." That tells you they learn.

Why it matters: you're hiring for judgment, not perfection. A provider who admits to mistakes and adjusts is far safer than one who claims infallibility.

Lock it in writing

Once you've had these conversations, ask them to send you an escalation policy in writing—bullet points are fine, not a formal document. It doesn't need to be elaborate; it just needs to be specific to you and referenced when disputes arise. A provider willing to do this has nothing to hide. One who resists is signalling that they expect the rules to be flexible or unclear, which is how critical issues slip through.

When you're ready to hire someone to handle customer queries, look for a provider on Strove who walks you through their approach without hesitation.

Common questions

What should I do if a provider refuses to put escalation rules in writing?: That's a red flag. A provider willing to handle your queries should have no issue documenting when and how they'll flag issues to you. If they resist, it suggests they want flexibility to ignore the rules or aren't confident enough in their process. Look for someone who treats escalation as a core part of the job, not an afterthought.
How detailed should an escalation policy be?: Specific enough that you and your provider agree on what triggers it. You don't need a 20-page manual; bullet points covering your most likely scenarios (complaints, refund requests, urgent bookings, safety issues) are enough. The goal is preventing avoidable surprises, not creating bureaucracy.
What if my provider escalates too often and I'm overwhelmed?: Revisit the rules with them. If they're flagging routine queries, your escalation criteria are too broad or they haven't understood your business yet. Ask them to show you three examples they escalated last week and discuss which ones you'd actually want to hear about. Adjust from there.
Should escalation rules differ by query type or customer?: Yes. A complaint from a repeat customer might escalate immediately, while a pricing question from a first-timer doesn't. A safety concern always escalates; a scheduling conflict usually doesn't. Tell your provider upfront which query types matter most and what makes a customer worth your direct attention.

Find a verified provider on Strove

Compare vetted customer query handling providers, check their credentials, and book or request a quote — all in one place.

Find a Business

More on Customer query handling

What counts as an escalation in your eyes?

How fast will you hear about it?

What information do you include when you escalate?

Can you give me examples of issues you've left unescalated that you now wish you'd flagged?

Why it matters: you're hiring for judgment, not perfection. A provider who admits to mistakes and adjusts is far safer than one who claims infallibility.

Lock it in writing

When you're ready to hire someone to handle customer queries, look for a provider on Strove who walks you through their approach without hesitation.

Common questions

What should I do if a provider refuses to put escalation rules in writing?

That's a red flag. A provider willing to handle your queries should have no issue documenting when and how they'll flag issues to you. If they resist, it suggests they want flexibility to ignore the rules or aren't confident enough in their process. Look for someone who treats escalation as a core part of the job, not an afterthought.

How detailed should an escalation policy be?

Specific enough that you and your provider agree on what triggers it. You don't need a 20-page manual; bullet points covering your most likely scenarios (complaints, refund requests, urgent bookings, safety issues) are enough. The goal is preventing avoidable surprises, not creating bureaucracy.

What if my provider escalates too often and I'm overwhelmed?

Revisit the rules with them. If they're flagging routine queries, your escalation criteria are too broad or they haven't understood your business yet. Ask them to show you three examples they escalated last week and discuss which ones you'd actually want to hear about. Adjust from there.

Should escalation rules differ by query type or customer?

Yes. A complaint from a repeat customer might escalate immediately, while a pricing question from a first-timer doesn't. A safety concern always escalates; a scheduling conflict usually doesn't. Tell your provider upfront which query types matter most and what makes a customer worth your direct attention.