#Call Limits
| Role | Access Level |
|---|---|
| Client Admin | Edit |
| Client Manager | View only |
| Client Staff | No section |
#Overview
Call Limits settings let you review and manage the maximum duration for inbound calls on one project at a time. The portal exposes the customer-safe hangup.max_duration.timeout_seconds control only. It does not configure concurrent-call caps, daily-call caps, queues, rejects, or redirects.
#Prerequisites
- You are signed in to the AiDial portal. See Signing In for instructions.
- Client Admins can edit supported call-limit values.
- Client Managers can review the summary only.
- Client Staff do not receive this Settings section.
- Your session must include at least one project. If your account has access to multiple projects, the page asks you to choose a project before loading its call limits.
#Configuring Call Limits
- Open Settings from the sidebar, then select Call Limits.
- Choose a project if the page asks for one.
- Review the current maximum duration, provenance, last-changed details, and runtime publish status.
- If the section is editable, enter a new Maximum duration (minutes) value.
- Select Save call limit to save your change.
- Review the runtime publish status after saving. Pending publish means the portal has saved the working copy, but the runtime YAML has not yet been published or deployed with the new value.
> Screenshot reference: Call limits settings with maximum duration and runtime status fields
#Field Reference
| Field Name | Description | Validation Rules | Default Behaviour |
|---|---|---|---|
| Project | The in-scope project whose call limit you are reviewing or editing | Required when your session has multiple projects. The selector only lists projects in your current server-side scope. | A single in-scope project loads automatically. |
| Maximum duration | The maximum call duration before the runtime hangup policy applies | Required for edits. Enter a whole number of minutes from 5 through 30. | The first view is taken from the published project configuration unless a customer-portal working copy already exists. |
| Provenance | Where the displayed value came from | Read only. | Shows whether the value is the saved customer-portal draft or the currently published runtime project configuration. |
| Last changed | When the displayed value was last changed or observed | Read only. | Shows whether the timestamp is a customer-confirmed change or a live source observation. |
| Runtime publish status | Whether the saved value matches the published runtime configuration | Read only. Possible states include published runtime matches, pending publish, and runtime status unavailable. | Saved changes can remain pending until the runtime configuration is published or deployed. |
#Empty State
If your session has no in-scope projects, the page displays No in-scope projects available and does not show edit controls.
If your session has multiple in-scope projects, the page asks you to select one before it loads the call-limit summary.
If the published runtime call limit cannot be resolved safely, the page displays a temporary unavailable state. Reload after the source is corrected, or contact your AiDial delivery partner.
#Common Issues
| Issue | Resolution |
|---|---|
| Cannot edit call limits | Only Client Admins can save changes. Client Managers see a summary-only view, and Client Staff do not receive this Settings section. |
| No project is selected | Choose a project from the Project selector. The page will not load project-specific call limits until one in-scope project is selected. |
| Value is rejected | Enter a whole number of minutes from 5 through 30. Values outside that customer-safe range cannot be saved from the portal. |
| Save button is disabled | The value may be unchanged, the section may be summary-only, or the published runtime value may be outside the supported customer-safe range. Contact your AiDial delivery partner if the panel says the value is managed elsewhere. |
| Save reports that the state changed elsewhere | Select Reload latest, review the latest confirmed value, then save again if a change is still needed. |
| Saved change is not live yet | Check the runtime publish status. Pending publish means the portal working copy has been saved, but the runtime YAML still needs to be published or deployed. |
| Changes are temporarily rate-limited | Wait for the retry period shown in the message, then try again. |