One phone system across every office
Numbers for each location, one account to manage them, and the identity, retention and audit controls that make a rollout signable.
What usually goes wrong
Every site did it differently
Three offices, three phone systems and three sets of logins make it impossible to see what is happening.
Access needs to follow the directory
Manual user management across sites is where access problems begin.
Data has rules
Where call data lives and how long it is kept need to be decided once and applied everywhere.
See how multi-site teams teams run CallVend.
Numbers for every location
Each office has its own numbers in the same workspace, with the same settings and one bill.
Users from your directory
SAML sign-on against your identity provider, with roles and permissions defined per workspace.
Every live call on one board
Admins see who is on a call right now, across every number, as it happens.
A data region you choose
Your workspace is created in one data region and your call data stays there, with retention set per workspace.
Multi-site teams: the questions that decide it
Yes: numbers per office, and one place where the call history, contacts and reporting live. Enterprise is sold by quote, so it is sized to the organisation you actually run.
Roles, including custom roles per workspace, decide who reaches which numbers and recordings. SAML 2.0 single sign-on works against your identity provider, two-factor authentication uses TOTP apps with single-use backup codes, and every privileged action lands in an append-only audit trail.
Yes — a ring group can include people wherever they are, because the phone is a browser tab or the Windows app rather than a desk handset.
Other cases, and the product behind them
Similar teams
The product
Built for multi-site teams teams.
Set up a workspace, add your team, and take your first call the same afternoon.