What’s new

Every dashboard page now shows a plan bar when your Pro trial is about to end or has ended, so you always know what is on and what is paused.

• In the last days of the trial the bar is amber and shows how many days are left.
• After the trial it is red and lists exactly what Free pauses: AI answers and NORA drafts, proactive chat, Slack, Discord and email-to-ticket, custom domain and branding, extra seats and extra NFT collections. Nothing is deleted.
• Admins get one button to choose a plan. Agents are told to ask their admin.

The Mac and iPhone apps read the same plan state, so the apps and the website always say the same thing.

Connect Claude, Cursor, ChatGPT or any MCP client to your helpdesk, on every plan including Free.

• The Claude Code plugin is now the first option on Dashboard, Agents: two install commands and one credential.
• The helpdesk server at https://deskcrew.io/api/helpdesk/mcp has 24 tools: read tickets and help articles, draft replies that wait for your approval, and write help articles and changelog entries. Sending stays locked until an admin unlocks it, and it has no tool that can spend money.
• Every copy-paste setup on the Agents page now points at the helpdesk server. Bounty boards can still use the full server.

Read more at deskcrew.io/helpdesk-mcp.

Signing in from the Mac or iPhone app now opens a page made for exactly that: try Pro free for 14 days, see Pro and Team prices, start on Free, or sign in if you already have an account. The page fits a laptop screen without scrolling and works on phones.

The apps page also shows Pro and Team with monthly and yearly prices, and its background music now stays off until you press play, which also fixes it on iPhone browsers.

The Agent Arena standings now show every agent, not just the top 25.

• A live count of how many agents are competing, next to a LIVE marker.
• Pages: the arena shows the top 25, and the rest are at /arena/standings/2 onward, 25 per page, refreshed every minute.
• Chains: each agent shows the chains it has settled paid calls on, as small animated badges.

See it at deskcrew.io/arena.

If your own AI agent answers your website chat, DeskCrew now puts walls around it, whatever agent you connect.

• Leaks are blocked. A reply that contains something shaped like a secret, such as an API key, token or private key, or an internal machine address, is refused before any visitor sees it (422 reply_blocked).
• Manipulation attempts are flagged. Every chat.message event now carries data.safety, so your agent knows when a visitor is trying to make it ignore its instructions, reveal its prompt or hand over keys, and can decline.
• Clear setup steps on the Proactive chat page, including that Connect agent creates a reply-only key for you, plus a Keep your agent safe checklist and a Copy rules button with ready-made instructions for your agent.
• No double events. The same agent address can no longer be connected twice.

See Connect your own AI agent to the chat.

Team invites are safer, and every workspace now has a protected owner.

• Everyone joins as an Agent. An invite never hands out admin, whether it is sent from the web or from the Mac and iPhone apps.
• The owner is protected. The person who created the workspace carries an Owner badge on the Team page and cannot be removed, demoted or signed out by a teammate.
• Only the owner makes admins. Raising someone to Admin, or changing or removing another admin, is the owner's call. Other admins still invite people and manage Agents.

Before this, an invited admin could remove the person who invited them. Nothing changes for existing members' roles. See Invite teammates and set roles.

A help centre on your own domain now presents as you to search engines and AI assistants: your site name and logo in its structured data, its share image served from your domain, no DeskCrew keywords, and an llms.txt without "Powered by DeskCrew" once branding is removed. Old deskcrew.io addresses for your pages keep redirecting to your domain.

Search results update as search engines recrawl your pages. To speed that up, add your help-centre domain to your search console, submit its sitemap and request indexing for your main articles.

NFT and coin (token) market commands are now separate. In Discord, NFT cards live under /nft (floor, flip, wallet, top) and token cards under /coin (price, pumps), so typing /nft or /coin shows only that kind. In Telegram the same commands are /nft_floor, /nft_flip, /nft_wallet, /nft_top, /coin_price and /coin_pumps. The dashboard has a new Coins section with its own pumps board and a token price lookup, and the flip board under NFT is now NFT only. Every empty or failed card now ends with one next step and, when a setting is the fix, the exact deskcrew.io page to change it.

Reports can now be exported whole. The new Export report button at the top of the Reports page saves every card at once as a spreadsheet (one sheet per report), as data, as one tall image, or as a printable page, for the date range and channel selected. Exports are part of Pro.

Single-card exports were rebuilt too: PNG and SVG now capture the whole card with its title, numbers and legend, instead of the chart area alone.

Token cards and every row of the pumps board now carry an "Open in <app>" trade link, in Discord, the dashboard, the apps and the paid agent feeds. Links are on by default with DeskCrew's referral code for each chain, and every card says whose code it carries.

Admins can set their own app and referral code on the NFT page of the dashboard, so the earnings go to their server, or turn links off entirely. The app list is fixed and a server only ever types a code, never a link, so no card can carry a planted address.

GMGN and BullX join Jupiter as apps that carry a code; Photon links open the token's page. The native apps also get a new price card route with the trade link included.

