Organization billing

With organization billing, the organization pays for the credits of the workspaces you choose, on one bill. Each of those workspaces is organization-billed: it has no plan of its own. The other workspaces in the organization are standalone: each pays for its own plan, as before. Your account manager turns organization billing on. The dashboard has no way to buy it. Until then, the Billing tab on the Organization page says: Organization billing is not active. Contact your account manager to activate it.

​

Pool or metered

An organization is billed in one of two ways. Your account manager agrees the terms with you. The usage invoice has one line for each organization-billed workspace. Credits count the same way as on Billing types: agent, workflow and chat credits, plus Phone Agent minutes. A pool can start on any day. Its first commit is charged for the days left until the next 1st. A later change to the commit takes effect on a 1st.

​

The Billing tab

Open Organization → Billing. Organization owners and administrators see this tab. Only owners add workspaces, remove them and set limits. For a pool, the figures are the commit, the credits used, the overage so far and the estimated overage charge. For a metered organization, they are the credits used and the cost so far at your rate. All amounts are before tax. The workspace table has these columns: Workspace, Billing (Organization or Standalone), Credits this month, Share of total and Limit. The credits are the ones the organization pays for this month. A workspace that left organization billing during the month keeps the credits it used before it left, and the organization pays for them. A workspace that was standalone all month shows Not counted.

​

Add workspaces

An owner adds existing workspaces once organization billing is active or has a start date. There is no payment step, because the organization’s card is already on file. A workspace on a plan has two choices: A workspace in a trial, or with no plan, joins at 00:00 UTC the next day. When organization billing starts on a later date, no workspace joins before that date. Join now and a workspace with no plan join on the start date. At period end joins at the first end of a paid period on or after the start date, so the plan can renew once or more before then. The review shows each workspace’s real join date.

​

Create a workspace the organization pays for

When organization billing is active or has a start date, Create workspace on the Organization page asks how to bill the new workspace:

• Own plan: a 14-day free trial, then the workspace pays for its own plan.
• Billed by the organization: no trial. The organization pays for its credits from the start, or from the start date.

The rest of the steps are on Create a subsidiary workspace.

​

Limits and the cap

Both count the credits of the current month and start again on the 1st at 00:00 UTC.

• Workspace limit: only an organization owner sets, raises or clears it. The owner types a monthly credit limit in the Limit column of a workspace. It saves when you leave the box. Leave it empty for no limit. A workspace at its limit stops new agent and workflow runs until the 1st, so one workspace cannot use the whole commit.
• Cap: your agreement can set a cap for the whole organization. The Billing tab shows the credits used against it. Organization owners and administrators get an email alert at 80% and at 100% of the cap, once for each level in a month, and again if the cap changes. At the cap, new agent and workflow runs stop in every organization-billed workspace until the 1st. Only Neo raises the cap: ask your account manager.

​

What an organization-billed workspace sees

Its Billing page says Billed through the organization’s name. It shows the workspace’s own credits this month and its limit, if one is set. It shows no plan, top-up, add-on, price or invoice, and no other workspace. For an add-on such as the Phone Agent, contact your account manager. When a run stops at the workspace limit or the organization cap, its message tells you to ask an owner of your organization.

​

Neo API and the Neo Support agent

• GET /public-api/billing/organization returns the open workspace’s own share: the organization’s name, its credits this month, its limit and the removal date. Any caller of the workspace can read it, and the Neo Support agent uses it to answer “how much has this workspace used”.
• GET /public-api/organizations/{organization_id}/billing returns what the Billing tab shows, and PUT /public-api/organizations/{organization_id}/billing/workspaces/{client_id}/limit sets a workspace limit. Both need an organization owner or administrator; only an owner sets a limit. A workspace API key gets 403 on both.
• In the dashboard chat, the Neo Support agent answers organization-wide questions and sets limits for a person who holds that organization role. It asks for approval before it changes a limit. In Teams or Slack it answers only for the workspace, and sends you to the dashboard for the rest.

​

Remove a workspace

An owner selects Remove… on the workspace’s row and picks a removal date. The earliest date is 7 days from today, and the workspace’s admins get an email 7 days before it. From that date the workspace has no plan, so new runs stop until one of its admins chooses a plan on its Billing page. Until that date its Billing page shows a Choose a plan banner with the date. The organization still pays until then, so the workspace cannot buy a plan of its own earlier. A workspace leaves organization billing before it can leave the organization.