How It’s Done
Employee interview
INT-000017
Employee: EMP-0007 — Person 1
Official role: Customer Support Inbox Coordinator
Interview status: submitted
Interview Session ID: INT-000017-1a870efb
You can leave this page and resume the same interview from your employee profile. Replies are saved as you go.
Previous approved maps (0)
None linked to this employee yet. This interview starts fresh.
Interview chat
Agent
Hello! I'm your process discovery assistant. I'm here to help map out your normal responsibilities and workflows so we can get a clear picture of how your day-to-day operations work.
To get started, could you briefly describe your role and tell me what the main activities or tasks are that you regularly perform?
Employee
’m the Customer Support Inbox Coordinator, which really just means I’m the person my boss comes to when he needs an email written. He’ll stop by my desk or ping me with whatever’s going on, like a customer who’s upset, a follow-up he’s been putting off, or a reply he just doesn’t have time to deal with, and I write it up in Outlook so he can look it over and send it.
Beyond that, I keep an eye on the support inbox throughout the day and sort through what’s coming in. A lot of it is routine stuff like common questions or simple issues, and I just reply to those myself. The ones that are sensitive, unusual, or need a decision from him, I bring to him instead of guessing.
Most of my day is pretty reactive. He’ll come over with a request and I turn it around as fast as I can, then go back to the inbox and make sure nothing’s sitting unanswered.
Agent
Thanks for explaining that. It sounds like you have two main tracks of work: drafting emails for your boss when he requests them, and managing the incoming support inbox yourself by handling routine questions and escalating sensitive ones.
Let's start by looking closer at the first one. When your boss asks you to write an email for him, what typically happens from the moment he makes the request to the time you hand it off to him?
Employee
So when he comes to me, it’s usually pretty informal. He’ll walk over or message me and give me the quick version, something like “this customer is upset about a late shipment, can you write them back?” Most of the time he gives me just enough to get started, so if I’m missing something important, like what he’s willing to offer or whether this is the first time the customer has complained, I’ll ask him right then instead of guessing.
Then I pull up the customer’s email thread or account info so I know the history, and I draft the reply in Outlook. I try to match how he normally sounds, which is friendly but direct, and I keep it short unless the situation needs more. If it’s a sensitive one, I’m more careful about the wording and I’ll often flag the part I’m least sure about so he can look at it first.
When it’s done, I save it as a draft and let him know it’s ready, either by messaging him or walking it over. He reads it, sometimes tweaks a line or two, and then he sends it himself. If he wants changes I make them right away. Once it’s sent, I’ll usually make a quick note on the customer’s thread so the next person who looks at it knows what happened.
Agent
That gives a really clear picture of how those boss-requested drafts come together—from his initial ask, clarifying details, checking the history, drafting in Outlook, saving it for his review, and making any tweaks before he sends it.
Now, let's look at the other main part of your day: managing the incoming support inbox. When you're going through the inbox, what's the typical flow for reviewing a new incoming message and deciding whether you handle it yourself or bring it to your boss?
Employee
I look at each new message and decide pretty quickly if it’s something I can handle. If it’s a basic question or a common issue, I just reply myself. If it seems tricky or the customer is upset, I take it to my boss.
Agent
Got it. When you decide to handle a routine question or issue yourself, what does that process look like from start to finish? For example, do you use saved templates, write a custom reply, and do you need to check anything else before hitting send?
Employee
I usually start with a saved template if there’s one that fits, then tweak it a bit for the customer. Sometimes I’ll check their account first to make sure the info is right. Then I send it.
Agent
That makes sense—quickly seeing if a template fits, doing a quick account check if needed, tweaking it, and sending it off.
Now, on the flip side, what happens when you get a message that you *don't* handle yourself—the ones you decide to bring to your boss? How do you hand those off to him?
Employee
I usually flag it and send him a quick message or stop by his desk to tell him about it. I give him the short version of what the customer wants and let him decide what to do from there.
Agent
Got it. So for those trickier or sensitive messages, you flag them, give him the quick summary, and pass them over for his decision.
To make sure I have everything, it sounds like your role centers around two main operations:
1. **Drafting requested emails**: Receiving a request from your boss, clarifying details, reviewing history, drafting in Outlook, having him review/edit, and adding a note after he sends it.
2. **Managing the support inbox**: Reviewing incoming messages, either replying directly (using templates and quick account checks for routine stuff) or escalating to your boss (flagging and giving a quick summary).
Does that summary accurately reflect the structure of your work?
Employee
Yes, that’s pretty much it. Those two things make up most of my day.
Agent
Wonderful. Thank you so much for walking me through your day and helping me map out how your role works.
Here is a quick overview of what we've captured:
### A. Role Overview
* **Role:** Customer Support Inbox Coordinator
* **Identified Operations:**
1. Drafting Requested Emails
2. Managing the Support Inbox
### B. High-Level Process Maps
1. **Drafting Requested Emails:**
* **Initiation:** Boss requests an email (informally in-person or via message).
* **Clarification:** Ask clarifying questions if details or parameters are missing.
* **Context Check:** Pull up customer account history/email threads.
* **Drafting:** Create draft in Outlook (matching tone; adding flags for uncertain areas on sensitive topics).
* **Review & Send:** Save draft, notify boss, incorporate any edits, and boss sends.
* **Closure:** Add a quick note on the customer thread.
2. **Managing the Support Inbox:**
* **Initiation:** Reviewing incoming support messages throughout the day.
* **Triage / Decision Point:**
* *Path A (Routine):* Use templates, do a quick account check if needed, tweak, and reply directly.
* *Path B (Sensitive/Unusual):* Flag the message, give boss a quick verbal or messaged summary, and hand off for his decision.
### C. Areas for Further Investigation
* Specific criteria or triggers used to determine if an incoming email is "routine" versus "sensitive/unusual."
* How templates are selected or customized.
* Specific guidelines or tone expectations for drafting boss-requested emails.
### D. Validation Status
* **Confirmed Operations:** Both "Drafting Requested Emails" and "Managing the Support Inbox" have been confirmed by you as the accurate structure of your work.
This gives us a fantastic foundational map of your workflows. A second agent will be able to use this structure to dive into the finer details if needed. Is there anything else you'd like to add before we wrap up?
Employee
No, I think that covers it for now. Thanks!
Agent
You're very welcome! Thank you for your time and for sharing how your day-to-day operations work. Have a wonderful rest of your day!
Employee
/finish
Agent
Map saved: map-20261117-232317-3f42d8b8.json
This interview was submitted and is read-only. Start a new interview for changes.
Optional screen demonstration (computer tasks only)
You can attach a narrated recording during process discovery, but it is usually best to map the broad workflow first. This does not replace the employee interview. Detailed step-to-screenshot links are added later when an SOP is approved.