Skip to main content

Demo links

A demo link is a temporary address that opens a conversation with one of your agents in the recipient’s browser. They click it and talk. No account, no API key, no setup on their side — which makes it the fastest way to show an agent to a prospect, a colleague or a client. In the agent list, open the ⋯ menu in the agent’s row and choose Share demo link… — or, in the agent editor, choose Share in the toolbar ⋯ menu. Archived agents have no Share demo link… item. The Share a demo of … window opens, with the agent’s name in the title. It asks for two things:
  • Link lives for — 1 hour, 24 hours, 7 days (the default) or 30 days.
  • Calls allowed — how many conversations the link may start in total. Leave the field empty and the link gets 25 calls; a value above 200 is cut to 200.
Click Create link — the new link appears in the list below. The agent’s variables are not set in this window. If the agent declares any, the recipient sees a form on the demo page with their default values from the agent’s published version and can enter their own — their name or an amount, for example — so the demo talks about them rather than reciting a generic script.
Only a published agent can be shared. A link to an unpublished agent cannot place a call, so the platform refuses to create one. Publish the agent first, then create the link.
If the published version of the agent has provider contract findings, the link is still created and the window lists the findings — so you learn right away that the demo may start reduced or not start at all.

Which agent version a call gets

Every call through the link goes to the agent’s current published version. Publish a new version, and the next call through a link you already handed out goes to it. The link is bound to the agent’s name and does not follow a new name. If the agent is renamed, unpublished or deleted, the demo page shows The demo is temporarily unavailable. The link never opens a different agent instead.

What the recipient sees

The page opens with the agent’s name, the Call details form and two buttons:
  • Start call — a voice conversation; the browser asks for microphone access.
  • Chat without audio — the same conversation in text, no microphone. This button is always available, including when there is no microphone or access to it is denied.
The demo link page: the agent's name, the call details form, the Start call and Chat without audio buttons The form fields are labelled with the agent’s variable names. If the agent declares no variables, the form shows This agent declares no variables — just start the call. instead of fields. During the conversation the visitor can type to the agent in the field at the bottom, and end the conversation with Hang up. Variables are filtered against the agent’s published version: only names the agent actually declares are accepted, and anything else the page sends is dropped. The browser can fill in the contract, never extend it. When a link is no longer usable — expired, revoked, or all its calls used up — the page shows This demo link is no longer active and Ask whoever shared it for a new link. A link that does not exist looks the same. The reason is visible only to you, in the Share demo window. A demo link is a credential handed to someone outside your organization, so its blast radius is limited by design:
  • One link, one agent. It cannot reach anything else in your organization.
  • A call ceiling and an expiry, both enforced atomically — a link cannot overrun its cap under concurrent use.
  • Every start spends one call — both Start call and Chat without audio, even if the connection then fails. A spent call is not returned.
  • One conversation at a time. While a call is running, the link is busy and the next visitor sees Another conversation is going on right now. Try again in a minute. The same answer appears when your organization’s concurrent call limit is exhausted. This refusal does not spend a call.
  • Revocation at any moment. Revoking is immediate and cannot be undone: whoever holds the link can no longer call.
Treat the link itself as the credential. The Share demo window can show the same address again — that is deliberate, so you can re-send a link you already handed out — which also means anyone who can open that window can read a live link. For the same reason the Share demo window and demo links are closed to the Manager and Member roles, reads included. See Roles and access.
Below the form, the Share demo window lists Links to this agent. Each link shows its address, its state (active, expired, revoked, or calls used up), a Calls: N / M counter and its expiry.
  • Only an active link can be copied.
  • Revoke asks for confirmation first.
  • Expired and revoked links stay in the list — it shows everything you have shared.
The state in the list describes the link itself, not the agent: if the agent is unpublished, the link stays active in the list while the demo page shows The demo is temporarily unavailable. The Share demo window: link lifetime, number of calls allowed, and the list of issued links with their states

Demo calls in the history

A conversation from a demo link lands in History as an ordinary call, and you find it there with the All channels → Web filter. A demo runs in the recipient’s browser, so the platform records it on the web channel rather than phone.
The web channel is not only demos. It also holds conversations from the widget on your site and from your own code on the browser SDK — everything that arrives from a browser rather than over a telephone line. If you use both, the channel filter narrows the list to browser calls but will not separate a demo from a widget call; filter by agent as well, since a demo link is always issued for a single agent.
They are ordinary calls in every other respect: transcript, analytics, recording and reports all work as usual — so a demo that went badly can be reviewed like any other conversation.

Embedding the conversation in your own site

A demo link is a ready-made page. When you want the same conversation inside your own product instead, use the browser SDK, published as @hubtalk-ai/web-sdk — a thin wrapper over the web call endpoint of the Web API, with a ready-made widget. How to connect it: Calls from your website.