Loading the catalog…
A small LangGraph app classifies a ticket, drafts a reply, and interrupts for a person before anything is sent.
The docs cover persistence, interrupts, and human-in-the-loop. Use an interrupt for the approval rather than a comment in the prompt alone.
The wait node does not have a send tool. That is the product decision.
Write down disagreements. Fix the excerpts before you tune adjectives in the prompt.
Add it behind the approved flag, in a separate change, with a log of who approved.
These are editorial labels so you can compare playbooks. They are not measurements.
No. Status is unverified. Paste the prompt, keep the version that worked, and do not treat the time or cost lines as measurements.
LangGraph is a runtime. The playbook is the shape of the graph: classify, draft, stop. There is no hosted 'LangGraph agent' to click through in this catalog.
Official documentation URL, checked when this seed was written. The prompt and steps are an original AI Playbook Gems playbook, not a quotation of a customer story, and have not been re-run.
Machine-readable copy: JSON
LangGraph handles this as a draft: What they saw, when, and what I should not click. Do not reply with a link.
Unverified · docs.langchain.com · 15 Oct 2026
LangGraph handles this as a draft: Group by the error string I name. Count each group. Do not close tickets.
Unverified · docs.langchain.com · 14 Oct 2026
LangGraph handles this as a draft: Which ones mention a charge id. Do not refund.
Unverified · docs.langchain.com · 11 Oct 2026