Not another floating orb
Support that reads the room — and the repo.
Support that sits on the product — one desk per app, tickets when humans step in.
- Trains on
- GitHub
- Answers via
- Grok
- Install
- 1 script
“Most chatbots guess. This one has a desk assignment.”
01How the desk works
01
Assign an extension
One bot per product. Name it like a desk line — not a fun cartoon mascot.
02
Hand it the binder
Connect GitHub. We read README, AGENTS, docs, and the routes that matter.
03
Pin the house rules
Add instructions: discounts, tone, when to escalate. Always on, always first.
04
Hang the handset
One script tag. A quiet corner widget. Customers talk; you get the log.
02The only install step
Drop a line into the product.
No SDK. No React tree. Shadow-DOM so your CSS can’t wreck it. Origin allowlists when you’re ready to lock it down.
Get an extension keyinstall.sh · plain htmlbefore </body>
<script
src="https://deskq.app/embed.js"
data-bot-key="pk_ext_••••"
async
></script>03What sits on the desk
- 01 / Grok repliesGrounded in your knowledge — not generic small talk.
- 02 / Repo memoryRe-sync when main moves. Chunked, searchable, cheap.
- 03 / House rulesInstructions always win over user jailbreaks.
- 04 / Conversation logRead threads. Spot handoffs. See what people actually ask.
- 05 / Email pingsResend to your ops inbox when a line opens or escalates.
Ready when you are