Workflow fit
Can they manage a queue against a reply-time target, use your macros, and keep tickets moving without daily direction?

Support is judged on tone and resolution, not ticket count. Before candidates reach you, we look at how they write under pressure, follow a refund policy, and decide what to escalate.
Can they manage a queue against a reply-time target, use your macros, and keep tickets moving without daily direction?
Gorgias, Zendesk, Freshdesk, Intercom, Help Scout, and the store or account system behind them. Learning your macros quickly matters most.
Replies that sound like your brand, not a script, and clear notes on the ticket so the next person is not starting over.
They resolve routine tickets and issue refunds inside your rules. Anything outside the policy is escalated with the context attached.
You set the priorities, the working hours, and the access. We handle recruiting, vetting, and the employment side, so one dedicated assistant can own the work from the first week.



You define the refund limits, the response-time targets, the escalation rules, and the tone your customers should hear. Your assistant answers inside those boundaries and brings the exceptions to you.
The same person works your tickets, email, and chat every day, learns your products, and builds the macros and help-center answers your customers keep needing.
Stellar Staff screens for written clarity, patience under pressure, and judgment on when to escalate, then manages payroll, HR, and support after the placement. The search takes 5 to 10 business days.
Support usually breaks down on exceptions. Agreeing on what a resolved ticket looks like, what can be refunded without asking, how quickly replies should go out, and what gets escalated keeps the queue predictable.
A cleared queue means every ticket is answered within your target time, resolved or handed off with notes, and nothing is left unread overnight.
Answering, refunding inside your limits, and updating orders go ahead without asking. Anything above the limit or outside policy comes to you.
Tickets are handled throughout the day, the backlog is cleared before close, and a weekly summary shows what customers kept asking about.
Chargebacks, safety issues, public complaints, and customers asking for a manager are routed to you with the full history attached.
The first month moves from learning your products and policies, to owning the routine queue, to holding a steady reply time with escalations arriving in one place.
Your help desk, your policies, your product catalog, and the answers your team already uses for the most common questions.
The daily queue moves off your team, and response times stop depending on who happens to be free.
The queue is cleared every day rather than every few days, and repeat issues are reported as patterns instead of being treated as isolated tickets.
Your VA works the ticket queue oldest to newest, on a schedule, against a first-reply target you set and can measure. Answerable tickets get answered. Incomplete tickets get the missing information gathered before anything is escalated. Backlogs usually grow when support belongs to everyone in theory but nobody in practice.
A chat window and an Instagram DM are judged quickly. Your VA covers the window you choose and answers chat, DMs, and comment questions using the same approved information as email, so customers get a consistent experience across channels. Conversations about content rather than customer support belong with a social media virtual assistant.
"Where is my order?" "Can I still change the address?" "Why does tracking say returned?" In most store queues, a small number of questions make up a large share of the volume. Your VA checks the carrier, fulfillment tool, and store admin to give customers a real status instead of a generic link, and flags recurring patterns when the same issue keeps generating tickets. If most of your operation runs through the store, the wider role is covered on our ecommerce virtual assistants page.
You define the policy: what gets refunded, up to what amount, and what counts as an exception. Your VA applies those rules consistently, processes requests within the approved threshold, and sends only the judgment calls to you. That keeps refund decisions consistent without pushing every routine case into your inbox.
Bugs go to engineering with reproduction steps and the account ID attached. Billing disputes go to finance with the invoice. Legal, medical, and safety-related questions are routed to the appropriate person without interpretation. A good support agent is valuable not only for what they can resolve, but also for knowing what should be escalated.
A relatively small set of saved answers can cover much of a support queue, but only if someone updates them when the policy changes. Your VA maintains the macro library and tracks which help center articles customers visit before they still open a ticket, which helps show where the documentation needs improvement.
Beyond answering tickets, your VA tracks which issues repeat, which policies create the most contacts, and which pages customers visit right before they write in. That summary goes to you monthly. Support is often the first place a product or process problem shows up, and it is worth reading rather than only clearing.
Customer service outsourcing companies often use shared agents working across several brands. This model is different: one named agent assigned to your business and working inside your help desk. Written support and phone support are also different jobs. If most of your volume arrives by phone, a call center virtual assistant is usually the better fit. Every role is listed on our virtual assistant services page.
The difference is not a faster first reply. It is whether a customer's problem is finished or just acknowledged, and whether anyone owns the queue when the day gets busy.