← ClaudeAtlas

support-inbox-agentlisted

Use when doing the daily support-inbox pass - checking the support chatbot inbox for new visitor issues and questions and preparing personalized email drafts for human review. Triggers on "/support-inbox-agent", "support inbox pass", "draft support replies".
sitespeakai/support-inbox-agent · ★ 0 · AI & Automation · score 62
Install: claude install-skill sitespeakai/support-inbox-agent
# Support Inbox Agent Read new threads from the support inbox, investigate each issue or question until verified, then create one personalized email draft per visitor. Drafts only - a human reviews and sends. Safe to run daily (or more often): the state file prevents duplicate drafts. ## Placeholders - fill these in - `<INBOX_ID>` - your support chatbot/inbox id - `<EMAIL_ACCOUNT>` - the email account drafts are created in - `<DOCS_URL>` - your public docs, used to verify how-to answers - `<REPO_PATHS>` - local paths to the codebases the agent may read when investigating - MCP tool names below are examples (SiteSpeak inbox, Sentry, Superhuman). Swap them for your stack's equivalents. ## Config - State file: `state/processed.json` - JSON object mapping `visitor_id` to `{ "processed_at": ISO UTC, "action": "drafted" | "skipped", "reason"?: string, "email"?: string, "draft_id"?: string, "draft_thread_id"?: string }`. Missing file = empty object. ## Steps ### 1. Load state and list threads Read the state file. Then list open inbox threads (e.g. `list_inbox_threads` with `chatbot_id: <INBOX_ID>`, `status: "open"`), newest first. Keep a thread when BOTH: - its last activity is within the last 7 days (self-heals skipped days), AND - the thread is not in state, OR its last activity is later than its `processed_at` in state (the visitor wrote again since the last run - this applies to previously skipped threads too) If nothing qualifies, report "No new inbox activity" and s