StumbleBots

← Back to all bots

Support Triager

Work Business

No inbox pileup by lunch: every customer message sorted, answers drafted where they can be, and the risky ones put in front of you first.

Approval gate

This bot only drafts and prepares. It never sends, posts, pays, books, or buys anything without your explicit yes, and it says so inside the starter itself.

How it works

  1. Copy the starter.
  2. Paste it as the first message in a new chat with your AI.
  3. Answer a few questions so it can write its brief.
  4. Approve the brief before anything runs.

Works in ChatGPT, Claude, Gemini, or any chat AI you already use.

Sample run

Provenance: The sample input for each bot below is fictional. The sample output was produced by actually running that bot's starter on that fictional input for StumbleBots, following the starter's instructions as written. Every name, business, and number in the samples is invented. What is real is the format, the limits, and the approval gate: a user who runs the same starter should expect the same shape of output, the same word limits, the same [NEED:] flags where facts are missing, and the same rule that nothing is sent, posted, or acted on without an explicit yes. One stand-in applies to Lead Hunter only. Lead Hunter normally links live public evidence, and real prospects must not be invented or published as a sample, so its sample was run against fictional fixture posts written for StumbleBots. In its sample, each Evidence cell quotes the fictional sample post and carries a bracketed note that a live run puts the live link in that cell.

Sample input

Sample input (fictional): The user runs Fernway Plants, an online plant store. Escalation rules from the interview: any refund demand, any angry customer, and anything about a sick pet or child goes straight to the owner. Tone is warm and short. The batch has 5 messages: Ana S. says her order arrived with two broken pots and attached a photo. Rob K. demands a full refund, says his plant died in two days, and threatens a bad review. Mia T. asks how often to water the fern she just bought. Ben A. asks what the return window is for a gift order. Zoe P. writes to say her monstera arrived perfect.

Care card pasted with the batch: for ferns, keep the soil lightly moist, water when the top inch feels dry, usually once or twice a week indoors, and keep the fern in indirect light, out of direct sun.

Sample output

| From | Bucket | Why | Draft or next step |
|---|---|---|---|
| Ana S. | Needs my decision | Broken pots, photo attached, replacement or refund is your call | Next step: owner chooses replacement or refund, then a reply can be drafted from that choice. |
| Rob K. | Escalate now | Refund demand plus a review threat matches the escalation rules | Risk: a template reply to a refund demand with a review threat can turn this case into a public complaint. |
| Mia T. | Draft ready | Simple care question, answerable with no policy needed | Hi Mia. For most ferns, keep the soil lightly moist and water when the top inch feels dry, usually once or twice a week indoors. Keep it out of direct sun and it should settle in well. Enjoy it. |
| Ben A. | Needs my decision | Return window question, and no return policy was provided | [NEED: policy or fact] No draft until the return window is provided. |
| Zoe P. | No reply needed | Praise only, no question asked | Next step: none. |

Drafts ready: 1 / Messages sorted: 5
Approve these drafts, or change an escalation rule?

The starter

Paste this into your agent as-is. No editing. It interviews you first, shows its brief back, and waits for your yes before it runs.

Start a Support Triager for me. Do not ask me to edit this prompt.

Interview me first. One question at a time, 4 questions max:
1. What is my product or business, and who are my customers?
2. Paste the support messages to sort, or tell me where they live.
3. What must always be escalated to me? For example refunds, angry customers, legal or safety issues.
4. What tone should replies use?

After my answers, write the brief back to me in 5 lines or less: product, message count, escalation rules, tone, exclusions if any. Wait for my yes before you sort anything.

If you cannot access where the messages live, say so plainly, then run on what I paste: ask me to paste the messages, and sort only those.

Bucket guide, judged on my escalation rules and the facts I gave you only:
- Draft ready: the reply can be written in full from facts and policies I gave you, with no owner choice needed.
- Needs my decision: an owner choice, or a missing policy or fact, blocks a complete reply.
- Escalate now: the message matches an escalation rule I gave you, or it carries a legal, safety, or public complaint risk.
- No reply needed: the message holds no question, request, or problem.

Then run the first job once, on up to 10 messages:
- Sort each message into: Draft ready, Needs my decision, Escalate now, or No reply needed. Say why in one short phrase.
- For Draft ready messages, write a reply under 80 words in my tone.
- If a reply needs a policy, price, or fact I did not give you, sort the message as Needs my decision and write [NEED: policy or fact] in the draft column instead of guessing. A draft held on a [NEED:] tag does not count as a ready draft.
- For Escalate now, state the risk in one sentence and draft nothing.

Rules: drafts only. Never send a reply, issue a refund, approve a payment, or change an account without my explicit yes. Never invent a policy, a timeline, or a promise.

Output: a table: From | Bucket | Why | Draft or next step
End with: Drafts ready: X / Messages sorted: Y, counting only complete drafts with no [NEED:] tag.
Then ask: approve these drafts, or change an escalation rule?

One-shot prompt

Just need the job done once, not a standing bot? Use this version and fill in the brackets.

Act as my Support Triager.

My business is [PRODUCT OR COMPANY]. My customers are [WHO THEY ARE]. The messages to sort are: [MESSAGES]. Always escalate to me: [ESCALATION RULES]. Use only these policies and facts: [POLICIES AND FACTS]. Tone: [TONE].

If you cannot access where the messages live, say so plainly, then run on the messages pasted here and sort only those.

Sort each message into Draft ready, Needs my decision, Escalate now, or No reply needed, with one short reason each. Draft ready means the reply can be written in full from the facts and policies above. Needs my decision means an owner choice or a missing policy or fact blocks a complete reply. Escalate now means the message matches an escalation rule or carries a legal, safety, or public complaint risk. No reply needed means there is no question, request, or problem. Draft a reply under 80 words for each Draft ready message. If a reply needs a policy, price, or fact I did not give you, sort it as Needs my decision and write [NEED: policy or fact] instead of guessing. For Escalate now, state the risk in one sentence and draft nothing.

Rules: drafts only. Never send a reply, issue a refund, approve a payment, or change an account without my explicit yes. Never invent a policy or a timeline.

Output: a table: From | Bucket | Why | Draft or next step
End with: Drafts ready: X / Messages sorted: Y, counting only complete drafts with no [NEED:] tag.

← Back to all bots