Native channels
Voice and live chat are native. WhatsApp, Facebook, and SMS require their respective eligible accounts or supported providers; email is not listed as a native 3CX contact-center channel.
Plan eligible 3CX contact-center capabilities by edition, channel provider, privacy responsibilities, and operating requirements.

Voice and live chat are native. WhatsApp, Facebook, and SMS require their respective eligible accounts or supported providers; email is not listed as a native 3CX contact-center channel.
Queue and routing options depend on edition and configuration. BASIC explicitly excludes call queues.
Recording availability depends on edition. The PBX owner is responsible for lawful notices, access, retention, and review procedures.
PRO is documented with reports, queues, and wallboards; exact advanced entitlements must be checked in the current matrix.
WhatsApp conversations are subject to Meta requirements, inbound initiation, and the documented 24-hour response window.
Supervisor and routing functions are edition-dependent and should be listed explicitly in the approved scope.
The current official material lists voice, live chat, WhatsApp, Facebook, and SMS through a supported provider. Email is not listed as a native channel. External channel accounts and restrictions apply.
No. The current BASIC restrictions explicitly exclude call queues and call recording.
PRO is documented with core call-center, CRM, reporting, queues, wallboards, and messaging. Advanced routing, recording, transcription, and supervisor requirements must be checked item by item against the current matrix.
ECOLOR can map channels, editions, provider accounts, routing, privacy duties, and measurable acceptance criteria without promising business outcomes.
Continue to the most requested 3CX topics.