A contact centre platform is bought once and lived with for years, and the thing that decides whether you regret it is rarely the feature list. It is whether the routing model matches how your customers actually arrive and how your supervisors actually work. inConcert is an omnichannel cloud contact centre; the question this page answers is whether that description matches your operation.
You run a real contact centre — enough agents that shift patterns matter, more than one channel, and both inbound service and outbound campaigns in the same organization. If your customers reach you by phone, chat, WhatsApp and social and each arrives in a different tool with a different queue, a single omnichannel distribution layer is the point of the category.
We do not recommend it for a small team whose volume is comfortably handled by a shared inbox and a telephone line: you will buy supervision capability you have nobody to operate. We also do not recommend it where the real problem is a missing or unreliable customer record — an omnichannel front end over a fragmented back office just moves the confusion closer to the customer. Fix the record first; the options are on our CRM & contact centre page.
Per inConcert's own published material, its contact centre product centralises customer-experience channels in one platform: automated omnichannel distribution across inbound and outbound, configurable dialling engines for campaigns, integrated social media handling, embedded WhatsApp and chat, and AI-assisted self-service through virtual agents, voicebots and chatbots built in a bot flow designer. The vendor also publishes marketing automation and CRM sales management alongside it, and states security and data privacy as a platform concern.
Two to weigh before signing. First, breadth is a cost as well as a feature: a suite that also does marketing automation and CRM will overlap systems you already own, and the overlap has to be resolved deliberately or you will run two half-used platforms. Second, an omnichannel platform assumes an omnichannel operating model — skills-based routing, shared queues, supervisors who work across channels. Organizations that buy the technology without changing the operating model get their old silos back inside a new licence.
Three things shape this decision in the Kingdom. Call recordings and chat transcripts are personal data, so the national data-protection regime governs retention, access and where the recordings live — and for a cloud platform, "where" is a contract question, not a technical one. Arabic-language handling is a real evaluation criterion, not a checkbox: dialect coverage in speech and in bots is where generic demonstrations fall apart. And wherever the platform touches billing or invoicing, ZATCA's e-invoicing rules and VAT at 15% apply to the documents it produces. Sector context is on our telecom page.
We publish no prices, because a per-seat figure says nothing about your own total. Budget three years across five lines: concurrent or named seats at your real peak, telephony and messaging charges, the CRM and back-office integration, the bot and routing design that someone must keep current, and supervisor training. Seat counts sized on average load rather than peak are the single most common reason a contact centre budget is wrong.
The shortlist for a Saudi contact centre usually mixes global cloud platforms, regional suites and the contact centre module your existing CRM vendor sells. They differ most on Arabic handling, local telephony integration, and how much of the suite you will actually use. Our independent software comparisons set out the criteria we score them on.
We start from your traffic: volumes by channel and hour, what agents are actually doing, where handovers break. The requirement is written and weighted before anyone demonstrates anything, and scripted demonstrations are replaced with your own scenarios.
The CRM is the critical interface, then telephony, then whatever the agent needs open to resolve a case. We map every one before sequencing the rollout, because a platform that cannot show the agent the customer's history has moved the problem, not solved it.
Agents are trained on their own queues and their own scripts, supervisors on the reports they will run daily, and go-live is staged by queue rather than by switch-over date, with support on call through the first peaks. Adoption is the deliverable.
No percentages appear on this page. What we will say is structural: the centres that get value are the ones that redesigned routing before migrating it, rather than rebuilding yesterday's queues in a new tool. Ask us for references in your sector and we will arrange direct conversations.
We do not quote a duration before we have seen the operation. Seat count, channel mix, the number of integrations and how much routing redesign is in scope are what decide it, and all four are measured in the assessment before a timeline is written down.
Seats at real peak, telephony and messaging, CRM and back-office integration, bot and routing maintenance, and supervisor training. Section 4 sets out how we model it; the figures are yours, not a published average.
Compliance posture is configuration-specific and deployment-specific, so we verify it against your instance and your contract rather than repeat a claim. For a contact centre the obligations in scope are the national data-protection regime covering recordings, transcripts and retention, and ZATCA's e-invoicing rules with VAT at 15% wherever the platform touches billing. Where the data physically resides is a contractual term to be negotiated, not assumed.
Typically a global cloud contact centre platform, a regional suite, and the contact centre module your existing CRM vendor already sells you. The published starting point is our comparisons; the shortlist depends on your channel mix and Arabic requirements.
That is the normal design: the CRM stays the customer record, the back office stays where it is, and the contact centre platform becomes the channel and routing layer in front of them. What must be agreed up front is which system the agent works in, because an agent asked to work in two is an agent who works in neither properly.
The honest fast fact is that we publish no counters here. A project tally on a product page cannot be verified by the reader and cannot be kept current by the page. What can be verified is who and what, and that is available in reference calls arranged on request.
We name organizations only with their consent, and in conversation rather than in prose. References matched to your sector and seat count are provided on request.
Presented attributably in a first conversation — what was in scope, what changed in the queues, what it cost to get there. No unattributed outcome claim appears on this page.
We publish no testimonial quotations here. A quotation you cannot question is advertising; a reference call you can question is evidence, and the second is what we arrange.
Accreditations and partnerships are listed in proposals, where they are current and checkable. The claim worth verifying on this page is structural: our recommendation is not tied to a licence margin, and the section above on when we do not recommend it says plainly where this platform is the wrong answer.
Continue with CRM & contact centre for the category picture, telecom for the sector view, or our independent software comparisons.
Bring your channel volumes, your current queue structure and the systems you intend to keep. You will leave with a written fit verdict and the integration map behind it, whether or not the answer is inConcert. Book a session or ask for an impartial assessment.
Unlimited support included.
One-on-one onboarding sessions.
Training videos, webinars, & demos.