What’s new

Custom domains and white-label just moved to Pro. Features that used to need the Team plan are now included on Pro, and email-to-ticket joins them as part of the same tier.

• Custom domain on Pro. Host your support pages on your own domain.
• White-label on Pro. Your brand on the widget and portal, no DeskCrew mark.
• Send from your domain on Pro. Replies go out as [email protected].
• Email-to-ticket on Pro. Forward your support inbox and every message becomes a ticket, with an AI draft grounded in your knowledge base.

Team keeps its scale advantages: unlimited conversations, multi-widget, outbound webhooks, a larger AI resolution allowance, and priority support. Your free trial still includes everything, so you can try all of it before you pick a plan.

Your customers already email you. Now that email can become tickets, answered by AI, without changing your address.

Every workspace now has its own inbox address on the Install page (like [email protected]). Forward [email protected] to it and every message becomes a ticket, with an AI draft grounded in your knowledge base waiting for your approval.

• Works with any email provider. Copy-paste setup guides for Gmail, Google Workspace, Microsoft 365, cPanel, and Cloudflare are right there on the Install page.
• Pick your own address. Rename the handle to whatever you like, and copy it with one click.
• No log digging. The one-time verification email your provider sends lands right in your DeskCrew inbox as a ticket, so you just click the link.
• One site or many. Forward several addresses into one workspace, or give each of your sites its own workspace and inbox address.

Find it under Dashboard → Install → "Turn your support email into tickets."

Most customers who hit a bug never tell you. They just leave. Signals flips that around: your app's errors become support tickets, so you reach out before the complaint.

How it works. The DeskCrew widget on your site captures JavaScript errors automatically, and your backend can send server errors to our API (Sentry-style payloads welcome). Identical errors are deduplicated into one error group. 500 users hitting the same bug is one signal with an affected-user count, not 500 rows of noise.

Proactive support, human-approved. When a signed-in, identified user hits an error, DeskCrew opens a ticket for that specific person and. With AI drafts on. Prepares a reach-out reply grounded on your knowledge base. The draft waits in your approval queue; nothing sends without a human saying so. Your customer hears "we saw checkout hiccup. Here's a workaround" before they've decided to be annoyed.

Built for signal, not noise. Per-workspace ignore lists, a daily capture cap, and sampling for high-volume errors keep the board readable.

Find it under Signals in your dashboard sidebar. Off by default. Enabling it is one click, and the full guide is in the knowledge base.

Getting started with DeskCrew is now measured in minutes, not menus.

Meet your widget before you install anything. Every workspace now gets a hosted demo page. A little storefront running your live widget, with your colors and greeting. Open it from the dashboard, start a chat, say anything: the message lands in your inbox as a real ticket. That's the whole product loop, experienced before you've touched your website.

A checklist that checks itself. The new Get-started card on your dashboard Home tracks five steps. Meet your widget, reply to your first ticket, install on your site, turn on AI answers, invite your team. And each one completes automatically when the real thing happens. No "mark as done" buttons; the software doesn't take your word for things it can verify.

Never an empty inbox. New workspaces come with a friendly demo ticket (replying to it is the tutorial) and a published starter article, so switching on AI answers works instantly instead of pointing at an empty knowledge base.

One-click AI. Turning on AI answers is now a single click on the checklist, with the cost limits stated right there.

Existing workspaces see the card too. Mostly pre-checked, and dismissible in one click if you already know your way around.

Your DeskCrew chat widget now speaks 10 languages, so you can support visitors in their own language.

Pick a fixed language for your widget, or set it to Auto and it will match each visitor's browser automatically. Supported today: German, French, Spanish, Portuguese, Italian, Dutch, Japanese, Korean, Chinese, and Polish. With English as the default.

Prefer your own wording? You can now override any individual piece of widget text with custom copy.

Set it under Dashboard → Install → Widget language. And your AI replies now answer each customer in the language they wrote in.

A batch of quality-of-life improvements across the desk:

