Drafts a customer reply from product docs and cites the file.
Support Reply Draft is an Eve agent that Drafts a customer reply from product docs and cites the file. It is for Eve developers answering product questions. Preview every file on this page, then install with npx shadcn@latest add @evex/support-reply-draft. Support Reply Draft is an eve agent that drafts customer-facing support replies from product help and support documentation.
Drafts a customer reply from product docs and cites the file.
Support Reply Draft is an eve agent that drafts customer-facing support replies from product help and support documentation. It searches the roots listed in PRODUCT_DOCS_ROOTS, reads the matching articles, and returns a draft in email or ticket tone with file-path citations.
You interact with it through Eve chat sessions only. There is no GitHub channel and no email-send connection. Paste a customer question, get a draft, then copy it into your own mail or ticket tool.
When the product docs do not cover the question, it says so instead of inventing refunds, SLAs, or setup steps. The draft_support_reply tool records the reply text and citations and always reports sent false so the agent never claims delivery.
An operator pastes a refund question. The agent reads docs/help/billing.md, drafts an email-tone reply with the cited path, and stops so a human can send it from the real mailbox.
A ticket asks how to reset two-factor auth. The agent searches the support tree, cites the matching article, and returns a ticket-ready draft without posting to any ticket API.
When a customer asks about an undocumented on-call policy, the agent says the product docs do not cover it rather than inventing SLAs from training data.
After draft_support_reply returns, the operator can ask the agent to write_file the reply into a local path for review or handoff without implying the message was sent.
Run npx shadcn@latest add @evex/support-reply-draft inside an eve app, set AI_GATEWAY_API_KEY and PRODUCT_DOCS_ROOTS, then paste a customer question in Eve chat. Copy the returned draft into your mail or ticket tool yourself.
No. There is no send tool and no GitHub channel. draft_support_reply always returns sent false. Asking it to email a customer or open an issue still produces a draft only.
Only paths under PRODUCT_DOCS_ROOTS. search_product_docs and read_product_doc refuse application source, tests, configs, and lockfiles.
The agent says the product documentation does not cover the question and still does not invent policy. It may still call draft_support_reply with docsCovered set to false.
Docs Knowledge Assistant answers developer questions from README, docs/, CONTRIBUTING*, and AGENTS.md and can open a docs-gap GitHub issue. This agent drafts customer support replies from product help roots and stops at the draft.
npx shadcn@latest add @evex/support-reply-draft