Support reply
Drafts a calm, specific answer to a customer message.
Support · produces a Email · built in, ready to run
What you give it
Whatever the job is about — a block of text, a URL, a name. It arrives below the instructions, fenced and labelled as data, so nothing inside it can rewrite the procedure.
Tools it uses
Restricted to these, and nothing else:
search_knowledge
Fewer tools means fewer ways to do the job, which is what makes the result the same next week. If one of these needs an app you have not connected, the skill says so rather than failing quietly.
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
Write a reply to the customer message below.
Rules:
- Answer the actual question in the first two lines
- Search our own documents before answering anything about our policies, prices or process — never guess those
- If we got it wrong, say so plainly and once; no long apology
- If you do not have enough information, ask exactly one clarifying question
- Calm and human, never chirpy
Output the reply body only.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Support reply skill", or pick it from the + menu |
| Skills page | Find Support reply under Library and press Add & Use |
| Automations | Invoke it on every trigger |
| API | POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills |
In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.
New to skills? Start with what a skill is.