Skip to main content

Share an Agent

Get an agent into the hands of end users (or yourself, for a quick test).

What you need​

  • An agent created and saved.
  • End users must have an account on the platform to open the link.

Steps​

1. Go to Your AI Agents​

Open the Admin Dashboard and navigate to Your AI Agents.

2. Open the Share dialog​

Two ways:

  1. Click the Share button on the agent's card (always visible).
  2. Click View more dropdown → Share.

The dialog title reads: "Share your ESP Private Agent", followed by the agent's name.

3. Check for warnings​

If the agent has a Knowledge Base that hasn't finished ingesting, the dialog shows:

Knowledge base(s) not yet configured.
The agent will not retrieve data from the knowledge base until successfully configured. Check the status of the knowledge base from the tool configuration page.

If you see this, go to the Tool Configuration page and wait for the KB to reach Configured status before sharing broadly — or share now if the KB isn't critical for first impressions.

4. Test it yourself​

Click Start chatting. The User Dashboard opens in a new tab and you can use the agent as an end user.

Send a few messages and check:

  • The tone and behaviour match the system prompt.
  • Tools are called as expected.
  • KB-backed answers cite the right material.
note

Start chatting requires that your admin account also has end-user access. In deployments where admin and end-user accounts are separate, you may need a separate end-user account to test.

5. Hand it off​

Pick your channel:

  • Copy link — the button copies the share URL. Paste it into Slack, email, or a doc.
  • QR code — for phone or device handoff. Phone users point the camera app at the code; it opens the agent directly.
  • ESP RainMaker Home app — scanning the QR code can assign the agent to an ESP device. See the Mobile App section for details.

About the share URL​

<your-user-dashboard-url>/agents/<agent_id>

The URL and QR code are stable — they don't rotate when you edit the agent. You don't need to re-share after making changes.

Who can chat​

Opening the link doesn't automatically grant access. The recipient needs:

  1. An end-user account on your deployment.
  2. Access to this specific agent (per your deployment's authorization model).

If both are true, opening the URL drops them directly into a chat with the agent.

Common gotchas​

SymptomLikely cause
End user sees "agent not found"Agent was deleted or the URL is wrong. Re-share from the dialog.
End user can't sign inThey don't have an end-user account. Ask your platform admin to create one.
Agent doesn't answer from the KBKB isn't Configured yet. Watch the status; once it flips to Configured, the agent can answer.
QR scan opens the wrong pageCamera apps sometimes intercept. Use the camera's "Open in browser" option, or paste the link directly.

Tips​

  • Test before you broadcast. A 30-second self-test via Start chatting catches most issues.
  • The link is stable. Re-sharing on agent edits isn't needed — the URL doesn't change.
  • Keep a record of agent URLs. If you manage multiple agents, maintain a doc with their names and share URLs.
  • Wait on the KB if it matters. Hold the share until the KB status is Configured if your agent's value depends on it.

On this page