How do you choose a remote operations desk?

Who is actually on shift

The first question, and the one that filters hardest. Ask for names, roles and the shift structure. Ask whether the same people will be on your account in six months, and how you would know if that changed.

Anonymity is the tell. If a provider will not say who works your account, it is usually because the answer changes weekly, or because the work is being resold to someone they have never met either.

The response standard, and what backs it

Almost everyone advertises a response time. Very few define it. Push on the definition until it is boring: does the clock measure a first human reply or a resolution, which hours does it cover, which channels count, and what happens when it is missed?

A standard with no consequence attached is a marketing number. A standard with published exclusions is usually a real one, because nobody writes exclusions for a promise they are not being held to.

• First response or full resolution?
• Which hours, and in whose timezone?
• Which channels are covered, and which are not?
• What is the make-good when it is missed?

Where their authority stops

Coverage and authority are different purchases and it is worth being precise about which one you are making. You want the night covered. You almost certainly do not want someone else deciding refunds, paying your vendors, or changing your pricing.

Ask for the boundary as a list. A provider who has thought about this will have one ready, because it is an operating document rather than a sales answer.

How the people are paid and scheduled

This question feels intrusive and it is the most predictive one on the list. Retention is the product: the operator who knows your building in month nine is worth more than any script, and nothing is more expensive than re-teaching your operation every quarter.

Clear hourly rates and a published schedule tend to produce people who stay. Per-ticket piecework and unpredictable hours tend to produce churn, and you pay for that churn in mistakes on your listings.

How you leave

Check the exit before you check anything else, and be suspicious of any answer that involves a long minimum term.

You want a short notice period, no exit fee, and a revocation you control entirely: remove their users, remove co-host access, rotate the codes they held. If unwinding the relationship requires their cooperation, they have more of your operation than they should.

• Notice period, in days, and any fee attached
• Whether any minimum term applies
• Exactly which access you revoke, and whether you can do it alone
• What happens to the documentation they built on your units

Three answers that should end the conversation

Some responses are disqualifying regardless of price.

• They ask for your platform account password rather than co-host access
• They take a percentage of your revenue while calling themselves support
• They will not tell you who is on shift, or the answer changes each time you ask

Frequently asked questions