Team Agents

Early access. Invites, citations and the reports-never-decides rule all work today. Shared administration and per-source ownership are on the roadmap.

When a Team Agent can't answer, it says so and tells your colleague this one's for you. The Escalation page is where you decide when it does that, and what it says while it does — see Handing over to a person.

What an invite does not include. An invited colleague can ask a Team Agent and read its answers. They do not get an inbox of what other colleagues asked it — a Team Agent keeps no per-person trail, so it never appears under Shared with you in anyone's twin switcher. On a Support Agent, where the conversations are with your customers rather than your colleagues, an invited colleague can open the Inbox: see who can open a conversation.

A Team Agent is you, for your colleagues. It answers from the internal material you give it — project notes, decisions, how-we-do-things — in your voice, so the fourth person to ask "where are the Meridian call notes?" gets the answer without you.

One rule defines it: it reports, it never decides. Ask it what you wrote and it tells you. Ask it to approve something, commit to a date, or make a call on your behalf, and it says plainly that that's yours to decide. A colleague acting on a commitment your agent invented is the worst thing that could happen here, so it can't happen.

Who can read it#

Only people you invite. An invite is just an email address — no codes, no links: access starts the first time your colleague signs into hiy with that address and opens the agent. Everyone else, including anyone who guesses the URL, gets a 404 — for them it doesn't exist.

hiy does not email them. Beside every address you have invited there is a Copy invite button: it gives you the message to send yourself, with the sign-in link, the address to sign in with, and the agent's own link to ask it things. That last one matters — a Team Agent never appears under Shared with you, so its address is the one thing a colleague cannot find on their own.

hiy does not build a per-person trail for a Team Agent. Public twins get an attribution view — open the conversation behind a lead or a booking click — and that is deliberately not enabled here. The default for an organisation is that admins see usage and topics, not who asked what, and a transcript view would quietly contradict it.

That survives the account-wide Dashboard. Overview, Insights and Activity add up every agent you own, and a Team Agent's conversations are left out of every per-conversation figure — it contributes no row to Activity, nothing to the recent-conversations list, nothing to the most-cited tally. It does count in the totals: conversations, questions, people, the activity chart. Top questions counts it too, because a tally of what was asked names nobody who asked it — that is the topics half of the promise above, and it is read separately from anything that could be regrouped into a conversation. All of these are counts about an agent, not a trail about a person, and they are the same numbers a Team Agent's own dashboard has always shown.

Each block of figures on those pages says which agents it covers, so you can see the exclusion rather than take it on trust — you will read Across 2 of your 3 agents — a Team Agent keeps no per-conversation trail. If a Team Agent is the only agent on your account, Overview and Activity say exactly that rather than showing you an empty list that would read as "nobody asked anything".

Its card on the Agents list carries no "last answered" either. Every other agent's card shows when it last replied; that is one conversation's timestamp, and on a three-person team "last answered 3 minutes ago" comes close to saying who just asked. The card shows how many questions are waiting to be taught, which is a count.

Turning it on#

A Team Agent is a draft until you publish it, and until then the link returns a 404 to your colleagues too. The control is on its Publish tab, under the link, and on Overview. Unpublishing is immediate and acts only on the agent you are looking at — your own public twin and any other agent are untouched.

Publishing hands you the team version of the launch kit: who can reach it, and how an invite works. No QR code and no ready-made posts — they would invite people who get a 404 — and the link itself stays on Publish, beside the list of who may open it.

A new Team Agent starts on Strict scope: it reports what your material actually says and declines the rest, because a confident guess about a company matter is worse than no answer. Change it on the Voice & rules tab whenever you like.

What it knows#

Only what you give it, and what you give it stays internal: sources on a Team Agent can be marked confidential, which makes it impossible — enforced in the database, not by a checkbox — for them to ever reach your public twin.

It shares your monthly allowance#

A second agent does not come with a second allowance. Your plan's visitor messages are one pool for the whole account, and every twin and agent you own draws from it — so adding this one divides the month rather than doubling it. The meter on your Overview and in Settings → Plan & billing already counts it that way. See Plans and billing.

Creating one#

A Team Agent is part of Founding, and free during your 14-day trial — making one starts that trial if you haven't spent it yet. Your own public twin is free, always. See Plans & billing.

From the twin switcher in your dashboard: New Team Agent. It's usually named after you, because it speaks as you — and a Team Agent named after yourself goes live without review. Name it after somebody else and a person checks it first; that's the identity rule doing its job.