OttoBot
OttoBot is a per-organization chat surface inside Phoenix. Unlike the public OttoBot at phoenix.hginsights.com/ottobot — which is shared and runs against generic data — your org's OttoBot is tuned to your Salesforce, your Confluence, your persona. It uses your members' Phoenix identities, so what each user sees respects the access controls you've already set up in Phoenix.
Quick start
Once OttoBot is enabled for your organization, you'll find it in the Phoenix sidebar at:
https://phoenix.hginsights.com/organizations/<your-org-slug>/ottobot
If you don't see "OttoBot" in your sidebar, OttoBot is not enabled for your organization yet — see Requesting activation below.
Sending your first message
- Click OttoBot in the sidebar (or navigate directly to the URL above).
- Type a question in the input box and press Send. A few starter prompts are listed under the empty state to give you an idea of what kinds of questions OttoBot is good at.
- The response streams back token-by-token. Markdown is rendered (tables, lists, bold, links).
- To start a fresh question, just send another message — OttoBot replaces the in-progress stream cleanly.
Example prompts
OttoBot is most useful for questions that span your org's data:
- "What were our top accounts last quarter?"
- "Show me technographic data for Cisco."
- "Summarize this week's pipeline movement."
Requesting activation
OttoBot is provisioned per-org, on request. To request activation for your organization:
- Email Phoenix@hginsights.com with your org name and a brief description of what you'd like OttoBot to be tuned for (your CRM? your knowledge base? both?).
- Alternatively, talk to your Customer Success Manager — they'll route the request to the Phoenix team.
The Phoenix team will provision a per-org OttoBot pod for your organization, register it in Phoenix, and email you when it's ready. Typical turnaround is 1–2 business days.
Until activation lands, navigating to /organizations/<your-org-slug>/ottobot shows an "OttoBot is not enabled for <your-org>" page with the same email address.
Who can use it
- Org members. Anyone on your team who already has access to your Phoenix organization can use OttoBot. There's no separate seat or per-user setup.
- Not org members. Users who aren't members of your org get redirected to the Phoenix home page if they navigate to your org's OttoBot URL — they never see chat content or even confirmation that it exists.
- Read-only superadmins. Phoenix superadmins who are temporarily "acting as" your org without being a member see a notice on the dashboard rather than the chat UI. OttoBot acts on real user identity, and the read-only acting-as mode doesn't have a per-user data context.
What OttoBot can and can't do
Can:
- Answer questions grounded in your org's data (whatever data sources your org has connected to Phoenix).
- Render markdown responses — tables, lists, links.
- Stream long answers progressively.
Can't (today):
- Carry conversation history across sessions. Each message is standalone for now — conversation memory is on the roadmap.
- Be embedded in your own application yet — that's coming in a separate phase (see iframe embedding below).
Privacy & access control
OttoBot calls Phoenix MCP on your behalf, using your Phoenix identity. That means:
- Anything OttoBot can answer, you can already see in Phoenix.
- Org members can't see another member's private data through OttoBot — the same access controls Phoenix enforces elsewhere apply here.
- Chat content is not shared across orgs. Your org's OttoBot is a dedicated instance tuned to your data.
Error messages
| What you see | What it means | What to do |
|---|---|---|
| "Your session expired — please refresh the page." | Your Phoenix session timed out mid-chat. | Reload the page; you'll be prompted to sign in again. |
| "You don't have access to this organization's OttoBot." | You're signed in but not a member of the org in the URL. | Sign in with the right account, or ask an admin to add you. |
| "Sending too fast — wait a moment and try again." | You've hit the per-user rate limit (50 chats/minute). | Wait a few seconds; the limit resets quickly. |
| "OttoBot is temporarily unavailable. Please try again in a few minutes." | The per-org OttoBot pod isn't responding right now. | Wait a few minutes; if it persists, email Phoenix@hginsights.com. |
Iframe embedding (coming soon)
The current OttoBot lives inside Phoenix. A future release will let you embed OttoBot directly in your own internal portal / CRM / Notion page, with your customer host page providing the auth handshake. That work is tracked separately; if you're interested in early access, mention it when you email Phoenix@hginsights.com.
Troubleshooting
The sidebar doesn't show "OttoBot" for me. It's only surfaced when OttoBot is enabled for the org in your current URL. Either activation hasn't been completed yet (email Phoenix@hginsights.com) or you're navigating in a different org's context — check the org switcher at the top of the sidebar.
I see the chat UI but every message returns "temporarily unavailable". The per-org pod is down or unreachable. Email Phoenix@hginsights.com with the time of the failure and we'll investigate.
A response includes garbled markdown. OttoBot streams responses progressively; partial markdown can look odd until the full response arrives. If a completed response still looks wrong, email us with a screenshot.