Sakhaa glossary
Use consistent terms for customer records, revenue work, communication, and proof.
- For
- All customers and partners
- Owner
- Product operations
- Outcome
- Use the same customer and operating terms across Sakhaa work.
- Last verified
- 2026-08-30
- Next review
- 2026-11-28
- Status
- supported
Use these terms in training, support, integrations, and operating records. A shared vocabulary reduces duplicate records and unclear ownership.
Customer and revenue terms
| Term | Meaning |
|---|---|
| Person | The canonical individual customer or contact record. |
| Account | An organisation or customer group linked to people and revenue work. |
| Deal | A qualified revenue opportunity that moves through a pipeline. |
| Pipeline | The approved stages used to track a deal from start to outcome. |
| Task | A next action with an owner and due date. |
Connection and proof terms
| Term | Meaning |
|---|---|
| Provider | An external service used for email, messaging, calling, identity, or another connection. |
| Webhook | A protected provider-to-service event path. Only approved public contracts are documented. |
| Idempotency key | A client value that prevents the same logical API request from creating duplicate work. |
| Local proof | Evidence from code, tests, or a local build. |
| Production proof | Evidence from the deployed service and the required customer or provider path. |
Use terms consistently
- Use person instead of lead or contact when you mean the canonical customer record.
- Name the provider and proof level when reporting a connection result.
- Name the workspace, role, record, action, and approximate time when reporting a problem.