email-delivery-failure
1
总安装量
1
周安装量
#77213
全站排名
安装命令
npx skills add https://github.com/skillrecordings/support --skill email-delivery-failure
Agent 安装分布
amp
1
cline
1
opencode
1
cursor
1
continue
1
kimi-cli
1
Skill 文档
Email Delivery Failure
Response Patterns (from samples)
Common openings:
- “Hi,”
- “Yes, click “unsubscribe from ai hero messages” at the bottom of the email. Sorry for being noisy!”
- “It’s still in review! Taking a bit longer than expected.”
Common core lines:
- “If you have any trouble accessing the course, please let us know!”
- “Hi,”
- “Everything should be back up and running now – please try to request a new login link and let me know if you still don’t receive it.”
Common closings:
- “If you have any trouble accessing the course, please let us know!”
- “I apologize for the inconvenience!”
- “Yes, click “unsubscribe from ai hero messages” at the bottom of the email. Sorry for being noisy!”
Phrases That Work (4-gram frequency)
- “let me know if” â 12 (25.5%)
- “if you have any” â 12 (25.5%)
- “me know if you” â 10 (21.3%)
- “you have any trouble” â 7 (14.9%)
- “using the email login” â 6 (12.8%)
- “the email login link” â 6 (12.8%)
- “email login link at” â 6 (12.8%)
- “login link at the” â 6 (12.8%)
- “link at the top” â 6 (12.8%)
- “at the top of” â 6 (12.8%)
Tone Guidance (observed)
- Openings trend toward: “Hi,”
- Closings often include: “If you have any trouble accessing the course, please let us know!”
What NOT To Do
- Don’t introduce policy details that are not present in the verified response lines above.
- Don’t paraphrase or reframe the customer’s question in a way that changes meaning.
- Don’t add refund/discount promises unless they appear in the extracted responses for this topic.
Validation
Draft must:
- Include at least one of the required phrases from the validation block
- Stay consistent with the observed response patterns above
- NOT introduce policy details that are not present in the verified response lines above.