Email Apology Drafter
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
Email Apology Drafter reads your email or message thread to identify situations requiring an apology—mistakes, delays, misunderstandings, service issues, or errors—then generates a sincere, professional apology reply draft. Choose your apology style: Formal (structured, professional accountability), Personal (warm, heartfelt, conversational), or Brief (concise, direct). Toggle explanation inclusion to provide brief context for what happened. Toggle remedy inclusion to offer specific next steps or make things right. The AI generates a complete, context-aware draft that acknowledges the issue, takes responsibility, and maintains a respectful, professional tone—saving you time and helping you rebuild trust with customers, colleagues, or clients.
WHERE IT RUNS
Any webpage with email threads, message conversations, or correspondence requiring an apology—Gmail, Outlook, Yahoo Mail, LinkedIn messages, Slack threads, Zendesk, Intercom, and more. The script scans the page for conversation context: subject lines, sender information, message bodies, and situation-relevant keywords. No site-specific configuration needed; the detection algorithm adapts to the page structure automatically.
HOW TO USE
Install the script and navigate to any email where you need to apologize. Click "Generate Apology" in the panel—the tool extracts the conversation context and sends it to the AI. Choose your apology style (Formal, Personal, or Brief). Toggle explanation and remedy on or off. The draft appears in the panel. Review it, edit if needed, then click "Insert" to place it directly into your reply field, or "Copy" to paste elsewhere. Settings persist per site and globally—the tool remembers your style, explanation, and remedy preferences. Keyboard shortcuts: Ctrl+Shift+A to generate, Ctrl+Shift+R to regenerate, Ctrl+Shift+I to insert.
TECHNICAL MECHANISM
The script extracts email content using a cascading DOM selector strategy: it targets subject lines (h1[data-thread-perm-id], .hP, .subject), sender information (.gD, .go, [email]), and message bodies (.ii.gt, .a3s, .msg-body, [role="article"]). Collected text is concatenated with labels into a structured input. The AI prompt includes the full thread content, apology style (formal/personal/brief), explanation toggle, and remedy toggle. Style mapping guides tone: formal = structured professional accountability; personal = warm, heartfelt conversation; brief = concise, direct apology. The model generates a draft that acknowledges the issue, takes responsibility, and includes explanation and/or remedy based on toggles. The response is displayed in a textarea with Insert and Copy buttons. Reply insertion uses native value setting with both "input" and "change" events for React/Vue compatibility. The script prefers WebMCP (navigator.modelContext) when available, falling back to DOM scraping when not.
THE PANEL
The tool runs inside BGPanel, a lightweight UI system built into the BotGentz extension. Drag the panel by its header to reposition it anywhere on screen—it snaps to edges and remembers its position per site. Click the header to collapse the panel into a small bubble; click again to expand. Resize the panel by dragging its bottom-right corner. Press Escape at any time to close the panel. The panel stays out of your way but is always accessible via the extension's toolbar.
PLEASE NOTE
Requires the free BotGentz browser extension and an active monthly subscription—the AI backend uses credits for each generation. One generation per click; regenerate counts as a new generation. The script reads only what is visible on the page—it cannot access iframes or shadow DOM. AI-generated apologies are suggestions—always review and edit before sending. No email content is stored or shared beyond the API request; all processing is ephemeral. The tool's apology style guides the AI's tone but actual wording may vary—review the draft before use. Sites change their markup over time; if detection fails, check for updates or use the tool on a page with clearly visible apology context.