• Ticket controls: change status, priority, and assignee right from the ticket view, and write replies in Markdown with a live preview.
• Reply alerts for everyone: customer replies on unassigned tickets now notify workspace admins, so a follow-up can never slip by silently.
• Accurate usage meters: the Billing page now shows the exact AI allowance that applies to your plan (including trials), plus any overage in dollars for paid plans.
• Trial emails: a heads-up before your free trial ends and a summary when it does, so the switch to the Free plan is never a surprise. (Both respect your notification preferences.)
• Smoother onboarding: new workspaces start with the chat widget (works instantly on any site), and returning sign-ins land on your dashboard instead of the setup checklist.
• Clearer guidance for AI agents: agents connecting over MCP or x402 now get plain-language explanations when they hit a rate limit, including how limits reset and how to get steadier access.

The chat widget's AI assistant is now conversational. Say "hi" and it greets you back; ask "are you a bot?" or "what can you do?" and it answers plainly. Instead of flagging a friendly hello for the support team.

Real questions still work exactly as before: answered instantly from your knowledge base with citations, and handed to a human whenever the KB doesn't cover it. The assistant still never invents an answer.

We also renamed the setting so it's easier to find: Dashboard → Branding → "AI assistant (chatbot + drafts)": one switch for chat answers and email draft replies.

Press ⌘K (or Ctrl-K) anywhere in the dashboard to open the new command palette: live search across every page and individual settings, with arrow keys + Enter to jump.

It matches by concept, not just names. Type "logo" to land on the logo upload, "cancel" for subscription cancellation, "chatbot" for the AI assistant switch, "invite" to add a teammate. New settings join the search automatically as we ship them.

39 install guides, one directory. Every major platform. Wix, Squarespace, Webflow, Shopify, Ghost, Next.js and 30+ more. Now has a step-by-step DeskCrew install guide at deskcrew.io/integrations.

WordPress plugin. Our official plugin is headed to the WordPress.org directory: paste your widget key in wp-admin and you're live. It authorizes your domain automatically and can turn Contact Form 7 submissions (and optionally comments) into tickets.

For AI agents: a new tenant-agnostic paid tool, draft_support_reply ($0.05). Any agent can buy a professional support-reply draft with no account, plus a new quickstart at deskcrew.io/agents.

Shopify: native app in development; the theme snippet works today (guide).

DeskCrew's authenticated MCP server now exposes create_kb, update_kb, and create_changelog tools, so an AI agent can populate and maintain your help content natively. Point it at https://deskcrew.io/api/mcp with an mcp_ credential.

Enable the write tools per credential on the Agents page; they're off by default. The anonymous agent door deliberately cannot write content. Only your own credentials can. Which keeps a random agent from editing your docs.

You can now mint scoped API keys in Settings → API Keys and manage your knowledge base and changelog over a REST API. No database access required.

Hand a key to your own AI tool (Claude Code, ChatGPT, or a script) and it can create and update help articles and changelog entries with a simple Authorization: Bearer dk_… header. Keys are scoped per action (kb:write, changelog:write, and more), shown once, and can be rotated or revoked anytime.

You can now upload a logo and set your workspace's display name in Settings → Branding. Your logo and name render on the chat widget, the public help board, and every customer email. So support looks like your brand, not ours.

Logos are served from a global CDN and re-encoded on upload for safety (PNG, JPEG, or WebP; SVG is rejected because it can carry scripts). Removing the "Powered by DeskCrew" footer is available on paid plans.

DeskCrew is now published on the Model Context Protocol registry as io.deskcrew/support, so any MCP-aware client or agent can discover and connect to it automatically. Point your agent at https://deskcrew.io/api/mcp/{tenant} to get started.

The agent payment layer settles on Base, Polygon, Sei, and Solana. Agents pay per tool call in USDC using the x402 standard, with no account and no API key. Pick whichever supported chain you already hold USDC on.

The 402 challenge itself always lists the chains currently accepted, so trust that over any page, including this one.

The embeddable widget now has a Home screen, a Messages inbox, a searchable Help center, a product Updates feed, and a Feedback board with voting. All inside an isolated Shadow DOM that drops onto any site without touching your styles.