Customer SupportSetupAI-generated

SOP Writer

Draft a support standard-operating-procedure from a topic and audience

What it is

Draft a support standard-operating-procedure from a topic and audience

Produce a complete, stand-alone support SOP from a topic description and audience level. Covers purpose, scope, prerequisites, numbered steps, exception handling, and related resources. Marks any detail that needs policy verification before publishing.

What you'll get

Custom instructionsCompiled from your answers, editable before you export.

SOP templateA fillable SOP skeleton with section labels, formatting conventions, and example steps. Claude uses this as the structural starting point for every SOP it drafts.

Export bundle for Claude ProjectsCopy-paste blocks with a guided walkthrough.

Try it on

Write a refund processing SOP for new agentsscenario · built in

Claude should produce a complete SOP with all six sections. The procedure steps should be granular enough for a first-week agent, including the Stripe system step with a [Requires: Stripe access] note. The exception handling section should cover refunds over $200 and requests outside the 30-day window. It should not fabricate Stripe UI details it does not know.

Write a ticket triage SOP for experienced agentsscenario · built in

Claude should produce a triage SOP written for experienced agents — concise, with a clear priority classification table, the four SLA targets, and numbered triage steps. The exception section should cover ambiguous cases (e.g., when a ticket could be P1 or P2) and give a concrete decision rule rather than "use your judgment."

Compiled preview

You are a support operations writer at {{companyName}} creating a standard operating procedure (SOP). SOP topic: {{sopTopic}}. Audience: {{audience}}. Calibrate assumed knowledge and level of detail to this audience — new agents need every step spelled out; experienced agents need precision and brevity over hand-holding. {{#if approvalRequired}} This SOP requires manager or compliance sign-off before publication. End the document with an "Approval" section containing fields for: approver name, role, date, and signature line. {{/if}} Structure every SOP in this order: 1. Purpose — one sentence stating why this SOP exists. 2. Scope — who this applies to and what it covers. 3. Prerequisites …