XCALLY Briefing

(XCALLY Motion / Asterisk-based Omnichannel Contact Center)

Executive Take

XCALLY is a flexible, Asterisk-based contact center platform aimed at organizations that want control, customization, and cost efficiency, especially in emerging markets or telephony-centric operations.
Strengths: deep telephony customization, open architecture, strong multichannel basics, API flexibility, and a highly configurable IVR/routing engine.
Weaknesses: limited AI, dated UI/UX, weak WEM, uneven omnichannel depth, and not designed for AI-era orchestration or large global enterprises.
Best for BPOs, telco-heavy operations, technical teams wanting customization, and regions where Asterisk expertise is abundant — not for AI-first or enterprise digital CX programs.

What’s True (first principles)

1. Architecture: Asterisk at the core

  • XCALLY Motion is built around Asterisk, meaning:

    • Very flexible telephony

    • Strong control over SIP, routing, IVR logic

    • High customizability via dialplan scripting

  • Not a pure cloud-native microservices platform; modernization exists, but Asterisk roots are always visible.

  • This architecture is stable for voice-heavy operations but not optimized for AI-first or complex omnichannel journeys.

2. Routing & Orchestration

One of XCALLY’s clearest strengths.

  • Skills-based routing

  • Complex IVR flows

  • Conditional logic

  • Data dips via APIs

  • Dialplan-level customization

  • Multi-queue distribution

Limitations:

  • No AI-driven routing

  • No attribute-based or real-time behavioral orchestration

  • Flow designer is powerful but technical, requiring telecom/VoIP skills

  • Harder to maintain at scale

Routing = great for custom telephony engineers; not friendly for CX ops teams.

3. Outbound Capabilities

Strong outbound tooling:

  • Predictive/power/preview dialer

  • Multicampaign management

  • Flexible list handling

  • Blended inbound/outbound

Very competitive for telesales, collections, and BPO work.

4. AI & Automation

AI is minimal:

  • Some speech-to-text

  • Basic sentiment

  • Chatbot integrations (3rd party)

  • Limited automation

Missing:

  • LLM-native agent assist

  • Conversation summarization

  • Knowledge AI

  • Autonomous orchestration

  • AI-based QA

  • AI-driven routing

AI posture = early-stage and lagging.

5. Omnichannel

Supports:

  • Voice

  • Chat

  • Email

  • SMS

  • WhatsApp

  • Some social channels (via connectors)

Strengths:

  • Channels integrated into a unified agent interface

  • Good flexibility for custom integrations

Weaknesses:

  • Digital UX is utilitarian

  • Limited async messaging features

  • No enterprise-grade omnichannel orchestration

  • Social care feels bolted on

6. WEM / Workforce

  • QA: manual with limited automation

  • WFM: not native; external tools required

  • Reporting: adequate dashboards, but not predictive

  • Workforce governance: minimal

This is not a workforce science platform.

7. Integrations & Ecosystem

  • Robust API layer

  • Integrates well with Salesforce, Zendesk, Zoho, Dynamics

  • Strong webhook/event architecture

  • Flexible for custom CRM or homegrown systems

  • Marketplace is small; developer-heavy environment

Great for technical orgs; less ideal for ops-led CX teams.

8. Economics & Operational Reality

  • Very cost-effective compared to enterprise CCaaS.

  • Attractive for mid-market or BPO operations with engineering support.

  • Requires internal technical expertise (SIP, Asterisk, routing logic).

  • Not suitable for organizations needing high governance or strict compliance.

What’s Off (gaps, hype, risks)

  • Not AI-era CCaaS: minimal AI and no orchestration intelligence.

  • Asterisk-based complexity: powerful but requires telecom engineers.

  • UX/UI dated: functional but nowhere near Talkdesk/UJET/Twilio.

  • Digital depth limited: insufficient support for modern async channels and social care.

  • Not scalable for global enterprise: governance + reporting limitations.

  • WEM deficiencies: no forecasting, adherence, or advanced QA.

Who XCALLY Is For

  • Technical teams wanting deep telephony customization.

  • BPOs and outbound-heavy operations.

  • Organizations in regions where Asterisk expertise is common (LATAM, APAC, EMEA).

  • Mid-market service centers with modest digital needs.

  • Companies wanting low-cost, highly adaptable CCaaS.

Who XCALLY Is Not For

  • AI-native organizations needing assist, bots, and workflow automation.

  • Digital-first brands with high social/messaging volume.

  • Regulated industries needing strong compliance/WFM.

  • Large enterprises with multi-region routing complexity.

  • Teams without telecom/VoIP engineering resources.

Do Next (actions, metrics, owners)

1. Routing Complexity Mapping (Owner: CX Ops + Telecom Lead)
Determine if XCALLY’s dialplan flexibility is needed.
Metric: <25 routing permutations → fine. >25 → complexity costs rise sharply.

2. AI Needs Assessment (Owner: AI/QA Lead)
Benchmark requirements for summarization, assist, automation.
Metric: If >20% interactions require AI → XCALLY becomes insufficient.

3. Outbound Fit Validation (Owner: Sales/Collections Ops)
Test predictive dialer performance.
Metric: target 90%+ connect rate efficiency for high-volume campaigns.

4. Workforce Management Gap Model (Owner: WFM Lead)
Identify external WFM/QA requirements.
Metric: incremental cost vs CCaaS with integrated WEM.

5. Technical Ownership Decision (Owner: IT/Telecom Leadership)
Assess internal capacity to maintain Asterisk-based routing.
Metric: at least 1–2 telecom engineers required for sustainable operations.

Forecast:

  • 2025–2028: Remains strong in technical, outbound-heavy mid-market + BPO environments (75% confidence).

  • 2028–2032: At risk against AI-native CCaaS unless AI + digital orchestration evolve (55–60% confidence).

Official website:
https://www.xcally.com/

Previous

Vonage
Next

Zai Lab