How It’s Done
Detailed and nested SOPs
SOP-0006 — Drafting Requested Emails
Customer Support Inbox Coordinator · Drafting Requested Emails · approved · Based on master 9
Revised from SOP-0005. Original stays intact until this draft is approved.
Human-approved SOP. Original evidence remains available.
Improve this SOP
Have a small correction? Create an editable revision from this version. For missing knowledge, use the focused Discovery questions further down. Neither path overwrites the approved copy until review.
Availability
Mark this approved SOP inactive if it should no longer appear as current guidance.
Drafting Requested Emails
Purpose: Cover the process for drafting, reviewing, editing, and finalizing customer emails requested informally by the boss.
Trigger: Boss requests an email informally in-person or via message
Procedure
How: For routine emails, use a template and tweak it. For sensitive emails (e.g., upset customer, threat to cancel, refund, billing dispute, legal matter, unfamiliar question), write from scratch or reference past emails for wording. Keep tone friendly and direct, acknowledge the issue, keep it short, and avoid defensive language or unapproved promises. Flag uncertain lines.
Decision: Determine whether an incoming email is routine vs. sensitive based on customer state, cancellations, refunds, billing disputes, legal matters, or unfamiliar questions.
Application / system: Outlook (to create draft)
Evidence: KNO-000004:E1, KNO-000004:E2, KNO-000004:E3, KNO-000004:E7
How: Save email as a draft in Outlook, then message boss or walk over in person if nearby. For sensitive drafts, point out flagged lines.
Application / system: Outlook
Evidence: KNO-000004:E4
How: Make edits in the same Outlook draft based on boss feedback (in person or via message). Check with boss on major changes before rewriting.
Application / system: Outlook
Evidence: KNO-000004:E5
How: Add an internal note summarizing the issue, what was told to the customer, that the boss sent the reply, and any promises made (like refunds or follow-up dates).
Application / system: Support system (internal note)
Evidence: KNO-000004:E6
Completion: Internal note added to the customer support thread after the boss sends the email.
Optional detailed sub-SOPs
Use only when a complex step needs a separate procedure. The new draft starts with what is already established; you can request a discovery follow-up for missing details.
No sub-SOPs needed yet.
Missing something?
Save a role-wide question. Investigate it later with any employee in the role. Unfinished questions do not block approval.
Evidence
View reviewed knowledge interview KNO-000004Sources link to the employee messages in each transcript.