Product fit and supported limits

For

Evaluators, admins, and security reviewers

Owner

Product operations

Outcome

Confirm that the supported Sakhaa product fits the customer use case.

Last verified

2026-08-30

Next review

2026-11-28

Status

supported

Customer journey

Evaluate and secure

Estimated time

15 min

Permissions and roles

Evaluator · Company admin · Security reviewer

Open the completion checklistSteps, proof, and recoveryClose checklist

Prerequisites

• A clear business use case
• A list of required channels and integrations
• The customer data, retention, and security requirements

Permissions in practice

• Evaluator: review public product and support boundaries.
• Security reviewer: approve data, access, and provider scope.
• Company admin: validate the workspace setup path.

Steps

• List the customer records, pipeline work, communication channels, and reports that must work.
• Compare each required outcome with the supported product and integration catalog.
• Review security, privacy, retention, access, export, and support responsibilities.
• Record provider approvals, DNS access, consent rules, limits, owners, and the fallback plan.
• Run the admin first-value journey with synthetic data before making a rollout decision.

Success proof

• Every required customer outcome has a supported guide and a named owner.
• The security reviewer can explain what Sakhaa controls and what providers control.
• The team records an explicit go, narrow-scope, or do-not-proceed decision.

Common failures

• A required provider or workflow is not in the supported catalog.
• The data owner, security reviewer, or support owner is not named.
• A provider approval, DNS, consent, or retention requirement is still unknown.

Recovery

• Ask Sakhaa support to confirm an unlisted provider or workflow before committing to it.
• Narrow the rollout to the supported CRM core while the dependency is resolved.
• Record the open decision and do not describe an unverified capability as available.

Rollback

• Stop the evaluation before importing or connecting real customer data.
• Remove only approved synthetic test records and preserve the decision record.

Next task

Run Admin first value in 60 minutes.

Open next guide

Use this guide before setup. It separates supported customer capabilities from internal, tenant-specific, pilot, and provider-controlled work.

Start from the customer outcome

Sakhaa is a customer relationship workspace for customer records, revenue work, communication, automation, reporting, and controlled AI assistance. Confirm the required workflow and users before selecting connections or importing data.

• List the customer records, pipeline, communication channels, and reports that must work.
• Confirm the admins, managers, frontline users, developers, and security reviewers involved.
• Identify provider approvals, DNS access, consent rules, and data-retention requirements.
• Treat a feature as supported only when it appears in this public documentation.

Understand the boundaries

Provider approval, carrier behavior, external quotas, and third-party outages are outside Sakhaa control. Internal platform pages and application endpoints are not public customer contracts.

If a required provider or workflow is not in the supported integration catalog, ask Sakhaa support before committing to it.

Verify before rollout

1. Complete the 60-minute admin first-value journey in a clean workspace.
2. Test each required integration with synthetic data and no real provider traffic where possible.
3. Confirm roles, exports, retention, recovery, and support ownership.
4. Record the accepted limits and provider dependencies for the customer team.