# Recipe: answer a customer question, with sources you can check

A copy-paste prompt: your agent drafts a support reply from what your team knows in onecell, cites every claim, and keeps internal notes out of the reply.

> [!info]
> **For:** support and customer success. **When:** a question arrives that someone on the team has answered before, or should have written down. **Takes:** about a minute of agent time. **You get:** a reply ready to send, the source behind every claim, and internal notes kept separate.

## The prompt

```text
A customer asks: "<their question>". Draft a reply from what we know in
onecell. Save it to <cell>.

1. Search onecell for product notes, docs, past answers and decisions on
   this. If it's about how the product behaves and the code is here,
   check the code too. Cite every source as cell · heading · passage, or
   as a file path.

2. Draft "Support: <short question>" (dry run first):
   - a reply ready to send: plain words, the direct answer first, then
     what they can do instead if the answer is no
   - a table of each claim in the reply and its source
   - internal notes the customer shouldn't see: wording rules, known
     issues, anything uncertain
   Claim nothing you can't source. If the answer is unclear, say so in
   the internal notes and draft a holding reply instead.

3. Reply with the link and whether this deserves a help article.
```

## What your agent does

1. Looks up what the team knows
   Product notes, docs, earlier answers and decisions, and the code when the question is about behaviour.
2. Answers first
   The reply leads with the direct answer, then the way forward.
3. Sources every claim
   A table a teammate can check in seconds before sending.
4. Keeps the internal separate
   Known issues and wording rules go in notes the customer never sees.

## What you get

An answer for a made-up invoicing app, Tally: the reply, a source for each claim, and a detail the agent kept out of the reply on purpose.

<!-- onecell:block {"type":"embed","documentId":"34f428fa-b3c3-4b6e-ae15-7e42732803fe"} -->
[Sample support answer: can I change an invoice after sending it?](https://onecell.io/p/sample-support-answer-edit-sent-invoice)

## Variations

<details>
<summary>Turn it into a help article</summary>

Add: “Then write it as a help article for the docs: a question as the title, the answer in two sentences, then steps.” Publish it once someone has checked it.

</details>

<details>
<summary>A bug report, not a question</summary>

Add: “If this is a bug, write a ticket in `<backlog cell>` with steps to reproduce, and link it from the internal notes.”

</details>

<details>
<summary>Many questions at once</summary>

Paste a batch of questions and ask for one reply each, plus a list of the ones onecell had no source for. Those are your missing docs.

</details>

## Tips

- A claim without a source is a guess. Send the holding reply instead.
- Answers you send often belong in the docs, not in a support inbox.
- If the code and the docs disagree, the code wins, and the docs get a fix.

---

Part of [onecell recipes](https://onecell.io/help/recipes): copy-paste prompts for using onecell in your work.