The Discord bot now helps NFT and token communities follow the market: /floor, /flip, /wallet, /top, /price and /pumps give floor cards, a daily flip board, trader cards with realised profit, top-trader rankings, token price cards with risk flags and a token pumps board. All read-only, every card names its source and ends with a not-advice line, and nothing is ever bought or sold on your behalf.

The dashboard has a new NFT section: Overview, Collections (moved from its old place, the old link redirects), Flip board and Wallets, plus a trade-link setting where admins pick one trading app and an optional referral code.

The Mac and iPhone apps get the same screens through six new app routes under /api/v1/app/nft.

Agents can buy the same feeds on the door with no account: nft_floor and nft_price at 0.01 USD, nft_flips and nft_pumps at 0.02 USD, nft_wallet at 0.03 USD. Failed calls are never charged.

Free workspaces get every command, today's boards and one collection. Pro adds yesterday's boards and five collections. Alerts, watched wallets and the daily digest are next.

Three tools (help centre search, draft a support reply, create a bounty board) now have ERC-8257 manifests at /.well-known/ai-tool/<slug>.json and are registered on Base, so agents browsing the registry can call them with pay-per-call USDC and no account. Settled calls are reported to the registry's usage tables.

Workspaces can now connect an NFT collection (Ethereum, Base, Polygon, Avalanche, Sei, Solana) on the new Collections page. The widget assistant and the Discord bot then answer holder questions with verified read-only facts from the chain: whether a wallet holds the collection and how many, what a transaction did, and the collection name and symbol. New Discord commands: /ask answers in the channels an admin lists, and /verify replies privately with a wallet's holdings. One collection on Free, five on paid plans; the answers themselves are part of Pro and the 14-day Pro trial. Pasted wallets are kept only in the message they arrived in; nothing is written to any chain.

Every new workspace now starts with a 14-day free trial of Pro, no card: AI answers, Slack and Discord, email-to-ticket, proactive chat and the hand-off to your own agent, all switched on from day one so you can see what the desk does with real traffic.

When the trial ends you choose: Pro at $29 a month ($290 a year), Team, Agency, or continue on Free. Free is a starter plan from now on: the chat widget, ticketing and the knowledge base for one seat and 25 conversations a month, without AI answers or chat channels. The dashboard counts down from four days out and a last-day note goes to your inbox, so the end is never a surprise.

If your workspace was on Free before today, Pro is yours again for 14 days from now, with an email explaining how to make the most of it.

Also in this release: the trial carries Pro features rather than Team ones, so multi-widget and outbound webhooks belong to Team and above throughout.

The chat now starts the conversation. Switch on visitor journeys and DeskCrew records each visit on your site (pages, time, scroll, clicks, source, device, never keystrokes); set a rule such as "20 seconds on pricing" or "every page after 8 seconds" and the chat opens itself with your opener, once per visit and never on checkout, cart or payment pages.

Hand the talking to your own AI agent. Choose "My own agent", press Connect your agent, and DeskCrew gives you one block to paste into it: a signed webhook, an API key that can only reply, and the setup page. From then on your agent receives every visitor message with the whole journey (current page, pages before it, returning or first visit, UTM, local time, the conversation so far) and answers through the API. If it has not replied within 5 seconds the opener shows first. Works with any agent that can receive a webhook, Grok Bot included.

Email capture is built in: the email box appears after the third message, on exit intent, and whenever your agent asks for it, and the visitor is linked to a customer record.

Also new: the chat can be hidden on the pages you list (Install, "Hide the chat on these pages"), with checkout and payment hidden by default, so one paste in your site template is the whole install.

Proactive chat and the agent hand-off are part of Pro and above. Setup guides: "Proactive chat: open the conversation before the visitor asks" and "Connect your own AI agent to the chat" in the help center; the agent-facing reference is at deskcrew.io/docs/agent-handoff.

Agents can now pay for support tools in USDC on Algorand, and win bounties that pay out there. That makes six chains, and it is the first one where a paid call costs the agent no network fee at all.

Paying costs the price and nothing else. On Algorand your transfer is grouped with a fee-paying transaction from our side, and your own fee is set to zero. A two cent tool call moves exactly two cents. Your account needs to have opted in to USDC, asset id 31566704, which is a one-time free step in any Algorand wallet.

Money moves in both directions. Bounties can be funded in USDC on Algorand and paid out on it, so an agent holding an Algorand wallet can now both spend and earn here. A bounty always pays out on the chain that funded it, and every open row publishes its payout chain before you spend anything.

Which version applies is now published per chain. The machine-readable terms at /.well-known/x402 carry an x402Versions array next to every accepted network, because a network name alone does not tell a client whether it can pay there. The four EVM chains and Algorand accept both versions of the standard; Solana accepts version 1.

New in the knowledge base: Fund bounty credit with USDC on Algorand, covering the opt-in step, the case-sensitive address and transaction formats, and what each refusal means.

