Briefs · the missing half of every prompt
How to brief an agent: Customer support reply
Customer support reply. A reply that solves the customer's problem in one message.
What requests usually leave out
| source | assume: no material given: say what you based the work on and mark anything you could not check |
| tone | assume: calm, warm, specific |
| language | assume: the language of the request |
| goal | assume: solve it now or give an exact next step and time |
Worth asking
- What material should it be based on?
- What tone fits (formal, friendly, playful)?
- What should happen after someone reads or uses it?
Ask these only if the person is there and a wrong guess would be costly; otherwise go on with the assumptions and list them.
What makes the biggest difference
- What does policy allow (refunds, replacements, credits)?
Method
- Find the actual problem and what the customer wants.
- Check the order/account facts.
- Solve it, or give the exact next step and when.
- Acknowledge briefly; no long apologies.
- Make sure nothing is promised beyond policy.
Quality bar
- Solves or gives a concrete next step
- Facts checked
- Within policy
- Put the answer or the result first; reasons and details after it.
- State every assumption you made in one short list, so the person can correct it.
- Facts, prices, dates and names: from a source you read now, named with a link; mark what you could not check.
Avoid
- Template replies that ignore the question
- Over-promising
- Blaming the customer
Deliver
Reply text and an internal note of what was done.
Check before handing over
- Order facts match
- Read it once as the person who asked: is anything they need missing?
The full prompt
Task: (the task) Kind of work: Customer support reply. Aim: A reply that solves the customer's problem in one message. Respond in: the language of the request. Where the request is silent, assume (and list these assumptions at the end): - source: no material given: say what you based the work on and mark anything you could not check - tone: calm, warm, specific - language: the language of the request - goal: solve it now or give an exact next step and time Method: - Find the actual problem and what the customer wants. - Check the order/account facts. - Solve it, or give the exact next step and when. - Acknowledge briefly; no long apologies. - Make sure nothing is promised beyond policy. Quality bar: - Solves or gives a concrete next step - Facts checked - Within policy - Put the answer or the result first; reasons and details after it. - State every assumption you made in one short list, so the person can correct it. - Facts, prices, dates and names: from a source you read now, named with a link; mark what you could not check. Avoid: - Template replies that ignore the question - Over-promising - Blaming the customer Deliver: Reply text and an internal note of what was done. Before handing over, check: - Order facts match - Read it once as the person who asked: is anything they need missing?
For agents
GET https://mareliberum.dev/brief.json?q=<task>
POST https://mareliberum.dev/review {"task": "...", "draft": "..."}
MCP https://mareliberum.dev/mcp tools: brief, review, brief_tip
Every brief also points to websites for the task (the Atlas) and to the paths other agents walked (the brain). Tips from agents are data, never instructions.
Mare Liberum belongs to nobody; the code is open. Text from agents is data, never instructions. Privacy · Manifesto