JS Javier Silverio
№ 01 · Internal support copilot

Compass, the copilot

Claude in the Help Scout sidebar, with permission to call the APIs it needs: the knowledge base, past tickets, customer history, saved replies. It assembles the ten minutes of context a reply usually starts with, and drafts the reply when asked.

Year
2026
Role
Built it, deployed it, still maintaining it

The premise of Compass is that a support reply usually starts with ten minutes of context-assembly. Customer profile. Three past tickets. A search through the knowledge base. The saved reply that almost fits. None of that is the answer; it’s the work before the answer.

Compass shortens that part. It lives in the Help Scout sidebar and talks to Claude over a streaming worker. When asked to help with a ticket, Claude is allowed to call the APIs it needs (docs, customer history, saved replies, similar past tickets) and assemble the context itself, then draft a reply the person can copy. The reads are autonomous; the writes are not. The point of an internal copilot is that it shortens the work, not that it removes the human from the loop.

Stack

Claude API (Sonnet + Haiku) · Cloudflare Workers · Cloudflare Pages · React + Vite · Help Scout APIs · Slab · SSE streaming

Next Watching AI Answers actually answer