FAQ Answer Drafter from Ticket
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
FAQ Answer Drafter from Ticket reads the current support ticket or conversation, extracts the customer question and context, and sends it to the AI to draft a clear FAQ-style answer. You can configure the answer tone — helpful, professional, friendly, or concise — and choose the answer length (short, medium, or long). The tool also offers options to include step-by-step instructions, reference screenshots, and include relevant links. The draft is presented in the panel for review before you copy it to your clipboard.
WHERE IT RUNS
This userscript runs inside major customer support platforms including Zendesk, Freshdesk, HelpScout, Intercom, HubSpot, and Salesforce in your browser, powered by the free BotGentz extension. It operates entirely on the page you are viewing — it reads the ticket or conversation from the page and sends it to the AI backend for drafting. All AI processing happens remotely, but your ticket data is only sent for the purpose of generating the answer.
HOW TO USE
Install the BotGentz extension and ensure you have an active subscription, then install this userscript from the BotGentz catalogue. Navigate to any support ticket or conversation on a supported platform — Zendesk, Freshdesk, HelpScout, Intercom, HubSpot, or Salesforce. Open the tool panel, select your desired answer tone from the dropdown, choose the answer length, and toggle the options to include step-by-step instructions, screenshots, or links. Click "Draft Answer" to generate an FAQ-style answer. The tool will display the original ticket and the drafted answer. Review the draft, then click "Copy Answer" to copy it to your clipboard, or "Regenerate" to try a different version. You can also paste custom ticket text into the manual input field.
HOW IT WORKS UNDER THE HOOD
The script first attempts to extract the ticket content using WebMCP if available — the new W3C proposal for structured browser tools — which allows direct, typed access to ticket data without DOM scraping. If WebMCP is not available, the script falls back to a multi-strategy DOM extraction approach, scanning for ticket content using platform-specific selectors like .ticket-content, .comment-body, .ticket-description, .thread-content, .conversation-message, and .case-detail. It also extracts the ticket subject when available using selectors like .ticket-subject and .subject. The extracted ticket content is sent to the AI backend via a secure API call with your subscription key. The AI processes the input with a system prompt that instructs it to generate a clear FAQ-style answer with the specified tone and length, optionally including step-by-step instructions, screenshots, and links, and caps the output at 1,024 tokens. The response is presented in the panel for review.
THE PANEL
The tool runs in the BotGentz panel, a draggable floating interface that stays on top of the page. You can drag the panel by its header, collapse it to a small bubble, and resize it. The panel remembers its position per site, so it stays where you left it when you return to your support platform. Press Escape to close the panel when you are done. The panel includes settings for tone, length, step-by-step, screenshots, links, and auto-copy, a display area showing the original ticket and the drafted answer, and action buttons for drafting, copying, regenerating, and saving settings.
PLEASE NOTE
This tool requires the free BotGentz extension and an active subscription to the AI service. AI-generated answers should be reviewed before use — they are drafts, not final responses. The tool works only on the current page and may not detect all tickets depending on platform structure. Support platforms frequently update their interfaces — if the tool stops working, check for an updated version or report the issue. Your ticket data is only sent to the AI backend for the purpose of generating the answer; no data is stored permanently. The manual input field can be used as a fallback for unsupported platforms or when automatic extraction is incomplete. Always verify AI-generated answers for accuracy before sending to customers.