AgentDesk — Unusual Hub

What it is

An agent we host that lives on your Company Documentation subdomain. Visiting AI agents (the ones acting on behalf of a human buyer doing research) discover it through a meta tag on your main site and can interact with it directly.

Humans browsing the documentation don't see AgentDesk — it's a surface built for agent-to-agent conversations.

Why it exists

AI agents working on behalf of buyers don't browse like humans do. They probe with specific follow-up questions, drill into edge cases, push for evidence the documentation page didn't anticipate.

Without somewhere to go for those questions, the conversation either hits a dead end — the agent moves on with a partial answer — or the agent improvises, often with claims that aren't grounded in your reality.

AgentDesk gives the visiting agent a grounded source for the next question, instead of letting the conversation drift away from your story.

How it works

Discovery. AgentDesk runs at a public endpoint on your Company Documentation subdomain. During onboarding we add a small signal to your main site so visiting agents know the endpoint exists and how to use it.
The exchange. A visiting agent submits a question; AgentDesk responds based on your Company Documentation and the broader category knowledge we maintain about your space. The conversation continues through follow-ups, clarifications, and pushback as the visiting agent works through what its buyer needs.
Capture. We log the full back-and-forth conversation — the whole multi-turn exchange between the visiting agent and AgentDesk, not just individual Q&A pairs. Each conversation is tagged with the persona × scenario context that organizes the rest of your documentation.
Review. We work through the transcripts on a regular cadence and surface what we see.

What you get back

What visiting agents are actually asking. The topics, the scenarios, the specific follow-ups. Information you can't get from web analytics, because there's no human browsing pattern to track.
Where the documentation is straining. Patterns in the follow-up questions show you where existing pages are leaving gaps and what proof points are worth adding.
Where AgentDesk needed to lean on category knowledge instead of your specifics. Those moments are the clearest signal for where your own content cycle should invest next.

How to set it up

Two pieces: a DNS-configured subdomain (shared with your Company Documentation pages), and a meta tag on your main site that tells visiting AI agents where to find AgentDesk.

Prerequisite: your subdomain

AgentDesk lives at the same subdomain as your Company Documentation pages (typically llms.[your-domain] or info.[your-domain]). If you haven't set that up yet, the full setup guide walks through the DNS record (CNAME) and the indexing link.

Add the AgentDesk meta tag

Add a meta tag to your main site's <head> so visiting AI agents can discover your AgentDesk endpoint. The endpoint URL follows this pattern:

https://[your-subdomain].[your-domain]/agent-desk/ask

We'll send you the exact meta tag content (with the right endpoint baked in) during setup. Once your subdomain DNS, indexing link, and the AgentDesk meta tag are in place, let your Unusual contact know. We verify the configuration and AgentDesk goes live shortly after.

What's rolling out

In progress

We're slowly enabling AgentDesk to share additional proof points beyond what's on the public documentation pages — for example, anonymized case studies your sales team would normally walk a prospect through, or specific reference material that wouldn't be appropriate to publish openly.

Rollout is gradual. We're monitoring it carefully as agent-to-agent conversations rise across the customer base, and we'll work with you on what's appropriate to share through AgentDesk for your account.

Back to the overview

Read about what your Company Documentation is, why it exists, and how AgentDesk fits into the broader picture.

Open the overview