A team is three things at once
This is the page’s one genuine trap. A team is:- A roster. Who takes a dialler campaign’s calls.
- A budget. A team can be cut off while the organisation still has credit.
- Part of what a login can see. A supervisor’s scope is their teams.
Staffing a team
Add somebody to a team and give them a skill level from 1 to 10. The level is the team’s own rating of that person; it is not the same number as a queue member’s priority, which decides who a waiting call is offered to first and is set on the queue. Rostering a team needsteams:write, which an organisation admin holds and a
supervisor does not. A supervisor rosters
queues, not people.
Somebody can be on more than one team, and a supervisor who runs several sees
all of them as one scope.
The budget
A team can carry an amount and a period — daily, weekly or monthly. Type the amount exactly as you mean it; it is kept as typed, because parsing a budget to a number and back would round it before it ever reached the ledger. Where a budget applies, it is a second limit alongside the organisation’s balance, and the more restrictive of the two wins. A prepaid call is allowed only as many seconds as the remaining budget will pay for, and where the team is what stopped it the refusal says so rather than reporting insufficient credit against a balance that is plainly healthy. Calls that cost nothing are outside it entirely: an internal call, or one over a carrier the organisation owns, is never rated, so no budget applies.Presence is declared, not guessed
Three different facts sit behind the word “available”, and the directory shows all three side by side:
Only the person can declare their own presence, and it survives a
disconnection because it is stored. Whether somebody is on a call is never
stored: a saved copy is a lie waiting for a crash. On a call wins over the
declaration, because somebody who forgot to come back from a break is still
on the phone.