In a virtual PBX, it is possible to control the expenses of employees for outgoing communications. At the same time, you can limit the use of paid outgoing traffic both per day and per month. In addition, you can completely prohibit employees from making paid calls. Restrictions on outgoing communication are configured for each employee individually - each employee can be allowed to spend different funds in accordance with company requests.
Restriction of paid outgoing traffic is set by setting a daily and/or monthly limit. When the daily or monthly limit is reached, the employee's paid outgoing communication will be disabled. Paid outgoing traffic will be available to the employee from the next day (if the daily limit is exceeded) or from the next month (if the monthly limit is exceeded), as well as when a new limit is set.
⚠️ Note:
Limiting outgoing communication costs by setting a daily and monthly limit is a paid option. To be able to set daily and monthly limits, you must activate the "Expenditure control" option. See "How to enable Cost Control" for more details.
To set a limit:
Go to Virtual PBX >> Settings >> Extension Numbers >> Outbound Routing tab.
In order to limit an employee's expenses for outgoing calls, set the daily and/or monthly limits.
The cost limit for a subscriber for paid outgoing traffic is set in the currency that is used for the account:
Daily traffic limit — to set a daily limit for outgoing communications, move the slider to the active position and enter the limit value. If the subscriber needs to completely disable paid outgoing calls, specify the value "0".
Monthly traffic limit — to set a monthly limit for outgoing communications, move the slider to the active position and enter the limit value. If the subscriber needs to completely prohibit making paid calls, specify the value "0".
Instructions for setting up a subscriber can be found in the "Subscriber numbers" section.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article