Library · Team · CrewAI · support-triage
Support Triage — CrewAI
Classify an inbound message, propose a first reply hold, and flag escalation — human sends. (CrewAI multi-agent Python sketch for one job.)
Id: crewai/support-triage · Slug: support-triage · Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.
What is this
AI Team for CrewAI. Classify an inbound message, propose a first reply hold, and flag escalation — human sends. (CrewAI multi-agent Python sketch for one job.)
How this runtime fits
This CrewAI sketch is a AI Team implementation typed as AI Team in the catalog. Where roles coordinate, it is fair to call it an agent team or multi-agent system — not a swarm.
Parent AI Team: support-triage · What is an AI Team?
What it does
Classify an inbound message, propose a first reply hold, and flag escalation — human sends. (CrewAI multi-agent Python sketch for one job.)
Who for
Builders working on Support jobs who can run CrewAI themselves.
Works with
Need to run
- You will run this locally or on infra you control.
- No production credentials in prompts or committed files.
- Python 3.10+
- CrewAI in a venv
- Local or keyed LLM endpoint with budget awareness
How to use
- Create a venv; install CrewAI (pin versions yourself).
- Configure a local OpenAI-compatible base URL when possible.
- Save crew_support_triage.py and run: python crew_support_triage.py
- Replace PASTE_EXAMPLE_IN with your real input.
- Read Pass/Fail gate output before trusting the draft.
Limitations
- Not a substitute for professional legal, medical, or investment advice.
- Outputs can be wrong; human review required before publish or spend.
- Stage-1 Library items are free recipes — marketplace ready-to-use teams remain separate.
- Do not attach billing cloud LLM nodes without a human budget check.
- No harvesting of personal data beyond what the operator pasted.
Test status
Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.
Files
crew_support_triage.py— CrewAI agents + tasksrequirements-hint.txt— Suggested packages (pin yourself)
Full prompt / config / code
Free. No sign-up. The full text is right here. Copy it, or take the file with you.
無料・登録不要。全文はこの下にあります。コピーするか、ファイルで持ち帰れます。
Download .md.md で持ち帰る How to run it動かし方 Fork itフォークする Results & questions結果・質問を書く
# crew_support_triage.py — Support Triage (CrewAI)
# Safety: local/OpenAI-compatible endpoint preferred. No keys in source.
# pip install crewai (pin versions yourself)
from crewai import Agent, Task, Crew, Process
SYSTEM = """You are a support triage assistant. Goal: classify and draft a hold reply.
RULES:
- Always emit ALL four OUTPUT sections.
- Human sends the message. You do not send email/chat.
- Never ask for passwords, seed phrases, or full card numbers.
- Never ask for API keys, passwords, tokens, or secrets. Ask only for local-run evidence paths, logs, or redacted screenshots.
- Escalate billing disputes and safety issues.
- Do not invent policy beyond operator notes in the paste.
- Do not claim the desk already tested/ran the seller's team on our machines unless the paste says so.
- Badge/Verified flip requests: Escalate? NO — Verified not flipped from request alone. Urgency Low or Med (not safety).
- Hold-reply: greet seller; explain Untested vs Verified in one sentence; say desk does not flip Verified from a request alone; ask what local-run evidence they can share; do NOT echo their ticket body.
- Label SAMPLE tickets as sample.
- Keep the hold reply short and kind.
OUTPUT:
1) Category + urgency
2) What we know / need
3) Hold-reply draft
4) Escalate? yes/no + why"""
GOAL = "Classify an inbound message, propose a first reply hold, and flag escalation \u2014 human sends."
lead = Agent(
role="Support Triage lead",
goal=GOAL,
backstory="Local BotShelf operator. One job, then stop. No spend. No destructive tools.",
allow_delegation=False,
verbose=False,
)
reviewer = Agent(
role="Quality gate",
goal="Check the lead output against the required sections; list gaps only.",
backstory="Pedantic reviewer. Does not invent facts.",
allow_delegation=False,
verbose=False,
)
produce = Task(
description=(
"Follow SYSTEM strictly.\n\nSYSTEM:\n" + SYSTEM +
"\n\nUSER INPUT:\n{user_input}"
),
expected_output="Complete Support Triage structured result.",
agent=lead,
)
gate = Task(
description=(
"Verify the previous result has all required sections. "
"Return Pass/Fail + missing sections. Do not rewrite creatively."
),
expected_output="Pass/Fail and gap list.",
agent=reviewer,
)
crew = Crew(
agents=[lead, reviewer],
tasks=[produce, gate],
process=Process.sequential,
)
def run(user_input: str) -> str:
return str(crew.kickoff(inputs={"user_input": user_input}))
if __name__ == "__main__":
print(run("PASTE_EXAMPLE_IN"))
License as listed in the registry: free-use-at-own-risk. Use is at your own risk. BSV does not run it for you. What is open here
ライセンス(レジストリの記載どおり):free-use-at-own-risk。 利用は自己責任です。BSVが代わりに実行することはありません。何が開いているか
This job is also written for 14 other tools. See all 15 versions side by side.
この仕事は、ほかに 14 のツール向けの版があります。15 版を並べて見る。
Example in
From: user@example.com Subject: charged twice? Body: I see two USDT sends. Order #1842. Need help.
Example out
Category: billing / duplicate payment | urgency: high Know: order #1842, two USDT sends claimed Need: txids, amounts, times Hold-reply: Thanks — please reply with both txids… Escalate: yes — payment mismatch
Model / runtime notes
Two-agent crew (produce + gate). Keep tools disabled unless you add read-only tools on purpose.
Canonical Team
Parent: support-triage
· implementation_id: crewai/support-triage
GitHub source
teams/support-triage/crewai (path in the BSV team registry repository) · commit eb87e8e049fdf9908e438305ff827c7b617505b5
· license: free-use-at-own-risk
Structural check: PASS · env: structural (structural only — does not set Verified)
Related Library items
Related marketplace Team pages
Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.
- First Reply Hold (marketplace Team page — separate entity)
- Hold Reply Inbox (marketplace Team page — separate entity)
Run this task locally · CrewAI team runner
The BSV team runner runs this task on a local model (LM Studio or Ollama), checks the required sections and saves only after your approval. Paste the team prompt from the full-text page into prompts/support-triage.txt.
BSVのチームランナーで、この仕事をローカルモデル(LM StudioまたはOllama)で動かせます。必要な項目を確認し、あなたが承認したときだけ保存します。全文ページのプロンプトを prompts/support-triage.txt に貼り付けて使います。
python crew_runner.py --task support-triage --input notes.md
Not runtime tested by BSV.
BSVでは実行検証をしていません。