- If you are not a telecom/CSP or do not have telco-style B2C+B2B complexity
- The product is specifically positioned for telecom operators; non-telco industries may find generalist CX suites better aligned to their needs.
- If your primary need is Voice-of-the-Customer analytics and survey programs
- The vendor presents CXP primarily as a digital self-service and marketplace layer. If primary objectives center on feedback collection, advanced VoC analytics, and closed-loop actioning, dedicated VoC platforms may be more appropriate.
- If you need independently validated public proof (reviews, benchmarks, security certifications)
- Limited accessible third-party reviews and limited published security certifications can be a procurement blocker in regulated environments.
- If you cannot support integration and change management
- Telco digital experience rollouts are typically integration-heavy; organizations with limited architecture and delivery capacity may prefer a narrower solution or a managed front-end offering from their existing BSS vendor.
- Current limitations acknowledged by the vendor
- The public product page focuses on features and benefits and does not list explicit limitations.
- Features on the roadmap (not yet available)
- No specific roadmap dates or feature release plans were available in accessible sources.
- Scale limitations
- The vendor describes scalability but does not publish benchmarks (concurrent users, throughput, latency). These should be requested and validated with reference customers or via performance tests.
- Security or compliance gaps
- Main gaps in public documentation are the absence of published SOC 2 or ISO 27001 attestations and limited security documentation specific to the product.
- API limitations or integration constraints
- The vendor references an integration layer but does not publish public API documentation for CXP; potential integration constraints should be validated during technical due diligence.