Product Release Notes

Release history for Akontec's platforms. Client-facing where a client uses the product; internal for pre-release work.

Akontec AI Support Operations

Initial release — 01 August 2026

Super-admin and BPO workspace platform, 34 pages: 20 super-admin, 14 BPO workspace.

Architecture: AI Solution → Deployment → BPO Workspace. Workspaces are data-isolated; no tenant can access another tenant's data.

AI solution lines (8): Call Taxi · E-commerce · Finance · Real Estate · Franchise · AI SaaS Sales · Healthcare · Travel & Holidays.

Super-admin capability: partner and workspace management, deployment control across solution lines, AI agent configuration, commission and revenue views, platform-wide reporting.

Workspace capability: the BPO Service Provider's own view — their agents, their deployments, their employees, their performance, isolated from every other tenant.

Design system: navigation rail #0D1526 · crimson #E4262C · workspace background #F4F6F9 · Plus Jakarta Sans, JetBrains Mono.

Demonstration dataset: 42 partners · 38 workspaces · 42 deployments · 156 AI agents · 1,286 employees · 22% blended commission. Demo data only — no customer data appears in any environment used for demonstration or recording.

Omnetra BPO OS

Multi-tenant BPO operating system. Specification, design reference and static build complete. See 10_SaaS_Products/02_Omnetra_BPO_OS.md.

AI eCommOps

AI-powered e-commerce operations admin platform. 30-module static build complete. See 10_SaaS_Products/04_AI_eCommOps.md.

projects.akontec.com — Partner portal

Partner-facing portal covering 25 projects with banners, documentation and the billing request workflow. The billing request workflow enforces reconciliation before invoicing, which is the sequencing control described in 23_Finance/02_Invoice_And_GST_Standards.md.

Kontact

Free chatting and messaging application. Naming and branding established. See 10_SaaS_Products/05_Kontact.md.

Vertical dashboards

Release note standard (for future entries)

## [Product] v[x.y] — [DD Month YYYY]

**New:** [features added]
**Changed:** [behaviour changes — the section clients actually need]
**Fixed:** [defects resolved, with ticket references]
**Deprecated:** [what is going away, and when]
**Action required:** [anything a client or partner must do]
**Downtime:** [scheduled window, or none]

Rules

1. Behaviour changes are stated prominently. A client who discovers a changed workflow by having it break is a support ticket and a lost hour of their day.
2. Breaking changes require notice before release, per the client's contract.
3. Scheduled maintenance: minimum 48 hours' notice, lowest-traffic window for that client (17_Support/03_Priority_Matrix_And_SLA.md).
4. Emergency security releases proceed with as much notice as is safely possible, always followed by a written explanation.
5. Every release note is checked against 27_Guardrails/03_Restricted_Statements.md before issue — release notes are a common place where "seamless" and "world-class" reappear.