- If independent review coverage is a strict procurement requirement
- Active.Ai has limited accessible peer review coverage compared with many mainstream SaaS vendors. If procurement decisions rely heavily on large review corpora, alternatives with more public feedback may be preferred.
- If a platform-first, fully customizable build is required
- For teams that want full control over architecture and have strong ML/platform engineering resources, a toolkit approach (Dialogflow/Vertex, Azure Bot Framework, etc.) may be more appropriate.
- If procurement requires strong public documentation of vendor stability and product continuity
- Active.Ai is post-acquisition (April 2022) and may be subject to rebranding, packaging changes, or roadmap integration into Gupshup. Buyers concerned about product continuity should obtain contractual clarity on roadmap commitments, SLAs, support ownership, and end-of-life policies.
- If publicly posted SOC 2/ISO documentation is a precondition
- Security certifications are not clearly documented in accessible sources on the Active.Ai domain; if a security team requires publicly posted artifacts to proceed, consider vendors with established public trust centers.
- Publicly documented limitations
- Vendor-acknowledged limitations are not clearly documented in accessible sources.
- Practical limitations to validate during procurement
- Post-acquisition product clarity
- Confirm current product naming, ownership, and whether Active.Ai is sold standalone or embedded in Gupshup offerings.
- Security and compliance documentation availability
- Confirm SOC 2 Type II, ISO 27001 status, penetration-testing cadence, and sub-processor lists.
- Governance for generative AI
- If generative AI is used, confirm guardrails, grounding via retrieval, evaluation methods, and auditability.