Channels
API and Telegram access stay inside one reviewed SayHex access plan
API and Telegram are optional access channels for approved teams and follow the same project review, license scope, SCU planning, and audit expectations as protected portal work.
Planning focus
What buyers can plan on this page
Explain how API and Telegram access fit into the same reviewed license, project, and audit model as portal usage.
API access is planned, not assumed
Teams can discuss API use during review. Access follows the signed license scope, approved user roles, and Customer Admin provisioning instead of public self-service.
Telegram follows approved workflows
Telegram can support lightweight updates and approved workflow steps for provisioned teams without creating a separate privilege path or bypassing portal controls.
One reviewed boundary
Portal, API, and Telegram work all stay inside the same approved project, audit trail, and capacity plan before customer delivery begins.
Claim boundary
Public guidance can explain channel planning and approval expectations, but it must never expose credentials, endpoint details, setup secrets, or unsupported runtime promises.
Every public promise stays tied to reviewed access, approved channels, and the current maturity evidence.
Department inventory
18 platform departments can be compared before customer delivery begins
The catalog helps teams compare department scope, access channels, and readiness while customer delivery stays behind reviewed maturity evidence.
- SayHex 3D: 12 contract-defined capabilities
- SayHex Agent: 8 contract-defined capabilities
- SayHex Assistant: 7 contract-defined capabilities
- SayHex Business: 42 contract-defined capabilities
- SayHex Coder: 23 contract-defined capabilities
- SayHex Detector: 9 contract-defined capabilities
- SayHex Doc: 9 contract-defined capabilities
- SayHex Doctor: 14 contract-defined capabilities
- SayHex Financial: 9 contract-defined capabilities
- SayHex Food: 21 contract-defined capabilities
- SayHex Law: 11 contract-defined capabilities
- SayHex Live: 20 contract-defined capabilities
- SayHex Security: 15 contract-defined capabilities
- SayHex Smart: 19 contract-defined capabilities
- SayHex Studio: 18 contract-defined capabilities
- SayHex Support: 31 contract-defined capabilities
- SayHex Talent: 8 contract-defined capabilities
- SayHex Teacher: 36 contract-defined capabilities
Rollout planning
Choose the channel that fits the team workflow while keeping one approval, audit, and capacity boundary.
Use this route to prepare the next commercial or technical conversation, then continue through reviewed demos, licensing, and provisioning rather than public self-service.