Separation enforced by the database
Call data is stored with the customer it belongs to, and PostgreSQL row-level security enforces that boundary inside the database. Every request for call data runs pinned to one customer, and the desk also checks that the person asking belongs to that customer. If they do not, the database returns nothing.
This does not depend on every page of the application remembering to filter correctly; the database applies the rule to every query.
Your own sign-in page
You sign in on the VereTel sign-in page with your email address and password. Our public sign-in page never asks which business you belong to, and it lists no customers, so nobody can use it to find out who our customers are. A customer whose company gave it a direct sign-in link uses that link.
Several locations, one account
If your business has several offices or teams, they can share one desk with tracking numbers labeled per location, and each number can forward to that location’s line. Our guide to call tracking across several locations was written for insurance agencies, and the set-up is the same for any business.