Back to Details

email-ops

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Email Ops

邮件运营

Use this when the real task is mailbox work: triage, drafting, replying, sending, or proving a message landed in Sent.
This is not a generic writing skill. It is an operator workflow around the actual mail surface.
当实际任务为邮箱相关工作时使用本工作流：分类、草稿撰写、回复、发送，或者验证邮件是否已成功存入已发送文件夹。
这不是通用写作技能，而是围绕实际邮件界面的操作工作流。

Skill Stack

技能栈

Pull these ECC-native skills into the workflow when relevant:
  • brand-voice
    before drafting anything user-facing
  • investor-outreach
    for investor, partner, or sponsor-facing mail
  • customer-billing-ops
    when the thread is a billing/support incident rather than generic correspondence
  • knowledge-ops
    when the message or thread should be captured into durable context afterward
  • research-ops
    when a reply depends on fresh external facts
相关场景下可在工作流中调用以下ECC原生技能：
  • 撰写任何面向用户的内容前调用
    brand-voice
  • 面向投资人、合作伙伴或赞助商的邮件调用
    investor-outreach
  • 若邮件线程是账单/支持事件而非普通通信，调用
    customer-billing-ops
  • 后续需要将邮件或线程保存到持久上下文时调用
    knowledge-ops
  • 回复需要最新外部事实支撑时调用
    research-ops

When to Use

适用场景

  • user asks to triage inbox or archive low-signal mail
  • user wants a draft, reply, or new outbound email
  • user wants to know whether a mail was already sent
  • the user wants proof of which account, thread, or Sent entry was used
  • 用户要求分类收件箱或者归档低价值邮件
  • 用户需要撰写草稿、回复或者新建外发邮件
  • 用户想知道某封邮件是否已经发送
  • 用户需要获取使用了哪个账户、哪个线程或者哪条已发送记录的证明

Guardrails

防护规则

  • draft first unless the user clearly asked for a live send
  • never claim a message was sent without a real Sent-folder or client-side confirmation
  • do not switch sender accounts casually; choose the account that matches the project and recipient
  • do not delete uncertain business mail during cleanup
  • if the task is really DM or iMessage work, hand off to 
    messages-ops
  • 除非用户明确要求直接发送，否则先撰写草稿
  • 没有真实已发送文件夹或者客户端确认的情况下，绝不能宣称邮件已发送
  • 不要随意切换发件人账户；选择与项目和收件人匹配的账户
  • 清理时不要删除存疑的商务邮件
  • 如果任务实际是DM或者iMessage相关工作，转交给
    messages-ops
    处理

Workflow

工作流

1. Resolve the exact surface

1. 明确准确操作界面

Before acting, settle:
  • which mailbox account
  • which thread or recipient
  • whether the task is triage, draft, reply, or send
  • whether the user wants draft-only or live send
操作前先确认：
  • 要使用哪个邮箱账户
  • 要操作哪个线程或者哪个收件人
  • 任务是分类、草稿、回复还是发送
  • 用户是只需要草稿还是需要直接发送

2. Read the thread before composing

2. 撰写前先阅读线程内容

If replying:
  • read the existing thread
  • identify the last outbound touch
  • identify any commitments, deadlines, or unanswered questions
If creating a new outbound:
  • identify warmth level
  • select the correct channel and sender account
  • pull 
    brand-voice
    before drafting
如果是回复邮件：
  • 阅读现有线程内容
  • 确认上一次外发沟通内容
  • 找出所有已承诺内容、截止日期或者未回复的问题
如果是新建外发邮件：
  • 确认沟通的亲密度等级
  • 选择正确的渠道和发件人账户
  • 撰写草稿前调用
    brand-voice

3. Draft, then verify

3. 撰写草稿，然后验证

For draft-only work:
  • produce the final copy
  • state sender, recipient, subject, and purpose
For live-send work:
  • verify the exact final body first
  • send through the chosen mail surface
  • confirm the message landed in Sent or the equivalent sent-copy store
仅需草稿的任务：
  • 产出最终文稿
  • 说明发件人、收件人、主题和用途
需要直接发送的任务：
  • 首先验证最终正文内容准确无误
  • 通过选定的邮件界面发送
  • 确认邮件已进入已发送文件夹或等效的已发副本存储位置

4. Report exact state

4. 上报准确状态

Use exact status words:
  • drafted
  • approval-pending
  • sent
  • blocked
  • awaiting verification
If the send surface is blocked, preserve the draft and report the exact blocker instead of improvising a second transport without saying so.
使用准确的状态词：
  • 已起草
  • 待审批
  • 已发送
  • 已阻塞
  • 待验证
如果发送界面被阻塞，保留草稿并上报具体阻塞原因，不要未告知用户就临时使用第二种发送渠道。

Output Format

输出格式

text
MAIL SURFACE
- account
- thread / recipient
- requested action

DRAFT
- subject
- body

STATUS
- drafted / sent / blocked
- proof of Sent when applicable

NEXT STEP
- send
- follow up
- archive / move
text
MAIL SURFACE
- account
- thread / recipient
- requested action

DRAFT
- subject
- body

STATUS
- drafted / sent / blocked
- proof of Sent when applicable

NEXT STEP
- send
- follow up
- archive / move

Pitfalls

常见陷阱

  • do not claim send success without a sent-copy check
  • do not ignore the thread history and write a contextless reply
  • do not mix mailbox work with DM or text-message workflows
  • do not expose secrets, auth details, or unnecessary message metadata
  • 未检查已发副本的情况下不要宣称发送成功
  • 不要忽略线程历史，撰写无上下文的回复
  • 不要将邮箱工作与DM或短信工作流混淆
  • 不要泄露密钥、认证信息或者不必要的邮件元数据

Verification

验证项

  • the response names the account and thread or recipient
  • any send claim includes Sent proof or an explicit client-side confirmation
  • the final state is one of drafted / sent / blocked / awaiting verification
  • 回复中明确标注账户、线程或收件人
  • 任何发送声明都包含已发邮件证明或者明确的客户端确认信息
  • 最终状态为已起草/已发送/已阻塞/待验证中的一种