Plans
Pilot
Starter
Growth
Custom
How credits are spent
Workflows (smart actions such as triage or dispatch) bill 1 credit per ticket they work. That is the simple rule for most automations. Agents bill in two different ways. The same tool list can look cheap on a ticket-triggered agent and expensive on a scheduled or chat agent:Ticket Dispatch
Dispatch bills per ticket it works on, so re-running it over a backlog doesn’t charge you repeatedly for tickets it leaves alone:- A technician is assigned — 1 credit.
- The ticket already had an owner and Skip if already assigned is on — free. Dispatch checks ownership before it does any work, so a scheduled re-dispatch over an already-handled backlog costs nothing.
- Dispatch couldn’t complete for a ticket — for example it kept hitting calendar-slot conflicts and ran out of retries without placing it — free. The run output lists the ticket and the reason.
- Someone claimed the ticket while Neo was deciding — 1 credit. Dispatch had already done the work by then; it discards the result rather than overwriting the human’s assignment.
Scheduled agents and chat agents
A scheduled agent with no ticket bills the same way as an internal chat agent: per tool call, at each call’s price. Test mode blocks writes; it does not stop those calls billing. The per-tool table is on Tool credit costs. Chat agents are also billed by who they serve:- Internal chat agents — your technicians chatting with Neo in the dashboard or Teams — spend credits per tool call. A turn with no billable tool costs nothing.
- The branded end-user Teams bot — the white-label bot your clients’ employees use — is not billed in credits. It’s priced per client company, from $9/month, and a client nobody used it in that month is free. See Chat sessions & billing.
What your credits cost
Wherever the dashboard shows credits, it also shows what they cost you in your billing currency: 1,234 credits ≈ $160. You see it on the agents list, Performance & Cost, Executions and each run, the Billing page, and chat History. Hover over the figure for the price per credit and where it comes from. The price per credit is what you pay, divided by the credits it buys:- Plan and top-up packs: your monthly plan charge plus the top-up packs you hold, after any discount, over the credits they include. A Growth plan at $2,340 for 20,000 credits is $0.117 a credit.
- Free credits do not lower the price. Bonus, referral, reserve and trial credits cost nothing, so they count on neither side. Every credit you use is priced at the paid rate, including one that came from a free balance, so the figure is an estimate and never an invoice line.
- Custom plans use the price per credit in your agreement. Pax8 partners see Pax8’s list price for their tier, in US dollars. A plan whose price no billing system holds shows credits only until the Neo team enters the agreed rate.
- Trials show credits only, because nothing is paid yet.
Credits per ticket
To see what each ticket cost over a period, for example to work out your cost per client company, click Export credits per ticket on Activity → Agent & Workflow Executions for a CSV file. Or ask the Neo Support Agent: “Show credits per ticket for the last 30 days.” It readsGET /public-api/billing/usage-by-ticket, which you can also call yourself with an API key.
- One row per ticket: its ID, its number, its client company (ID and name in your PSA), the runs that billed credits, and the credits with what they cost you, highest first.
- The company is the ticket’s company in your PSA when Neo last synced the ticket, so a ticket moved to another company shows the new one.
- An agent that runs on something other than tickets, such as time entries, bills per item: its rows show that item and its type, with no company.
- A credit counts in the period it was billed in, as on your invoice.
- Scheduled agents with no ticket, bulk runs and Chat Agents share one row with no ticket.
- The total covers the whole period for the agents you can see, also when the answer lists only the highest tickets.
- A period can be up to 93 days. Ask for a longer range one quarter at a time.
Unusual agent usage
Neo watches each agent’s credit spend through the day and emails you when one of them uses far more than it normally does. The email names the agent, what it has spent so far today, and how that compares with its own average day, and links straight to the runs behind it. An agent you have since deleted is still named and still reported, without that link. A notice raised by the default detection also gives the share of your monthly credits that today’s spend has used. A notice raised by a daily credit budget you set does not, because you chose the number it passed; it says so instead of calling the day unusual. The usual cause is a change to that agent. An agent that cannot finish its work will often repeat it, and a repeat every ten minutes adds up long before your monthly warning arrives. By default you are told when a single agent uses more than 8 times its average day (the average of its last 7 days with credits in the last 30 days) and at least 5% of your monthly credits in one UTC day. An agent with fewer than 3 days with credits in the last 30 days gets no default alert yet. Neo checks every 10 minutes, so the email arrives the same day, within about 10 minutes of the agent crossing that line. A crossing in the last minutes before 00:00 UTC is not reported for that day, because the next check starts a new day; an agent that keeps spending is reported on the new day. Each agent tells you at most once per UTC day. Agents that cross in the same check share one email; an agent that crosses later that day gets an email of its own. This default check covers every agent that has no daily credit alert of its own.A daily credit alert for one agent
Some agents use far more credits than others by design, so one threshold cannot suit them all. A daily credit alert gives one agent a cap of its own, and emails you on the same day that the agent goes over it, while there is still time to stop the spend. Rules live in Settings → Alerts, under Per-agent credit alerts. Select Add alert, choose the agent, and set the rule. Select an agent’s name in the list to edit its rule. From the same list you can switch a rule on or off with its On switch, or remove it, and each of those changes saves at once. A rule you switch off is paused: it keeps its settings, and the default check covers the agent until you switch it back on. Chat agents do not have this setting. You can also set the alert where you build the agent: switch on Daily Credit Alert on the Overview tab of the agent builder, or on the Review & Launch step of the workflow builder. It is off for a new agent or workflow. When you switch it on, it starts at 300% above the average, emails your account owners and admins, and leaves the agent running. Neo saves it when you save the agent; for a new agent, once the agent is created. How the cap is set. You choose how far above the agent’s average day it may go, as a percentage. Neo takes the agent’s last 7 days with credits within the last 30 days, and averages them. Days with no credits are skipped, so a week the agent was off does not lower its average. The cap is the average plus your percentage: 30% above an average of 100 credits is a cap of 130. The cap is never below 50 credits a day, so a quiet agent does not alert on a day too small to matter: 300% above an average of 10 credits would be 40, and the cap is 50. You cannot change this minimum. An agent needs at least 3 days with credits in the last 30 days for an average. Until it has them, the rule has no cap and does not alert, and the list shows Not enough history yet. With 3 to 6 such days, the average covers the days there are. Before you save, the form shows what the rule would do for this agent, and on how many of the last 30 days it would have alerted. Each of those days is judged against the cap the rule would have given on that day. For example: Average: 62 credits a day (last 7 days with credits). Alerts above 81. It would have alerted on 2 of the last 30 days. When it would have alerted, Show chart draws those 30 days against the cap. Neo works the cap out again every night, and each time you save the rule. When it alerts. The day is the UTC day, from 00:00 to 24:00 UTC, whatever your time zone. Every 10 minutes, Neo compares the agent’s credits since 00:00 UTC with its cap. As with the default check, a crossing in the last minutes before 00:00 UTC is caught on the new day only if the agent keeps spending. When the agent goes over, Neo emails your account owners and admins while Account owners and admins is turned on, and also every address in the email field under that toggle. A new rule starts with Account owners and admins turned on. Add more addresses one at a time in the email field; a shared mailbox or a Teams channel address works. A rule needs Account owners and admins turned on, or at least one address in the email field. When no email gets through, Neo puts the notice in your Neo inbox instead. Turning the agent off. Switch on Turn the agent off at the cap to also disable the agent when it goes over. The email says that Neo turned it off. If Neo cannot turn it off, the email says so, and asks you to turn it off yourself. When you turn the agent back on, its count for the rest of the UTC day starts again from the moment Neo turned it off: only the credits it uses after that count toward today’s cap. If it goes over the cap a second time, Neo emails you again and turns it off again. At 00:00 UTC a new day starts, with a newly computed cap. Without this setting, a rule emails at most once per UTC day. How it works with the default check. An agent with an enabled rule is checked against its rule only: the default check and the account-wide daily credit budget per agent skip it. An agent with no rule, or with its rule switched off, stays on the default check. Delete the rule or switch it off to go back to the default. You can also read and set these rules through the public API, or ask the Neo Support Agent to set one for you.When you hit your monthly limit
By default, automations pause until your credits reset on the 1st of the next month. You won’t be charged extra and no automation runs are lost — they resume the moment your credits reset. When this happens, the dashboard shows a banner explaining the pause, with a link to top up. You’ll usually see it coming: when your current usage pace would use up your monthly credits, the dashboard warns you before you hit the limit — and as you get close it shows the date you’re on track to run out (e.g. “Credits run out around Jul 14”). See Will I be notified before I run out? below. If you’d rather keep automations running, turn on auto top-up.Auto top-up
If you're on Pilot or Starter
If you're on Growth or higher
Removing or reducing your top-up packs
Top-up packs are reversible, and you change them yourself. Go to Billing → When you reach your limit and choose Manage top-up packs. You need the Admin or Owner role. Set how many of each pack you want to keep — drop one, drop several, or remove them all. As you change the numbers, the dashboard shows what you will pay each month, the extra credits you keep, and the credit limit you are left with. Two more things happen when you reduce your packs:- We credit you back for the unused part of the current billing period. The credit comes off your next invoice. It is not a refund to your card.
- If you remove every pack, auto top-up switches off, so we do not buy them again the next time you reach your limit. Keep at least one pack and your auto top-up setting is left alone.
When does the top-up actually happen?
Credit usage is checked once an hour. So if you blow through your monthly credits at, say, 14:23, the top-up applies sometime between 14:30 and 15:30. In that small window, automations might briefly pause. They resume as soon as the top-up lands.FAQ
Is auto top-up a one-off charge or recurring?
Is auto top-up a one-off charge or recurring?
What happens if a subscription payment fails?
What happens if a subscription payment fails?
What if my bank asks me to confirm the payment?
What if my bank asks me to confirm the payment?
What if I only need extra credits one month?
What if I only need extra credits one month?
Will I be notified before I run out?
Will I be notified before I run out?
- On pace to run out — if your usage this month is trending over your monthly credits, a heads-up appears from the 3rd of the month. The forecast adds your usage so far to your usual usage for each remaining day, based on your last four weeks, so quiet weekends don’t make it swing.
- Running out soon — within about 5 days of when we project you’ll hit your limit, the banner shows the expected date (e.g. “Credits run out around Jul 14”).
- Paused — if you use everything, a clear notice with a link to top up.
Do unused credits roll over?
Do unused credits roll over?
My subscription ended — what happens, and how do I restart?
My subscription ended — what happens, and how do I restart?
- 60 days after the pause, we delete your content: synced tickets and documentation, run history, chat, approvals, notifications, files, call transcripts and recordings, and the PSA and device data we copied.
- 90 days after the pause, we delete your setup: agents, workflows, dashboards, skills, memories, technicians, channels, dashboard users, API keys, integration settings, your end-client company list and its links, and the credentials you connected. Your account record keeps your plan, billing history and a few setup details, such as which PSA you used, with no credentials and no contact details.
Can I switch plans manually?
Can I switch plans manually?
I bought Neo through Pax8 — how do I activate my account?
I bought Neo through Pax8 — how do I activate my account?
I buy Neo through Pax8 — how does a plan change bill?
I buy Neo through Pax8 — how does a plan change bill?
How can I pay — card or Direct Debit?
How can I pay — card or Direct Debit?
Which email address do invoices go to?
Which email address do invoices go to?