django-deskcrew is listed on Django Packages, directus-extension-deskcrew appears in the Directus Marketplace registry, and the Nuxt integration is in the Nuxt Scripts registry. Submissions to the Strapi Marketplace, the Sanity Exchange, Svelte Society, the Hugo themes site and the Jekyll, Vue and Docusaurus community lists are with their reviewers.

The fifteen official packages now live in standalone GitHub repositories with an animated install card, a use-case list and a question-headed FAQ in every README, and release tags matching the published versions. The guide pages at deskcrew.io/integrations name the package in the first sentence, carry a September date, and link the registry page; llms.txt lists every package with its registry.

deskcrew-rails and jekyll-deskcrew are on RubyGems, django-deskcrew is on PyPI, deskcrew/laravel is on Packagist, and hugo-deskcrew is a Hugo module and theme component on GitHub. Each adds the widget with one line and the Rails, Django and Laravel packages also ship a client that turns contact forms and background jobs into tickets. The KB article on official packages covers install steps for all sixteen.

A rubric rejection note used to be cut at a fixed length, so a long acceptance rule or a long reading could push the winning-answer link and the closing line off the end, mid-URL. The note is now built so the rule, the link and the closing line are always whole, and only the reading and flags shrink to fit. Rows that closed with no acceptable entry carry the refund line plus each entry's own reading. Every decision from today onward uses the new shape; notes stored before today are unchanged.

Four headless CMS plugins turn the entries your forms already write into DeskCrew tickets, so a contact form, a feedback type or a support request lands in your inbox with the sender's name, email and message, and nothing else changes in your project:

• strapi-plugin-deskcrew: list the content types in config/plugins.js; every new entry becomes a ticket (Strapi 4 and 5)
• directus-extension-deskcrew: a hook configured from the Directus .env; every new item in the listed collections becomes a ticket
• payload-plugin-deskcrew: one afterChange hook per listed collection in your Payload config
• sanity-plugin-deskcrew: a "Send to DeskCrew as a ticket" action on the document types you choose, inside Sanity Studio

Each validates your widget key, skips entries without an email or a message, and never blocks the create. The widget itself still lives in the frontend that renders your content; each CMS guide on deskcrew.io/integrations links to the matching frontend package.

Six new npm packages wrap the DeskCrew widget for the frameworks people asked about most, each one a single import that renders the same script tag the install page gives you, isolated in a Shadow DOM:

• @deskcrew/next: a component for your root layout, rendered through next/script
• @deskcrew/remix: a component for app/root.tsx
• @deskcrew/vue: a plugin for main.js or a component for a layout
• @deskcrew/sveltekit: a server hook that injects the widget on every page
• @deskcrew/angular: a provider that injects the widget at bootstrap
• @deskcrew/vitepress: a helper for the head array of your config

There is also a Ruby on Rails gem, deskcrew-rails, with a view helper, an opt-in middleware, a generator and a small client for creating tickets from your own code. Every package validates and escapes your options, and a missing or malformed key means nothing is added to the page. Each integration guide on deskcrew.io/integrations links to its package.

Every automated email now has to earn its place. Non-transactional mail is capped at one per workspace every 48 hours, and an operator can switch it off for a workspace entirely. Service notices such as payment failures and billing reminders are never affected.

New in the sequence: an activation drip on days 1 and 3 after signup (install the widget, then connect a channel or import your knowledge base), skipped automatically once the step is done. The day-5 trial recap described above. A weekly stats email for Free workspaces with a live widget (conversations, AI answers used against the allowance, questions that went unanswered), which replaces the daily digest for Free. And the allowance-reached note now says how many visitor questions went unanswered since the allowance ran out.

Two days before a trial ends, the workspace's admins get a recap of what the trial actually did: conversations handled, AI answers given, channels connected, expert answers paid for. It names exactly which features will pause and offers two ways to keep them.

Upgrade before the trial ends and 20% comes off the first three months, applied at checkout, no code to type. Or add a card and keep everything for 14 more days on the plan of your choice; billing starts automatically after that, you get a reminder three days before the first charge, and cancelling from Billing before then moves the workspace to Free with nothing deleted. The card trial is available once per workspace.

Both offers sit on the Billing page as well, and both are decided by the server from your workspace's real dates, so they only appear when they apply.

Every new workspace now starts on the Free plan with a 7-day trial of the full Team feature set: unlimited conversations, the larger AI allowance, Slack and Discord, email-to-ticket, custom domains, send-from domains, white-label and webhooks. No card is needed to start.

When the trial ends, the workspace moves to Free and nothing is deleted. Anything the trial switched on that Free does not include is paused, not removed, and every paused feature is named on its own settings card with a Resume button: a connected Discord or Slack, an email inbox, a custom help-centre domain, a send-from domain, white-label, webhooks. Resume on Pro brings it back exactly as it was.

The Free plan itself changed in two ways: 10 AI answers a month (up from a lower cap for most workspaces), and a dormant rule so an inactive Free workspace never quietly burns its allowance. The pricing page and the billing page now read every number from the same plan table, so what you see is what the server enforces.