Skip to content
Docs
API reference Go to dashboard
DocsTeam

Team and permissions

Invite colleagues, assign roles, and decide who sees which area. This matters as soon as more than one person answers.

Why this matters early

While you work alone you do not need this page. The moment a second person answers, you do: two people replying to the same request is worse for the customer than one reply arriving ten minutes later.

Seats per plan

PlanSeats
Basic3
Business15
Enterpriseunlimited

Seats are included in the price. There is no per-seat price and nothing to add on — bringing another person into the inbox costs you nothing.

Why that is unusual. Intercom charges $29–132 per seat per month, Zendesk €19–115 — there, the head is the price. At Alpheris it is the conversation. A team of 15 costs you nothing extra; your limit is your conversation quota, not your team size.

If the seats run out, the next plan is the way — not an add-on.

Inviting someone

Under Team you invite by email. The invitee sets their own password — you never see it and never have to pass one around. Until they accept, they appear as pending in the list.

The roles

  • Owner. Everything, including billing and deleting the account. There is exactly one.
  • Administrator. Everything except what is reserved for the owner. Can invite people and grant areas.
  • Agent. Answers requests. What they see beyond that is up to you, area by area.

Granting areas individually

For each person you can separately allow: inbox, tickets, customers, knowledge base, settings, analytics, team and billing.

A sensible default for someone who should only answer: inbox and tickets on, everything else off. They then see no revenue figures and cannot reconfigure the AI.

When an area is missing: someone who cannot see a menu item has no access to it — that is not a bug, that is the permission. Check their areas under Team, not their role.

Who is working on what

A conversation can be assigned to one person. After that the others see somebody is on it and stop receiving notifications for it. That is the simplest way to avoid duplicate replies.

You can see who is online in the inbox bar. The AI uses the same signal: it only connects to a person when somebody is actually there — otherwise it creates a ticket.

Mailboxes per team

Email mailboxes can be assigned to individuals or departments. Someone in sales then does not see the returns mail, and the other way round.

When somebody leaves

Deactivate the account rather than deleting it. Their previous replies stay attached to the conversation — otherwise old threads show nobody, and later you cannot trace who promised what.