Configure free AI allowances and service usage limits

Free AI allowances and purchased AI credits are different controls. The free allowance permits a configured number of eligible requests for a service each day, while purchased credits are consumed according to measured token usage. Publish an offer that matches the settings you actually deploy.

01 Set the daily allowance

  1. Open AI engineers & credits and review both the website and hosting allowance settings.
  2. Enter the intended free daily allowance for each relevant Engineer experience. Do not assume the package's saved defaults match your customer offer.
  3. Review the monthly usage cap and whether paid credits will be sold. A free allowance should be affordable at the selected model's current cost.
  4. Save the settings and test a service with no earlier usage for the current day.
  5. Make a small request, then inspect the remaining allowance and service usage. Verify the correct service was charged.

02 Understand the scope and reset

The free counters are associated with a WHMCS service and a UTC calendar date. The WordPress website builder and WordPress Engineer share the website allowance for that service. They do not each receive an independent copy of the same allowance. The regular Hosting Engineer has its relevant hosting allowance.

The reset follows the UTC date used by the module rather than each customer's local midnight. Customers with several services should check the selected service's balance and allowance. Avoid describing a daily allowance as a promise of the same number of completed repairs or finished websites, since one task can need several requests.

03 Explain purchased credits correctly

Purchased credits also belong to a service, but their consumption depends on input and output token usage. A long conversation, large page or multi-step operation can cost more than a short question. Unused request reservations are released after settlement, and failed reserved requests are handled through the credit accounting workflow.

The module's monthly token cap can pause new AI requests even where paid credits remain. Treat it as an operational limit and monitor your provider account as well. It is not a guaranteed cash-spending ceiling under every provider or concurrent-request condition.

Common questions

Why does another website tool show a lower allowance?

Check whether the customer already used the shared WordPress allowance in the builder or Engineer on that service. Then compare the module's UTC date with the customer's local date.

Can I change the offer later?

Yes, the settings are configurable. Update customer-facing descriptions and support guidance at the same time, and respect any commitments already made to customers. Changing the configured allowance does not change a provider's prices.

  • 0 Users Found This Useful
  • hosting-suite, ai-engineer
Was this answer helpful?

Related Articles

Configure Hosting Suite access rules and verify effective permissions

Hosting Suite access rules add module-specific restrictions to the permissions already granted...

Set safe operating expectations for AI changes and Undo

The Engineers can inspect supported information and propose changes through available tools....

Price paid AI credits and check the protected minimum

Paid AI credits convert model usage into a service balance customers can buy through WHMCS....

Reconcile AI credit purchases, invoices and refunds

AI credit purchases create WHMCS invoices and add credits after successful payment. Use the...

Connect an AI provider and enable the customer Engineers

Hosting Suite needs a working AI provider configuration before customers can use the Engineers...