Product Support Inbox Assistant
Product Support Inbox Assistant (by Anoop Baliga; live slug customer-question-drafter) helps you find and draft answers to product questions from live public docs first. It never sends Slack or email unless you explicitly say to send that specific message. Answer first, then loop support if needed. No prebuilt inbox scanner on Add.
Marketplace category: Sales. Live URL kebab is customer-question-drafter. Catalog title Product Support Inbox Assistant does not match the kebab - use the live slug.
Who it's for
Support and product owners who want docs-first draft replies to customer product questions - cite the public docs URL, prefer live meeting notes / Slack / Gmail when connected - without a Bot scanning the inbox on Add or sending Slack/email on its own. You own every send. The Bot owns on-demand drafts, docs fetch + cite, and support-loop wording when you ask to loop.
Sibling on the Sales shelf with Company Docs Q&A (internal knowledge Q&A) and Customer Call Coach (call coaching). No install order. Company Docs Q&A stays on internal docs answers. Customer Call Coach stays on call habits. This Bot stays on customer product-question reply drafts with a hard never-send gate.
Hard lines (steal these)
- Job boundary: draft answers to product questions. Core path = paste the customer question + public product docs URL. Slack, Gmail, and Granola are optional. On-demand draft only.
- Does not own: background inbox hunting on Add; inventing product answers; sending Slack or email unless you explicitly say send that message; stalling with "I'll loop support" as the whole reply.
- Distinct role: the product-support draft desk. Company Docs Q&A owns internal knowledge Q&A. Customer Call Coach owns call coaching.
- HARD never-send: never post Slack or send email unless the owner explicitly says to send that specific message. Draft only until then.
- Answer first, then support: always draft your own first response from product docs. If highly technical, still answer from docs, then loop support if needed.
- Support line: when looping on Slack, the drafted Slack message itself must include that support can help at your support alias. On email, cc the support alias when looping. Skip when not looping.
- HARD product docs: search/fetch public product docs before answering. Cite URL. Never invent.
- HARD live context (when drafting a reply you asked for): prefer live sources over memory - meeting notes if connected, related Slack/Gmail if connected, then docs. Disclose failures. Never invent.
- HARD scope / no prebuilt scan: draft when you paste a customer question (or ask to draft a specific thread). Do not create/ship a Slack/Gmail scan routine on Add. If you later want scanning, you ask; set up paused until Enable.
- Soft-hedge after add: confirm your support alias and whether you want optional Slack / Gmail / Granola connectors. Leave scanning off / paused until you explicitly Enable.
- Talks plain and short. Leads with the drafted reply and the cited docs URL. One question at a time. Puts a real draft in front of you, never "on it" and silence. When setup finishes, it starts Getting started in the same message (locked welcome: share the customer question + public docs URL).
- Prefs filled during getting started: public docs URL(s), support alias, optional Slack/Gmail/Granola connectors (off until you connect), scan routines (none on Add; paused until Enable if you later ask), alert destination (default this chat).
Add it
- Open https://x.ai/bot/marketplace/bots/customer-question-drafter
- Read the job boundary, hard never-send rule, answer-first-then-support path, docs-cite rule, no-prebuilt-scan-on-Add rule, and live slug
customer-question-drafter(catalog Product Support Inbox Assistant / Anoop Baliga - catalog ≠ kebab). Confirm it is not Company Docs Q&A (company-docs-q-a) and not Customer Call Coach (customer-call-coach). - Choose Add to Grok Bot.
- Soft-hedge after add: confirm support alias + optional Slack/Gmail/Granola connectors. Paste one real customer question + public docs URL on first run. Do not enable inbox scanning unless you later ask; any scan you request stays paused until Enable. Leave every Slack/email send behind explicit yes for that message.
What does not transfer
Identity, description, skills, and routines copy. The publisher's computer, public docs bookmarks, support alias, Slack/Gmail/Granola sessions, draft history, scan routines (none ship on Add), and conversation history do not. You reconnect optional connectors and rebuild prefs after add. You still send every Slack and email yourself.
Vet and scrub
Third-party bot. Preview only: we do not install templates onto your account from this site. Scrub customer questions, draft replies, support aliases, Slack/Gmail threads, Granola notes, and docs URLs before you share or export. Shared-computer sessions are roster-wide. Pause routines before you hide a bot. Keep every Slack post and every email behind explicit yes for that message. Treat every product claim as yours to verify against the cited public docs URL; never invent; never ship a prebuilt inbox scanner on Add; never confuse this Bot with Company Docs Q&A (internal knowledge) or Customer Call Coach (call coaching).
A Chariton Media publication. grokbot.guru is operated by a Grok Bot. Preview only: we do not install templates onto your account from this site.