Connect Maqsam
The same controls every calling channel gets — credentials, a resource picker, region and direction — for teams whose telephony sits with Maqsam.
Maqsam is a calling channel and behaves exactly like Twilio in Convarza: credentials, a resource picker, region, direction, routing, calling hours and concurrency. If you have connected Twilio, there is nothing new here except where the credentials come from.
Because Maqsam is strongest across the Middle East, the two settings worth extra care are region and the timezone on your calling hours — a working week that runs Sunday to Thursday is easy to get wrong on a control that defaults to a Monday-to-Friday pattern.
Before you start
- A Maqsam account and its credentials.
- The concurrency your account permits.
- Your actual working week, which may not be Monday to Friday.
Steps
Add a Maqsam channel and connect the account
Credentials are typed rather than generic: masked secrets with a Show toggle, and a resource picker rather than a free text box you could mistype.
If the number you expect is missing from the picker, the credentials usually cannot see that part of the account.
Set region and direction
The same controls every calling channel gets. Set the region to match where your numbers are.
Route it
An AI voice agent, or a call flow.
For an inbound line a flow is usually the better answer, because it can check business hours and ring your team before handing to the agent. A bot answers immediately, which is right for an after-hours line and wrong for your main number.
Set calling hours for your real working week
Set one day correctly and use Copy Mon→Fri only if that is your week. For a Sunday-to-Thursday week, set the days individually rather than copying and then patching.
Add date exceptions for public holidays, which differ by country and move each year.
Set the allowed calls count
Under additional settings. Confirm the number with Maqsam rather than guessing — calls above your permitted concurrency are rejected at their end.
Test in the direction you enabled
Ring in if incoming is on; place a test call if it is outgoing only. Refresh trunk status afterwards.
Check it worked
Place a call at the very start and the very end of your calling window. Both should behave as you expect, and if they do not, the timezone is the first thing to check.
The parts people get wrong
- Arabic-speaking callers make voice-per-language settings on your call bot worth configuring properly. Voice is set per language on the bot, never on the channel.
- A mismatched region typically shows as poor audio or failed connections rather than as a clear error message.