Complete practical guide
The customer-support book about the refund window that changed nine months ago
37 chapters and 68 worksheets on handling somebody else's support queue - why twenty tickets a day were sixty on Mondays, why eleven customers were quoted a policy that no longer existed, and why the business honoured all eleven.
Look inside — read the first chapter freeOne payment, USD. Yours permanently — no subscription.
What this guide is
Noor quoted an hourly rate for 'email support, about twenty tickets a day'. The figure came from a trial week, which was a quiet week - it always is, because that is when a client has time to arrange one. The real number was thirty-five on weekdays and sixty on Mondays, because a weekend accumulates and nobody mentions it. The knowledge base was fourteen months old and covered six of the twelve questions that actually arrived, which meant half the queue was a message to the founder and a wait. In month three, eleven customers were told a refund window that had been changed nine months earlier - the macro still said thirty days, nobody had dated it, and the business honoured all eleven because the customers had been told by the business. In month six a launch nobody mentioned tripled the queue for eight days. In month nine a reply that was accurate, correct on policy and entirely tone-deaf was screenshotted and reached the founder, who could not fault the facts and did not need to. In month twelve the client asked whether live chat could be added at the same hourly rate, which is how a channel arrives - as a forwarded message rather than as a request.
What you get out of it
Specifics, not promises.
- Why a trial week is always the wrong number, in four separate ways
- The coverage check on fifty real tickets - the most valuable hour in the trade
- Knowledge-base coverage: the number that decides your throughput, your holidays and your rate
- Why an hourly rate pays you less the better you get at this
- The clock that runs while you wait on the client, and how to stop it
- Six measurable things that make up somebody's voice - and why a description is useless
- Why the accurate reply is the one that gets screenshotted
- The escalation summary that can be answered from a phone in ninety seconds
- Why your best client is the most likely to bring it in-house, and what to offer before they do
- 148 AI prompts - and a large share exist to stop a confident wrong policy being sent in your client's name
Ideal for
People handling customer support for small businesses, founders, agencies, software companies and online retailers as a side hustle - retained email and ticket support, knowledge-base building and maintenance, overflow and peak cover, live chat, and help-desk setup. Particularly three groups: somebody whose ticket volume turned out to be double what they quoted for; somebody who has never asked what proportion of a queue they will actually be able to answer; and anybody who has told a customer something the business then had to honour.
- Anybody handling support for founders, small businesses, agencies or online retailers
- Somebody whose ticket volume turned out to be double what they quoted for
- Somebody who has never asked what proportion of a queue they can actually answer
- Anybody who has told a customer something the business then had to honour
What's inside
Format
- Digital download, delivered instantly after payment
- Formatted for letter paper — read on screen or print it
- Yours permanently, re-downloadable from your library any time
- Licensed for use in your own business
By the end you can
A reader finishes with a customer type and channel chosen on starting coverage, escalation speed, authority clarity, channel demands and volume shape rather than on industry; a coverage figure measured by them on fifty real tickets before any price exists, sorted four ways rather than estimated; a named escalation contact with a stated response window and a named alternative, treated as a pricing input rather than an administrative detail; written authority limits covering refunds, replacements, credits and what may be acknowledged, which convert a judgement under pressure into a lookup; a retainer structured as a covered window within a stated volume band, with an above-band rate applied automatically and each channel priced separately with its own window; a voice record of six measurable things extracted from ten sent replies including two refusals and an apology, corrected rather than approved, and re-checked monthly for drift; a nine-step shift procedure with the knowledge-base pass and triage before answering anything; an escalation log of five columns that produces the coverage figure, the average escalation wait, the documentation argument and the record of what they were told; entries written on the day the answer arrives rather than as a Friday batch; a service level stating measurement, hours, channels, clock and percentage, with the clock stopping while waiting on the client; a monthly report sent unasked containing the coverage figure including when it is poor, because it is the only visible artefact of invisible work; a five-check review before anything that says no; five random closed tickets re-read monthly; and revenue per support hour computed across all seven hour categories, which is where an arrangement that looked like a good hourly rate turns out to return half of it.
A complete working system for outsourced customer support - built on four rules covering the fact that every reply carries the client's name, goes to their customer, and becomes a commitment they must honour, while the customer must never learn you exist; the fact that you can only answer what has been written down, so anything undocumented is an escalation regardless of how obvious it looks, and inference at speed is the failure mode that ends arrangements; the fact that the queue arrives on somebody else's schedule, triples during a launch nobody mentioned, and accumulates while you are away, so a window is a promise about the bad Monday rather than the average one; and the fact that both default pricing structures reward the wrong thing, because an hourly rate punishes every improvement you make while a per-ticket rate bets on a mix set by their documentation - with revenue per support hour as the economic unit, tickets resolved per support hour as the leading indicator, knowledge-base coverage as the master variable, and four gates the trade cannot be run profitably without: a coverage check on fifty real tickets before any price exists, a named escalation contact with a stated response window, written authority limits agreed before the first shift, and a service-level clock that stops while waiting on the client.
Instant download · One payment · Keep it forever
Other guides in the library
AI-Powered Website Maintenance Plans
The website maintenance book that tells you what to refuse
$47.00
AI-Powered Short-Form Video Editing
The short-form editing book about the batch that got muted
$47.00
The AI-Powered Local SEO Services Side Hustle
Look after local businesses properly, and say no to the rest
$47.00