Policy Coverage Question Drafter

WHAT IT DOES

AI-powered policy coverage question drafter that creates clear, professional questions for insurance providers. The script reads insurance policy details from the current page—policy type, coverage limits, exclusions, deductibles, and terms—and generates a draft question to ask the insurance provider about specific coverage, exclusions, or clarification. The AI produces a well-crafted question that addresses your concern about what is or isn't covered. You can customize the question type (coverage/exclusions/clarification/claim), tone (professional/clear/formal), length, and toggle inclusion of policy details and specific scenarios. You also describe your specific concern, and the AI incorporates it into the drafted question. The user reviews the output before copying or using it.

WHERE IT RUNS

Works on all insurance policy pages (match pattern *://*/*), including insurance company websites, policy documents, coverage summaries, benefits portals, and any page containing insurance policy information.

HOW TO USE

Install the script and navigate to any insurance policy page. The Policy Coverage Question Drafter appears in the panel. Configure your preferred question type, tone, length, and toggle inclusion of policy details and specific scenarios using the settings controls. Enter a description of what you want to ask about (e.g., "Does this policy cover flood damage?"). Click "Draft Question" to analyze the current page. The AI extracts policy information and generates a clear, professional question. Review the output in the panel. Click "Copy to Clipboard" to copy the question for use in email, phone calls, or contact forms. Adjust the settings and regenerate if you want a different tone or level of detail.

REAL MECHANISM: DOM CONTENT EXTRACTION WITH AI QUESTION DRAFTING AND REVIEW GATE

This script uses a hybrid extraction approach that prioritizes structured content when available. First, it checks for WebMCP (navigator.modelContext), a W3C proposal that exposes structured tools on the page. If available, it calls getContent() to obtain structured policy data. If WebMCP is not present—the common case today—it falls back to DOM scraping using targeted selectors for policy sections (policy-details, policy-summary, coverage-info, policy-type, coverage-limits, exclusions-list, deductible-info, insurance-terms, and policy-document). It also scans for policy keywords (policy, coverage, exclusion, deductible, limit, term, benefit, insured, claim, premium) in paragraphs and headings. The extracted text, along with the user's concern description, is sent to an AI backend via GM_xmlhttpRequest, which processes it with a system prompt that includes the user's question type, tone preference, length, and inclusion preferences. The AI returns a draft question (60-150 words depending on the selected length) that is clear, professional, and addresses the user's concern. The response is displayed in a bordered container for review before copying. Copy-to-clipboard uses GM_setClipboard. All settings (questionType, tone, length, includePolicyDetails, includeScenario) are persisted via GM_setValue. The script enforces a review-before-use pattern: the user must read and approve the AI output before copying it.

THE PANEL

Drag the panel anywhere on screen by clicking and holding the header. It snaps to screen edges when released. Collapse it to a small bubble by clicking the minimize button, and expand it back by clicking the bubble. Resize the panel from any corner. Press Escape to close the configuration panel. Your position and size preferences are saved automatically per site.

PLEASE NOTE

This script requires the free BotGentz browser extension and an active AI subscription for the drafting service. AI-generated questions should be reviewed for accuracy before sending—the AI may misinterpret policy details or generate a question that doesn't match your concern. The script reads the current page content and sends it to the AI backend for processing; no data is stored or logged. Websites change frequently; if the script stops detecting policy content, check for updates to the extraction selectors.