- If the organization is a small company (for example, fewer than about 50 employees) seeking low-cost, plug-and-play CX tooling, this vendor’s positioning and compliance posture may introduce heavier implementation and commercial overhead than SMB-first alternatives.
- If the primary requirement is a single vendor to deliver an end-to-end OSS/BSS mega-suite with large-scale systems-integration included, other vendors with established mega-suite offerings may align better depending on the program scope.
- If minimizing paid enhancements and change-order economics is a strict requirement, buyer-side negotiations and benchmarking are essential, as enhancement costs have been cited in reviewer feedback.
- If vendor transition risk is a primary concern, evaluate the implications of the NEC acquisition (completed May 2026) and confirm any changes to roadmap, commercial terms, or support models before committing to longer-term agreements.
- Portfolio clarity and scoping risk
- The corporate vendor label can map to multiple distinct products; procurement should require product-level references, SLAs, and scope definitions rather than vendor-level generalities.
- Pricing / enhancements
- Enhancement costs have been cited negatively in reviewer comments; buyers should clearly define configuration versus enhancement and include change-order governance in contracts.
- Security incident diligence
- A public report noted an investigation by a service provider into unauthorized access to provider data on a vendor platform in early 2025. Buyers should review incident-response SLAs, notification obligations, tenant-isolation design, logging/auditability, and breach-forensics support during diligence.
- Public documentation gaps
- Data residency details and a feature-by-feature security-controls matrix were not found in a single public source during this research pass; expect some documentation to be gated or NDA-restricted.