Managing companies

Do this

Open Companies. Type in the search box to find a company by name, short name (slug) or anyone’s e-mail. Use the status filter, or switch Table to Tree to see sub-accounts nested. Click a row to open the company.
To create one, press New company and go through four steps: company (name and slug), first owner (name and e-mail), plan (Trial, Standard or Enterprise, each with its limits) and review.
After it is created, the temporary password is shown once. Copy it and give it to the owner, who must change it at first sign-in.
To switch a company off, open it and press Suspend. Give a reason (at least 8 characters) and type the company’s short name to confirm. Resume switches it back on.
To plan the end of a company, open the menu next to Suspend and choose Schedule closing: reason and date. Cancel closing is in the same menu.

Roles: platform_support and platform_owner create, edit, suspend, resume and schedule closing. Everyone else reads.

Behind the screen: GET /tenants, POST /tenants, GET /tenants/{id}, POST /tenants/{id}/suspend, .../resume, .../closing.

What you see

The company page has six tabs: Overview (profile, plan at a glance, live numbers, health checks, recent changes; Edit changes the name and notes), People (everyone in the company with their role; each person has a menu to reset the password, disable or enable, sign out everywhere and reset two-step sign-in, each with a reason), Sub-accounts, Plan and limits (see plans and limits), Usage and billing (see billing) and Audit (what operators did to this company, with a link to the full audit log).
View as is in the page header. See view as a company.
The list shows each company with its parent, status, plan, live calls, agents online, calls today, AI minutes today, dropped calls over 30 days and last activity. It loads 50 at a time (Load 50 more) in creation order, so the live columns cannot be sorted across all companies. If a service did not answer in time, a notice names it and that cell shows a dash, not zero.
The detail shows the profile, people and roles, sub-accounts, plan, live numbers, this month’s usage, recent platform audit lines and the company’s own audit lines.
The health check shows each service’s answer, whether the company is suspended in the gateway and in core (and whether they agree), which caps it has hit, and whether the kill switch is holding it.
The tree (GET /tenants/tree) shows companies with their sub-accounts nested. A sub-account cannot have sub-accounts.

Creating a company

Creation is all or nothing. The gateway asks core to set the company up inside the same step. If core is down, nothing is created. A slug that is taken or an e-mail already registered is a 409. An e-mail that belongs to an operator is refused.

What suspending does

The Suspend box says it in one sentence: dialing stops at once and everyone in the company is signed out; calls already up finish. The steps behind it:

Suspending runs the same chain the parent owner’s own suspend button uses:

The company is marked suspended and everyone in it is signed out. Sign-in, sessions and API keys stop working at once.
Every running campaign is paused, in the dialer and in core.
Core is told, so it hands out no more people to call and refuses to start campaigns.

Dialing stops within seconds. Calls already up finish on their own. Nothing is deleted.

Resuming does not restart campaigns. The company’s own people must start them again.

If some step fails, the answer says complete: false and lists what failed. The suspension still stands. Repeat the call to retry.

Scheduled closing

POST /tenants/{id}/closing with a reason and a date moves the company to closing and stops it the same way. It is soft: nothing is ever hard-deleted. A closing company cannot be resumed until you cancel the closing (DELETE /tenants/{id}/closing), which leaves it suspended.