Go back to dialerseat.comsales@dialerseat.com
Build

Teams, roles and access

Tie your own teams and campaigns to the dialer, so each person sees and dials only what your platform lets them.


Your platform already knows who is on which team and who may work which list. Tell DialerSeat the same thing, by your own ids, and the dialer, the queue and every component show each person only what they may reach.

The model

  • A team is one of yours (a workspace, office, region), by your own id: POST /v1/teams.
  • A seat is on any number of teams, with a role: agent, manager or admin. POST /v1/seats { teams, role }, or POST /v1/teams/{id}/members.
  • A campaign lists the teams, and if you like individual people, who may dial it: POST /v1/campaigns { teams, seats }. A campaign with neither is open to everyone.

The rules, in order

  • A paused campaign is never dialable, by anyone.
  • If the session names campaigns, exactly those.
  • An admin may dial every campaign.
  • A campaign with no teams and no people listed is open to every seat.
  • Otherwise the person is on one of its teams, or listed on it.

Leads for a campaign someone may not dial never enter their queue, and the server refuses a call to it even if a page asks.

Saying it per session

Your server already checks permissions when it opens a page. It can state the answer when it opens the dialer, and that answer holds for that session. It replaces the stored rules for that one dialer, so it can narrow or widen them.

bash
curl https://api.dialerseat.com/v1/seats/SEAT_ID/sessions \
  -H "Authorization: Bearer dsk_test_..." \
  -H "Content-Type: application/json" \
  -d '{ "campaigns": ["crm_campaign_77", "crm_campaign_80"], "teams": ["team_west"], "role": "manager" }'

Checking it

GET /v1/seats/{id}/access returns one person's teams and role, every campaign with whether they may dial it and why, and the dial modes they get on each. The console's Teams and access page shows the same thing for anyone you pick.

Dial modes by team

A dial-mode exception can be for a campaign, a seat, or a team. The most specific wins: the campaign, then the seat, then the first of the seat's teams that has one, then your project's policy.

Who is on a call right now

Every open dialer reports where its agent stands: paused (the dialer is open, the agent not yet available), ready, dialing, on a call or wrapping up; a closed one reads offline. GET /v1/seats shows it on each seat, the seat.status_changed webhook tells your server when someone goes offline, becomes available or goes on a call, and the dialer's state event tells your page. A dialer that stops reporting for two and a half minutes reads as offline.

Managers and admins can put a team board on their page: <dialerseat-team>, or dialer.attach('team', element). It lists their people (everyone who shares a team with a manager; everyone, for an admin), each one's status, and today's dials, connects and talk time. It shows statuses only: nothing in it listens to a call or joins one.

Related:Seats and sessions, Campaigns and leads, Dispositions and Dial modes and exceptions.