Most service businesses lose money in customer service the same way. Not through bad hires. Through undocumented decisions. A CSR gets a refund request, pings the founder on Slack, waits 40 minutes for an answer, and the customer waits with them. Multiply that by 15 tickets a day and you have a support function that runs on interruption instead of process.
The fix is boring and it works. Write down how you handle the 9 situations that make up almost every ticket you will ever receive. Once those are documented, a new CSR can be productive in a week instead of a quarter, and you stop being the escalation point for every weird question.
Here are the 9 customer service SOPs every service business should have written down before they hire their next support person.
1. The First Response SOP
This is the one that quietly kills NPS. A customer emails at 9:12 AM. When does someone reply? What do they say if the answer will take longer than the reply?
Your first response SOP should define three things. The response time target (we recommend under 2 hours during business hours), the required elements of that first reply (acknowledgment, expected resolution window, ticket number), and what to do if you cannot solve it in that first touch.
Write a template. Something like: "Hi [name], I have your request and I'm looking into it now. I'll have an answer for you by [specific time, not 'soon']. If anything urgent comes up in the meantime, reply to this thread."
That template alone will change how customers feel about your business. Silence is what makes people angry. Not delays.
2. The Refund and Credit Policy SOP
This is the SOP founders resist writing because every situation feels unique. It isn't. About 90% of refund requests fall into four buckets: work not delivered, work delivered late, work delivered poorly, or buyer's remorse.
Your refund SOP should tell a CSR exactly what they can approve without asking, what needs a manager, and what needs you. A workable structure:
- Under $200 or under 10% of the invoice: CSR can approve if the customer has a valid reason in one of the four buckets.
- $200 to $1,000: manager approval, same day.
- Above $1,000 or full contract cancellation: founder approval.
The important part is not the numbers. The important part is that a CSR knows the boundary and does not have to ask. Every time they ask, you pay twice. Once in your attention and once in customer wait time.
3. The Escalation Tree SOP
An escalation tree answers one question: when this ticket is above my head, who exactly gets it next, and what do I hand them?
A clean tree has three levels. Tier 1 handles standard requests. Tier 2 handles account-specific issues, billing disputes, and quality complaints. Tier 3 is the founder or ops lead and handles legal threats, churn risk on accounts above a certain size, and press or public complaints.
The handoff format matters as much as the tree. When a ticket escalates, the person receiving it should get a one-paragraph summary at the top: what the customer wants, what has already been tried, what the CSR recommends. Not a forwarded email chain to scroll through.
4. The Response Template Library SOP
If your CSRs are writing every reply from scratch, you are burning hours and getting inconsistent voice. A support SOP template library covers your top 20 to 30 recurring situations.
Start by pulling your last 200 tickets and grouping them. You will find that most fall into a handful of shapes. Onboarding questions. Status updates. Login issues. Scope clarifications. Late delivery apologies. Invoice questions.
Write one template per shape. Keep the tone human, not robotic. The template is a starting point, not a script. Train CSRs to personalize the first line and the closing, and to leave the middle mostly alone.
A good template library cuts average handle time by 30 to 50% within a month. It also makes your quality control ten times easier because you know what "correct" looks like.
5. The Edge Case SOP
Every business has weird recurring situations that do not fit the main workflow. Customer wants to pause service for three months. Customer wants to transfer their contract to a business they just acquired. Customer's card keeps failing but they insist the card works. Customer wants a W-9 at midnight on December 31.
These are edge cases only the first time. By the tenth time, they are a category, and they deserve a documented procedure.
Run a monthly review of any ticket that took more than three internal messages to resolve. Those are your edge cases. Write them up. Add them to the CSR playbook. Over a year, you will have documented most of the strange corners of your business, and new hires will handle situations that used to require a founder call.
6. The Angry Customer SOP
This is separate from the escalation tree because tone matters as much as routing. An angry customer needs a specific sequence: acknowledge the frustration by name, take responsibility for the part you own, offer a concrete next step with a time attached, and do not defend.
Write out what CSRs should not do. Do not explain policy in the first reply. Do not use phrases like "per our terms." Do not ask them to calm down. Do not promise things you cannot deliver to make the ticket go away.
Give them one sentence they can always fall back on: "I hear you, and I want to make this right. Give me until [time] to come back with a real answer." That sentence buys time and lowers temperature. Both matter.
Also define when to move a conversation off email. A single phone call at the right moment saves accounts. A CSR should know they are allowed to offer one, and how to schedule it.
7. The Handoff to Delivery SOP
Half of support tickets are not really support. They are the delivery team missing something and the customer noticing. Your customer service procedures should include a clean handoff protocol back to the team doing the work.
What information does the delivery team need to fix it? Usually four things: the customer name, the specific deliverable in question, what the customer expected versus what they got, and the deadline for a fix. If a CSR sends anything less, the delivery team asks the customer directly, which makes the customer feel like nobody is talking to each other.
Define a single channel for these handoffs. Not DMs. A shared ticket queue or a project management column. If a delivery handoff lives in someone's inbox, it will be forgotten by Thursday.
8. The Retention and Save SOP
When a customer says "I want to cancel," what happens? In most service businesses, the answer is: whoever gets the email does whatever feels right that day. Sometimes they offer a discount. Sometimes they process the cancellation immediately. Sometimes they escalate to the founder who is on a plane.
A save SOP takes the guesswork out. It should specify:
- The required first response, which is never to process the cancellation immediately.
- The two or three questions you always ask (what changed, what would need to be true for you to stay, is this a timing issue or a fit issue).
- The concessions a CSR is authorized to offer without approval (a pause, a month at reduced scope, a switch to a different account manager).
- The concessions that require approval and who to route to.
Track your save rate. If you do not have a save SOP, it is probably under 10%. With one, you can get to 25 to 40% depending on the category.
9. The Weekly Loop-Back SOP
This is the SOP that keeps all the other SOPs from going stale. Once a week, your support lead should spend 30 minutes doing four things: review the five longest-open tickets, review any ticket that escalated to a founder, note any new pattern that appeared more than twice, and update one document.
Update one document. Not all of them. If you try to overhaul the whole system every week, nothing gets updated. Pick the SOP that needs it most and improve it.
This is how your customer service SOP library becomes a living thing instead of a Google Doc graveyard. In a year, you will have iterated 50 times on your playbook, and your support quality will be unrecognizable from where you started.
How to actually roll this out
You do not need all nine documents written before Monday. If you have none of them right now, here is a realistic order.
Week one, write the first response SOP and the template library for your top 10 ticket shapes. Those two together will change your metrics faster than anything else.
Week two, write the refund policy and the escalation tree. These stop you from being interrupted.
Week three, write the angry customer SOP and the save SOP. These protect revenue.
Week four, write the delivery handoff, edge case, and loop-back procedures. These make the system compound.
Each document should be one page. Two pages if it truly needs it. If your refund SOP is six pages, no CSR will read it, and you have not actually documented anything. You have written a legal document that lives in a folder.
The point of a CSR playbook is not to cover every situation. It is to cover the 80% that repeat, so your team has the time and energy to handle the 20% that are genuinely new. Get the boring 80% written down, and support stops being the thing that eats your calendar.