About BitterDesk
BitterDesk is a standalone agentic help desk for websites and web apps. Outside teams install one widget script, configure how the support agent should answer, collect safe visitor context, and hand conversations to their webhook or team workflow.
How BitterDesk Works
BitterDesk embeds as a single script tag on your website. Each installation is tied to the public hostname visitors use, the agent follows your site-specific support prompt, and the widget collects only the context your team needs to act.
When the agent cannot answer safely, BitterDesk preserves the transcript, source page, contact details, and handoff reason so your team can pick up the conversation with context attached.
What Makes BitterDesk Different
- One-script install: Add the widget to your site without replacing your existing app, storefront, docs, or marketing stack.
- Configured agent behavior: Write the support prompt, boundaries, fallback instructions, and handoff rules for each site.
- Safe intake: Ask for useful context while steering visitors away from passwords, one-time codes, API keys, raw card data, and unrelated personal information.
- Signed handoff: Deliver transcripts and handoff events to your HTTPS webhook with signatures your backend can verify.
- Outside-team first: Bitter-owned sites can dogfood the product, but they are consumers of the same standalone help desk, not the product boundary.
First Consumed by Bitter Properties
BitterDesk can support Bitter-owned properties, and that use proves the same product can handle multi-site routing, conversation handoff, and first-site activation. It is not limited to Bitter sites, Bitter-owned hosting, or any portfolio surface.
Outside teams can install BitterDesk on their own websites and apps with the same one-script widget, custom agent prompts, signed webhooks, and human handoff pipeline the portfolio uses.
Technology
BitterDesk is built around boring, inspectable integration points:
- Widget script: A browser embed that loads asynchronously and checks the configured hostname before sending messages.
- Installation records: Per-site prompt, allowed origin, webhook URL, and activation state.
- Conversation storage: PostgreSQL-backed sessions and transcripts for dashboard review and handoff continuity.
- Webhook delivery: Conversation and handoff events delivered to any HTTPS endpoint your team controls.
Getting Started
To add BitterDesk to your website, create an installation for the exact public hostname visitors use, write the support prompt, add your webhook URL if you want handoffs delivered to your stack, and paste the widget script before </body>.
After the first test message, the dashboard should show the site as connected and webhook payloads should be verified with X-Bitterdesk-Signature before production use.