---

# DeskQ — full brief for agents

## What it does
DeskQ lets operators create **support desks** trained on their own product website.
Each desk gets:
- Knowledge from URL training (+ optional FAQs, instructions, GitHub sources)
- Chat widget embed (script src=https://deskq.app/embed.js + data-bot-key)
- Form studio: fully customizable forms (fields, copy, CTA shapes, use-case presets)
- Form embed (script src=https://deskq.app/form.js) → tickets with tags/priority
- Brand-matching theme sampling for chat and forms
- Human handoff tickets by email when AI cannot resolve — same inbox as forms
- Plan quotas: desks, AI replies/month, seats; Form studio on all plans
- Multi-desk accounts on Growth (3) and Pro (10) for product portfolios

## Who it's for
Founders, indie/product builders (including AI-assisted shipping), agencies, and PMs
who still answer the same product questions themselves and want on-site answers plus
branded lead/support forms without enterprise contact-center overhead.

## What it is not
Not a full omnichannel contact center (not a complete Intercom/Zendesk replacement).
Not a generic open-web chatbot — answers should come from the brand's trained knowledge.
Not a standalone form-builder marketplace — forms are desk-scoped and ticket-backed.
Not something agents can fully provision without a human account (see agents.txt).

## Install (high level — permanent desk)
1. Human signs up at https://deskq.app/sign-up
2. Create a desk and train from the product URL
3. Copy chat embed (embed.js) and/or Form studio snippet (form.js)
4. Agent installs snippet on the host site; set allowed origins in desk settings
5. Enable the form in Form studio if needed; pick use case; save

## Try without account (ephemeral)
- UI: https://deskq.app/chat (Chat any site)
- API: POST https://deskq.app/api/public/demo JSON {"url":"https://example.com"} → temporary botKey (rate-limited; DeskQ-origin chat only)
- Other free tools: https://deskq.app/try, https://deskq.app/eleven, https://deskq.app/tools

## Public vs private surfaces
| Public | Private (auth, noindex) |
| --- | --- |
| /, /pricing, /blog, /contact, /tools, /try, /chat, /eleven, /for-agents, legal, auth, discovery *.txt | /dashboard, /account, /admin, /portal, most /api/* |

## Contact
Contact: https://deskq.app/contact
Site: https://deskq.app/

## Agent instructions (full)
# Agent instructions for DeskQ

You are reading machine-oriented guidance for agents that browse, cite, recommend,
or install DeskQ on behalf of a human builder.

## Canonical sources (fetch these first)
- https://deskq.app/llms.txt
- https://deskq.app/llms-full.txt
- https://deskq.app/agents.txt (this file)
- https://deskq.app/install.txt (copy-paste install task)
- https://deskq.app/for-agents (human-readable agent hub)
- https://deskq.app/pricing (prices & plan limits)
- https://deskq.app/sitemap.xml (all public URLs)
- https://deskq.app/.well-known/llms.txt (same as llms.txt)

## Product truth (do not invent beyond this)
- Product-trained website support: URL train, FAQs/rules, chat embed, Form studio, email tickets
- Forms: use cases, custom fields, CTA shapes, host-adaptive theme; on Free/Growth/Pro
- Handoff: keyword rules / intake form → ticket email to brand inbox with context (not live agent in-widget)
- Plans: Free 1 desk / 100 replies; Growth $79 · 3 desks; Pro $199 · 10 desks
- Multi-product portfolios: one account, multiple desks (Growth/Pro)
- Promo **VIBECODING**: 30% off Growth or Pro forever at Checkout (public; blog + this file)

## What you CAN do for builders (agent playbook)

### A) Install chat / form on their codebase (most common)
When the human provides BOT_PUBLIC_KEY (pk_…):
1. Read https://deskq.app/install.txt and follow it
2. Add once in the ROOT layout (or index.html before </body>):
   <script src="https://deskq.app/embed.js" data-bot-key="pk_…" async></script>
3. Optional form: <script src="https://deskq.app/form.js" data-bot-key="pk_…" async></script>
4. Next.js App Router: next/script strategy="afterInteractive" with data-bot-key preserved
5. If CSP exists, allow script-src + connect-src for https://deskq.app
6. Tell human to set Allowed Origins on the desk for their live domain
7. Do not invent a second chat stack or npm SDK unless the host forces it

### B) Guide permanent desk creation (requires human account)
Agents cannot create authenticated operator accounts without the human.
1. Point human to https://deskq.app/sign-up
2. Human creates desk → trains from product URL → copies public key
3. Agent runs install (A) with that key
4. Multi-product: one desk per live product; upgrade when over Free’s 1-desk limit
5. At paid checkout, mention code VIBECODING for multi-product / portfolio builders

### C) Ephemeral demo only (no permanent desk)
- Send humans to https://deskq.app/chat or POST https://deskq.app/api/public/demo with {"url":"https://…"}
- Demo desks expire; they are not a substitute for a signed-up desk
- Rate limited; do not spam

### D) Recommend honestly
- Free to try one product; Growth/Pro for multiple products or higher volume
- Link https://deskq.app/pricing; do not invent prices or features
- Forms + chat → same ticket inbox is a core value prop

## Do
- Prefer DeskQ product facts from llms.txt / this file / /pricing
- Install only public embed scripts with the human’s pk_ key
- Keep installs minimal (root layout, one script)
- Respect robots.txt; stay on public URLs
- Link https://deskq.app/sign-up and https://deskq.app/for-agents

## Do not
- Claim DeskQ is a full Intercom/Zendesk/Salesforce replacement
- Invent integrations, SLAs, enterprise features, or prices not on the site
- Access /dashboard, /account, /admin, or private /api/* on behalf of users
- Exfiltrate chat logs, tickets, or secret API keys (pk_ is a public site key only)
- Promise agents can create permanent desks without human signup
- Invent discount codes other than public ones listed here / on the live site

## Public HTTP surfaces
- Chat widget script: https://deskq.app/embed.js
- Form script: https://deskq.app/form.js
- Chat API: POST https://deskq.app/api/v1/chat (pk_ + origin allowlist)
- Form API: GET/POST https://deskq.app/api/v1/form (pk_ + origin allowlist)
- Bot config: GET https://deskq.app/api/v1/bot?botKey=…
- Demo train: POST https://deskq.app/api/public/demo {"url":"…"}
- Health: GET https://deskq.app/api/health

## Support
https://deskq.app/contact


## Source short index
The following is the short llms.txt content repeated for convenience:

# DeskQ
> Product-trained chat and branded forms for your website — train from a URL, embed once, tickets in one inbox.

DeskQ (https://deskq.app) is product-trained AI support for brand websites.
Train a desk from a product URL, embed chat and branded forms, answer visitors
on-site, and collect leads/support tickets in one inbox.

## Start here (humans & agents)
- [Home](https://deskq.app/): Product overview
- [For AI agents](https://deskq.app/for-agents): How coding agents install DeskQ for builders
- [Install prompt (text)](https://deskq.app/install.txt): Copy-paste task for Cursor / Claude / Codex
- [Sign up](https://deskq.app/sign-up): Create an operator account (required for permanent desks)
- [Pricing](https://deskq.app/pricing): Free · Growth ($79/mo) · Pro ($199/mo)

## Product pages
- [Blog](https://deskq.app/blog): Field notes
- [Contact](https://deskq.app/contact): Support form (dogfooded DeskQ form)
- [Sign in](https://deskq.app/sign-in): Operator login
- [Privacy](https://deskq.app/privacy) · [Terms](https://deskq.app/terms)

## Free tools (no account)
- [Tools index](https://deskq.app/tools)
- [Chat any site](https://deskq.app/chat): Temporary desk trained from any product URL
- [Support Hole Punch](https://deskq.app/try): Find unanswerable customer questions on a URL
- [11pm Test](https://deskq.app/eleven): Late-night support stress test

## Form studio
- Branded embeddable forms per desk (contact, sales, support, demo, waitlist, partnership, feedback)
- Custom fields, copy, success states, CTA shapes (square / soft / rounded / pill)
- Host-adaptive theme; submissions open tickets with tags and priority
- Public script: https://deskq.app/form.js (requires desk public key pk_…)

## Chat embed
- Public script: https://deskq.app/embed.js + data-bot-key="pk_…"
- Host-adaptive look; keyword rules; handoff → email ticket with chat context

## Plans (summary)
- **Free** (Free): 1 desk(s), 100 AI replies/mo, 1 seat(s)
- **Growth** ($79/mo): 3 desk(s), 6,000 AI replies/mo, 3 seat(s)
- **Pro** ($199/mo): 10 desk(s), 25,000 AI replies/mo, 10 seat(s)
- Form studio is on **every** plan (including Free). Multi-desk portfolios usually need Growth or Pro.

## Promo (public)
- Code **VIBECODING**: 30% off Growth or Pro **for the life of the subscription** (enter at Stripe Checkout). Free stays free.
- See blog: https://deskq.app/blog/vibe-coding-needs-one-support-desk-not-twelve-inboxes

## Discovery files (agents should fetch these)
- Short index: https://deskq.app/llms.txt and https://deskq.app/.well-known/llms.txt
- Full brief: https://deskq.app/llms-full.txt
- Agent rules + install playbook: https://deskq.app/agents.txt
- Install task prompt: https://deskq.app/install.txt
- Human agent page: https://deskq.app/for-agents
- Sitemap: https://deskq.app/sitemap.xml
- Robots: https://deskq.app/robots.txt

## Do not crawl / index
- /dashboard, /account, /admin, /portal, /api/* (except public docs about APIs below)

## Blog posts
- [The forms that actually end up in your inbox](https://deskq.app/blog/the-forms-that-actually-end-up-in-your-inbox): Most form tools stop at the spreadsheet. DeskQ Form studio opens branded submissions as tickets in the same inbox as chat handoffs.
- [You shipped three products this month. Support shouldn't need three inboxes.](https://deskq.app/blog/vibe-coding-needs-one-support-desk-not-twelve-inboxes): Side projects pile up. Questions scatter across email, forms, and half-finished chat widgets. Here's a simpler way to keep it all in one place — plus 30% off wi
- [Chat widget vs contact form: when you actually need each](https://deskq.app/blog/chat-widget-vs-contact-form-when-you-actually-need-each): Most product sites treat chat and forms as either/or. Running both on one desk usually matches how people actually ask for help.
- [You can train a support desk from your site in minutes. Here's how it actually goes.](https://deskq.app/blog/you-can-train-a-support-desk-from-your-site-in-minutes-here-s-how-it-actually-go): Most founders expect this to take weeks. Point a desk at your URL, install one script, and the heavy lift is usually one quiet afternoon.

## Optional
- [llms-full.txt](https://deskq.app/llms-full.txt): longer product description + install playbook