How quickly should you answer support requests?

Membergate Support - November 17, 2023

When a member sends a support request, the clock starts in their head straight away. They don't know whether you're a team of ten or one person answering between other jobs. All they know is that something isn't working, they're paying for access, and they've asked for help. How long they wait, and whether that wait matches what they expected, shapes how they feel about your whole membership.

Most owners never decide on a response time. They answer when they can, which means fast on quiet days and slow on busy ones. That inconsistency is the real problem. A clear commitment you can keep every single time does more for member trust than occasional heroic speed. Here's how to choose that commitment, publish it and live up to it.

First response and resolution are different promises

There are two clocks in any support conversation. The first-response time is how long until a person replies. The resolution time is how long until the problem is actually fixed. Members care about both, but you can only fully control the first. A tricky playback bug might take days to fix, yet you can still acknowledge it within hours and say what happens next.

So make your public promise about first response, and handle resolution with honest updates. “We reply within one working day” is a promise you can keep. “We fix every problem within one working day” is not. And an automatic acknowledgment doesn't count; the clock stops only when a person replies.

Find out what you do now

First, look back over a month or two of requests, noting when each arrived and when you first replied. Then look for patterns:

What's your typical first-response time, and what's your slowest?
When do requests pile up, such as right after a newsletter or on the day renewals are charged?
How many requests are urgent access or billing problems, and how many could comfortably wait?
When were you slowest, and why: travel, a launch, illness, or simply a full week?

Your slowest honest week tells you more than your average. Your promise has to survive that week.

Set different speeds for different problems

Not every request deserves the same urgency. A member who can't log in is paying for nothing until you help. A member suggesting a new course topic is happy to wait. Sorting requests into two or three levels lets you be fast where it matters without being chained to the inbox:

Urgent: the member can't access what they paid for, was charged incorrectly, or something is broken for many members at once. Aim to respond the same working day.
Standard: how-to questions, account changes, a single video that won't play. Respond within one working day.
Low: suggestions, general feedback, partnership inquiries. Respond within a few working days.

Choose a promise you can keep every time

A few questions help you find the right promise:

Who are your members? Professionals using your templates on client work may need a quicker answer than hobbyists who log in when they have a free evening.
What do you charge? A high-priced program with coaching carries higher expectations than an inexpensive content library.
Who covers when you're away? If nobody does, your promise has to allow for the days you're unavailable, or you need a plan for them.
Do you work weekends? If not, promise in “working days” and say what those are. Members accept boundaries they know about.

It's far better to promise one working day and usually reply within a few hours than to promise two hours and regularly miss it. Beating a modest promise feels like great service. Missing an ambitious one feels like neglect, even when the actual wait was shorter.

A worked example: one owner's support promise

Priya runs Kiln Notes, a hypothetical membership for hobby potters that shares glaze recipes, firing guides and a monthly live critique. She works on the business four days a week and teaches in-person classes on the fifth. After reviewing two months of requests, she sees that most arrive the day after her newsletter goes out, and that her slowest replies happen on teaching days. She writes this for her contact page:

How we handle support

Every message is answered by a real person, four working days a week. You'll get a reply within one working day, and usually much sooner.

If you can't log in or were charged incorrectly, put “Access” or “Billing” in your subject line and we'll deal with it first, the same working day if you reach us before mid-afternoon.

Messages sent on non-working days are answered first thing on the next working day.

She also writes a holding reply for problems she can't fix straight away:

Hi Sam, thanks for letting me know the firing chart download is failing. I can see the problem on my side too, so it isn't anything you've done. I'm working on a fix and will update you by the end of tomorrow either way. In the meantime, I've attached the chart to this email so you're not held up.

Publish it, then protect it

A promise only builds trust if members can see it. Put your response time on the contact page, in your automatic acknowledgment, in the help area and in the welcome email. If you've followed the approach in setting up customer support for your membership site, your support front door already appears in those places, so add a line beside it.

Then protect the promise with a few habits:

Check the support inbox at fixed times each working day rather than constantly.
Sort by urgency first and age second.
When you're going to be away, say so in the acknowledgment and adjust the promise temporarily, or arrange cover.
Answer thoroughly the first time, as described in writing support replies that solve problems the first time, so a fast reply doesn't turn into a slow thread.

If you miss your promise, apologize in one sentence, answer the question, and later ask whether the promise needs adjusting.

Your next steps

Log arrival and first-reply times for your recent support requests.
Note your slowest week and the reason for it.
Define two or three urgency levels with a target for each.
Write a short support promise in plain language, using working days.
Add it to your contact page, acknowledgment email, help area and welcome email.
Write one holding reply for problems that take longer to fix.
Review your actual response times monthly and adjust the promise if you're missing it.