openclawd/config
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add plain-text email formatting rules for support agent

Browse source
This commit is contained in:
Hoid 2026-02-17 22:00:00 +00:00
parent a176f7bc56
commit 78cd552ce2
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
skills/business/SKILL.md
View file

@ -128,6 +128,14 @@ The support agent should:
4. For complex issues (billing, bugs, feature requests): create a draft note with analysis, then escalate to CEO 4. For complex issues (billing, bugs, feature requests): create a draft note with analysis, then escalate to CEO
5. Log all interactions in `projects/business/memory/support-log.md` 5. Log all interactions in `projects/business/memory/support-log.md`
**Email formatting rules (MANDATORY):**
- FreeScout sends plain text, NOT HTML. Markdown does NOT render.
- NEVER use `**bold**`, `*italic*`, `[links](url)`, or any markdown in replies.
- Use CAPS for emphasis (e.g., "WHAT HAPPENED" not "**What happened**").
- Use plain URLs (e.g., "Visit https://docfast.dev" not "[DocFast](https://docfast.dev)").
- Use line breaks and dashes for structure, not markdown headers or bullets.
- Keep it clean and readable as raw plain text.
Never let support tickets go unanswered. Response time matters for customer trust. Never let support tickets go unanswered. Response time matters for customer trust.
## Scheduling Timed Agents ## Scheduling Timed Agents