Known limits and support boundaries

For

All customers and evaluators

Owner

Product operations

Outcome

Identify unsupported or provider-controlled requirements before customer commitment.

Last verified

2026-08-30

Next review

2026-11-28

Status

supported

Review these boundaries before a purchase, migration, integration, or rollout. A planned or internal surface is not a supported customer contract.

Current product boundaries

• The public API supports only the three published Capture API operations.
• Zapier, Slack, Salesforce, HubSpot, Shopify, LeadSquared, and a generic public webhook are not supported public integrations.
• Provider approval, quotas, billing, external outages, carrier behaviour, and template approval remain provider controlled.
• Provider-backed email, WhatsApp, calling, and AI calling require customer and tenant setup before production use.
• These public guides are currently published in English.

Evidence boundaries

• A saved credential does not prove provider traffic.
• A local test does not prove the deployed service or customer workspace.
• A green pull request does not prove a production deployment.
• A deployed page does not prove a signed-in tenant workflow.

When a requirement is not listed

1. Record the required outcome, provider, region, data, scale, and timeline.
2. Ask Sakhaa support to confirm whether the requirement is supported, controlled, planned, or unavailable.
3. Do not commit the requirement to a customer until the approved owner confirms it.