> ## Documentation Index
> Fetch the complete documentation index at: https://www.seilers.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a Customer Support SOP for Consistent Service

> Build a customer support SOP in Seilers covering ticket triage, escalation paths, and response templates so every rep handles customer issues consistently.

Customers don't care whether their ticket was handled by your most experienced rep or your newest hire — they expect the same quality of service every time. When your support process lives in tribal knowledge rather than documented steps, quality varies, SLAs get missed, and customer trust erodes. A Seilers customer support SOP gives your entire team a shared process to follow: how to categorize a ticket, when to escalate, what to say, and how to confirm the issue is actually resolved. When every rep works from the same SOP, your service becomes reliable instead of just occasionally excellent.

## What to Include

A complete customer support SOP covers the full ticket lifecycle from first contact to confirmed resolution:

<Accordion title="Ticket Intake and Categorization">
  Define how tickets arrive (email, chat, phone, portal), how they are logged in your ticketing system, and the standard fields that must be filled in at intake — account name, product area, issue description, and reproduction steps. Consistent intake data makes every downstream step faster.
</Accordion>

<Accordion title="Priority Triage Criteria (P1 / P2 / P3)">
  Define your priority levels clearly so any rep can triage any ticket without guessing:

  * **P1 — Critical:** Service is fully down or a security incident is suspected. Immediate response required.
  * **P2 — High:** Core functionality is degraded or a workaround is unavailable. Response within 4 hours.
  * **P3 — Normal:** Non-blocking issue or question with an available workaround. Response within 1 business day.
</Accordion>

<Accordion title="Response Time SLAs">
  Document your committed response time SLAs for each priority level and whether those SLAs differ by plan tier. Include guidance on what counts as a "response" — acknowledgment alone versus a substantive update — and how to communicate delays proactively.
</Accordion>

<Accordion title="Escalation Path">
  Specify the exact conditions that trigger an escalation, who to notify at each level, and how to escalate (tag in ticketing tool, Slack message to on-call, phone call for P1s). Avoid vague guidance like "escalate if needed" — instead, define the precise criteria.
</Accordion>

<Accordion title="Standard Response Templates">
  A library of approved response templates for your most common scenarios: initial acknowledgment, request for more information, workaround available, escalation notification, resolution confirmation, and follow-up CSAT request. Templates speed up responses and keep tone consistent.
</Accordion>

<Accordion title="Resolution and Closure Steps">
  The steps required before a ticket can be closed — confirmation that the fix works in the customer's environment, internal notes documenting the root cause and solution, any follow-up tasks logged, and the ticket status updated to resolved.
</Accordion>

<Accordion title="Customer Satisfaction Follow-Up">
  How and when you send a CSAT survey, who monitors the responses, and what the process is for following up on low scores. Include thresholds that trigger a personal outreach rather than an automated survey.
</Accordion>

## Building It in Seilers

<Steps>
  <Step title="Create a new SOP titled 'Customer Support Process'">
    In Seilers, go to **SOPs → New SOP** and name it `Customer Support Process`. Choose the **Support** category so it's easy to find. Add a one-paragraph description summarizing what the SOP covers and who it applies to.
  </Step>

  <Step title="Add a step for each stage of the support workflow">
    Create individual steps in the SOP for: Intake, Triage, Initial Response, Investigation, Escalation (if applicable), Resolution, Closure, and Follow-Up. Keep each step focused — one action or decision per step makes the SOP easy to follow under pressure.
  </Step>

  <Step title="Embed checklists for triage and escalation decisions">
    Inside the Triage step and the Escalation step, use Seilers' **Checklist** feature to add the priority criteria and escalation conditions as checkable items. Reps can work through the checklist in real time rather than trying to recall criteria from memory.
  </Step>

  <Step title="Assign a Support Lead as owner">
    Use **Assign Owner** to tag your Support Lead or Head of Support as the SOP owner. The owner is responsible for reviewing the SOP when SLAs change, when new ticket categories emerge, or when a support incident reveals a gap in the process.
  </Step>

  <Step title="Set a quarterly review date">
    Go to **SOP Settings → Review Reminders** and set a quarterly review date. Support processes evolve with your product — new features create new ticket types, and your escalation contacts change as your team grows. A quarterly review keeps the SOP accurate.
  </Step>
</Steps>

## Linking to Your Playbook

A support SOP is most powerful when it's embedded in the broader context of your customer success operation. In Seilers, you can link this SOP inside a **Customer Success Playbook** that covers the full post-sale journey — onboarding, ongoing health monitoring, renewal, and escalation.

To embed the SOP in a playbook:

1. Open or create your Customer Success Playbook.
2. Navigate to the **Support and Escalation** section of the playbook.
3. Click **Link SOP** and select your `Customer Support Process` SOP.
4. The SOP appears inline — team members can open and complete it without leaving the playbook.

This structure means new customer success managers and support reps find the SOP exactly where they expect it, nested inside the process they're already following.

<Tip>
  Use **Decision steps** in Seilers to build escalation branching directly into your SOP. For example: *"If P1: immediately notify the on-call engineer via PagerDuty and post in #incidents. If P2: respond to the customer within 4 hours and tag the senior support rep in the ticket. If P3: respond within 1 business day and assign to the next available rep."* Decision steps make the right action obvious at the exact moment the rep needs to choose.
</Tip>

<CardGroup cols={2}>
  <Card title="Incident Response SOP" icon="triangle-exclamation" href="/use-cases/incident-response-sop">
    Handle outages and critical incidents with a documented, tested response process.
  </Card>

  <Card title="Hiring Playbook" icon="briefcase" href="/use-cases/hiring-playbook">
    Standardize how you hire the support reps who will use this SOP every day.
  </Card>
</CardGroup>