How It’s Done
Reviewed discovery evidence
KNO-000004 — Human evidence review
Status: approved · Source: KNO-de8562c8769b405da21155332fa236bc
Approving this transcript certifies the evidence is ready to draft from; it does NOT approve an SOP or replace the master map.
Original employee interview
Agent — Agent
Hello! I'm here to help document the details for the "Drafting Requested Emails" operation. Based on our high-level process map, we know you start when your boss informally requests an email, gather history, draft the response in Outlook, and send it back for review and sending.
To dive into the specific decision criteria, let's start with the first Bot 2 question: What specific criteria or triggers do you use to determine whether an incoming requested email is routine versus sensitive or unusual?
E1 — Employee
I look for a few things. If the customer is upset or threatening to cancel, I treat it as sensitive. Same if it involves a refund, a billing dispute, or anything legal. If it’s something I haven’t seen before and I’m not sure how to answer, I also bring it to my boss. Basic questions like order status or how to do something are routine, and I just reply.
Agent — Agent
That's really clear. Once you've identified an email as sensitive or unusual and decide to draft a response, how do you go about selecting or customizing a template for it?
E2 — Employee
For sensitive ones, I usually don’t start from a template because they tend to need a more personal touch. I’ll write it from scratch, and sometimes I’ll look at a similar email we sent before to borrow wording or see how my boss handled it. Either way, he reviews it before anything goes out.
Agent — Agent
Got it. When you are writing these drafts, what specific guidelines or tone expectations do you keep in mind to make sure it matches what your boss expects?
E3 — Employee
I keep it friendly but direct, the way my boss normally writes. I start by acknowledging the customer’s issue, say what we’re doing about it, and keep it short unless the situation really needs more detail. I avoid anything that sounds defensive or promises something he hasn’t approved, like a refund or a deadline. If I’m not sure about a line, I flag it for him to check.
Agent — Agent
Thanks for explaining those tone expectations and how you flag uncertain lines.
When you finish drafting the email in Outlook and notify your boss, how does that handoff normally happen, and what tool or method do you use to let him know it's ready?
E4 — Employee
I save the email as a draft in Outlook, then message him to say it’s ready. If he’s nearby, I’ll just walk over and tell him instead. For sensitive ones, I point out any lines I flagged so he knows where to look first.
Agent — Agent
Got it. After you notify him and point out those flagged areas, what happens next when he requests edits or gives feedback on the draft? How do you incorporate those changes?
E5 — Employee
He usually tells me what to change right then, either in person or by message. Most of the time it’s a line or two, like softening the tone or adding a detail. I make the edits in the same Outlook draft, let him know it’s updated, and he reads it again before sending. If it’s a bigger change, like switching what we’re offering the customer, I’ll check with him on what he wants before rewriting.
Agent — Agent
Thanks for clearing that up. Once the email is finally sent by your boss, the map mentions adding a quick note on the customer thread. What system or tool do you use to record this note, and what specific details do you include in it?
E6 — Employee
I add it as an internal note on the customer’s thread in our support system. It’s just a line or two saying what the issue was, what we told them, and that my boss sent the reply. If we promised anything, like a refund or a follow-up date, I include that too.
Agent — Agent
To make sure I have everything correct, let me summarize what we've covered:
1. **Identifying Routine vs. Sensitive Emails:** You look for triggers like angry customers, cancellations, refunds, billing disputes, legal matters, or unfamiliar questions. Routine questions (like order status) are handled directly, while sensitive ones get special attention.
2. **Templates & Drafting:** For sensitive emails, you usually write from scratch rather than using a rigid template, though you might reference past emails. You aim for a friendly, direct tone mirroring your boss, acknowledging the issue without making unapproved promises.
3. **Review & Flags:** If you're unsure about a specific part, you flag it for your boss's review.
4. **Handoff & Edits:** You save the draft in Outlook and notify your boss (via message or in-person). If he requests edits, you update the draft in Outlook and he reviews it again before sending.
5. **Completion:** Once sent, you leave a brief internal note on the customer's support thread summarizing the issue, the resolution, who sent it, and any special promises made.
Is anything here incorrect or missing?
E7 — Employee
That all sounds right. The only thing I’d add is that for routine emails I still use a template and tweak it, so the “write from scratch” part only applies to the sensitive ones. Otherwise, nothing’s missing.
Agent — Agent
Thank you for clarifying that distinction about using templates for routine emails. We have captured all the necessary details for the operational decision criteria, tools, and handoffs regarding drafting requested emails.
A human reviewer will process this transcript separately. Have a great day!
Human review decision
Generate a draft SOP
SOP-0006: Drafting Requested EmailsapprovedSOP-0005: Drafting Requested EmailssupersededSOP-0004: Drafting Requested EmailssupersededRaw transcript JSON
{
"type": "knowledge_discovery_transcript",
"review_status": "pending_review",
"knowledge_session_id": "KNO-000004",
"source_session_id": "KNO-de8562c8769b405da21155332fa236bc",
"employee_id": "EMP-0007",
"master_id": 9,
"master_version": 1,
"role": "Customer Support Inbox Coordinator",
"operation": "Drafting Requested Emails",
"master_snapshot": {
"master_id": 9,
"role": "Customer Support Inbox Coordinator",
"operation": "Drafting Requested Emails",
"master_version": 1,
"title": "Drafting Requested Emails",
"trigger": "Boss requests an email informally in-person or via message",
"steps": "1. Ask clarifying questions if details or parameters are missing [Sources: map-20261117-232317-3f42d8b8.json]\n2. Pull up customer account history or email threads [Sources: map-20261117-232317-3f42d8b8.json]\n3. Create draft in Outlook matching tone and adding flags for uncertain areas on sensitive topics [Sources: map-20261117-232317-3f42d8b8.json]\n4. Save draft and notify boss [Sources: map-20261117-232317-3f42d8b8.json]\n5. Incorporate any requested edits [Sources: map-20261117-232317-3f42d8b8.json]\n6. Boss sends email [Sources: map-20261117-232317-3f42d8b8.json]\n7. Add a quick note on the customer thread [Sources: map-20261117-232317-3f42d8b8.json]",
"decisions": "",
"end_condition": "Not established",
"bot2_questions": "Specific criteria or triggers used to determine if an incoming email is routine versus sensitive or unusual\r\nHow templates are selected or customized\r\nSpecific guidelines or tone expectations for drafting boss-requested emails",
"unresolved": "• This draft starts from one approved account; review other employee sources and addenda before approving.\r\n• Specific criteria or triggers used to determine if an incoming email is routine versus sensitive or unusual\r\n• How templates are selected or customized\r\n• Specific guidelines or tone expectations for drafting boss-requested emails",
"review_resolution_notes": "",
"source_filenames": [
"map-20261117-232317-3f42d8b8.json"
]
},
"messages": [
{
"sender": "Agent",
"content": "Hello! I'm here to help document the details for the \"Drafting Requested Emails\" operation. Based on our high-level process map, we know you start when your boss informally requests an email, gather history, draft the response in Outlook, and send it back for review and sending. \n\nTo dive into the specific decision criteria, let's start with the first Bot 2 question: What specific criteria or triggers do you use to determine whether an incoming requested email is routine versus sensitive or unusual?",
"created_at": "2026-11-17T23:25:17+00:00"
},
{
"sender": "Employee",
"content": "I look for a few things. If the customer is upset or threatening to cancel, I treat it as sensitive. Same if it involves a refund, a billing dispute, or anything legal. If it’s something I haven’t seen before and I’m not sure how to answer, I also bring it to my boss. Basic questions like order status or how to do something are routine, and I just reply.",
"created_at": "2026-11-17T23:26:26+00:00"
},
{
"sender": "Agent",
"content": "That's really clear. Once you've identified an email as sensitive or unusual and decide to draft a response, how do you go about selecting or customizing a template for it?",
"created_at": "2026-11-17T23:26:26+00:00"
},
{
"sender": "Employee",
"content": "For sensitive ones, I usually don’t start from a template because they tend to need a more personal touch. I’ll write it from scratch, and sometimes I’ll look at a similar email we sent before to borrow wording or see how my boss handled it. Either way, he reviews it before anything goes out.",
"created_at": "2026-11-17T23:26:39+00:00"
},
{
"sender": "Agent",
"content": "Got it. When you are writing these drafts, what specific guidelines or tone expectations do you keep in mind to make sure it matches what your boss expects?",
"created_at": "2026-11-17T23:26:39+00:00"
},
{
"sender": "Employee",
"content": "I keep it friendly but direct, the way my boss normally writes. I start by acknowledging the customer’s issue, say what we’re doing about it, and keep it short unless the situation really needs more detail. I avoid anything that sounds defensive or promises something he hasn’t approved, like a refund or a deadline. If I’m not sure about a line, I flag it for him to check.",
"created_at": "2026-11-17T23:26:49+00:00"
},
{
"sender": "Agent",
"content": "Thanks for explaining those tone expectations and how you flag uncertain lines. \n\nWhen you finish drafting the email in Outlook and notify your boss, how does that handoff normally happen, and what tool or method do you use to let him know it's ready?",
"created_at": "2026-11-17T23:26:49+00:00"
},
{
"sender": "Employee",
"content": "I save the email as a draft in Outlook, then message him to say it’s ready. If he’s nearby, I’ll just walk over and tell him instead. For sensitive ones, I point out any lines I flagged so he knows where to look first.",
"created_at": "2026-11-17T23:27:08+00:00"
},
{
"sender": "Agent",
"content": "Got it. After you notify him and point out those flagged areas, what happens next when he requests edits or gives feedback on the draft? How do you incorporate those changes?",
"created_at": "2026-11-17T23:27:08+00:00"
},
{
"sender": "Employee",
"content": "He usually tells me what to change right then, either in person or by message. Most of the time it’s a line or two, like softening the tone or adding a detail. I make the edits in the same Outlook draft, let him know it’s updated, and he reads it again before sending. If it’s a bigger change, like switching what we’re offering the customer, I’ll check with him on what he wants before rewriting.",
"created_at": "2026-11-17T23:27:22+00:00"
},
{
"sender": "Agent",
"content": "Thanks for clearing that up. Once the email is finally sent by your boss, the map mentions adding a quick note on the customer thread. What system or tool do you use to record this note, and what specific details do you include in it?",
"created_at": "2026-11-17T23:27:22+00:00"
},
{
"sender": "Employee",
"content": "I add it as an internal note on the customer’s thread in our support system. It’s just a line or two saying what the issue was, what we told them, and that my boss sent the reply. If we promised anything, like a refund or a follow-up date, I include that too.",
"created_at": "2026-11-17T23:27:53+00:00"
},
{
"sender": "Agent",
"content": "To make sure I have everything correct, let me summarize what we've covered:\n\n1. **Identifying Routine vs. Sensitive Emails:** You look for triggers like angry customers, cancellations, refunds, billing disputes, legal matters, or unfamiliar questions. Routine questions (like order status) are handled directly, while sensitive ones get special attention.\n2. **Templates & Drafting:** For sensitive emails, you usually write from scratch rather than using a rigid template, though you might reference past emails. You aim for a friendly, direct tone mirroring your boss, acknowledging the issue without making unapproved promises.\n3. **Review & Flags:** If you're unsure about a specific part, you flag it for your boss's review. \n4. **Handoff & Edits:** You save the draft in Outlook and notify your boss (via message or in-person). If he requests edits, you update the draft in Outlook and he reviews it again before sending.\n5. **Completion:** Once sent, you leave a brief internal note on the customer's support thread summarizing the issue, the resolution, who sent it, and any special promises made.\n\nIs anything here incorrect or missing?",
"created_at": "2026-11-17T23:27:53+00:00"
},
{
"sender": "Employee",
"content": "That all sounds right. The only thing I’d add is that for routine emails I still use a template and tweak it, so the “write from scratch” part only applies to the sensitive ones. Otherwise, nothing’s missing.",
"created_at": "2026-11-17T23:28:15+00:00"
},
{
"sender": "Agent",
"content": "Thank you for clarifying that distinction about using templates for routine emails. We have captured all the necessary details for the operational decision criteria, tools, and handoffs regarding drafting requested emails. \n\nA human reviewer will process this transcript separately. Have a great day!",
"created_at": "2026-11-17T23:28:15+00:00"
}
],
"submitted_at": "2026-11-17T23:28:23+00:00"
}