ruLog in to Senler

Lead credit limits

What this setting limits

The limit determines how many credits agents can spend when working with one lead during a selected period. Credits are not a message count: usage depends on the selected model, response size, and tools used.

This is not the project balance or a separate way to pay for Senler AI. Even while a lead has a personal allowance remaining, the project still needs credits for the agent to work.

Configure limits

Open the settings dialog

Open Settings, then select Limits in the sidebar. After that:

  1. Find the Lead agent credit limits card.
  2. Click Configure.

A member without permission to update the project sees View instead: the dialog is read-only and has no Save button. Granting and resetting credits in a lead profile require the separate permission to manage leads.

Open the settings dialog. Highlighted elements: 1. Lead agent credit limits card; 2. Configure
1. Lead agent credit limits card · 2. Configure

Set periods

In the dialog:

  1. Turn on Limit agent usage when the default periods should apply across the project.
  2. In the first period, complete the Name field.
  3. Enter the Period, hours.
  4. Enter the amount in Credits.
  5. If needed, select Add period. You can create up to ten periods.
  6. To remove an unneeded period, select Delete period in its row.
Set periods. Highlighted elements: 1. Limit agent usage; 2. Name; 3. Period, hours; 4. Credits; 5. Add period; 6. Delete period
1. Limit agent usage · 2. Name · 3. Period, hours · 4. Credits · 5. Add period · 6. Delete period

At least one period must remain while the project-wide rules are enabled. A channel in Custom periods mode also requires at least one period.

For example, “1,000 credits per 24 hours” and “10,000 credits per 720 hours” limit usage both per day and approximately per month. The agent can work while every active period still has credits remaining.

Optionally select an automation

In Automation on exhaustion:

  1. Open the automation list.
Optionally select an automation. 1. automation list
1. automation list
  1. Choose a published contextual automation that accepts new runs.
Optionally select an automation. 2. published contextual automation
2 / 2
2. published contextual automation

The automation starts once when the allowance is exhausted. For example, it can record the event, notify the team, or send the lead further instructions. Leave the field empty if no special action is required.

Optionally add channel exceptions

When the project-wide rules are enabled, they apply to every channel without its own settings. To give one channel a different mode:

  1. Select Add.
Optionally add channel exceptions. 1. Add
1. Add
  1. In the new exception, choose a channel.

  2. Choose its mode:

    • Unlimited — the personal limit does not apply in this channel;
    • Custom periods — the channel uses its own periods and credit amounts.
  3. To return the channel to the project defaults, delete the exception.

Optionally add channel exceptions. Highlighted elements: 2. channel; 3. mode; 4. delete the exception
2 / 2
2. channel · 3. mode · 4. delete the exception

An exception changes the rule only for the selected channel. A channel can have only one exception.

Custom channel periods also work when the project-wide rules switch is off. For example, this lets you enable a limit only for the widget without limiting other channels. If the project-wide rules are off and a channel has no custom periods, no personal limit applies in that channel.

Save the settings

Review the periods, selected automation, and exceptions. Then:

  1. Select Save.
Save the settings. 1. Save
1. Save

The new rules start applying to the project only after they are saved.

How credits are used

Every actual agent usage is counted in all active periods. When several periods are configured, the available amount is determined by the period with the smallest remaining balance.

The limit is checked before a new agent run begins. If a response is already being generated, its final cost may exceed the remaining allowance: the current response completes, and the next run is blocked because the allowance is exhausted.

When a period ends, its used amount is reset and a new period begins. Extra credits granted manually or recorded as a purchase are stored separately: they are spent after the periodic allowance and are not removed when periods are reset.

Check a specific lead's limit

Open the lead profile. If a limit applies to the lead's channel, the Agent usage credits card shows the periods, used amount, renewal date, extra balance, and total available amount.

A member who can manage leads can:

  • click Grant credits, enter an amount, choose Manual grant or Purchase, and optionally add a comment;
  • click Reset limits to restart periodic limits; the extra balance is preserved;
  • open the operation history and find usage, grants, purchases, resets, adjustments, or refunds.

These actions change the amount available to the lead, but do not top up the project balance.

What a widget visitor sees

When the limit applies to a Widget channel, the visitor can see the remaining credits in the chat header. When they run out, the message input is replaced by “Credits used up.”

After exhaustion, the owner can offer the visitor either a credit top-up through the website or a way to connect the project's MCP server to their own AI client. The purpose of both options and the distinction between them are covered in Visitor credit limit, while payment integration and the subsequent credit grant are covered in Credit top-up request.