What's New in COnnect

September 10, 2026 · Product update

More reliable customer conversations across Web, Admin, and App.

Read the latest improvements to handoffs, Telegram session stability, chat performance, media playback, and admin conversation review.

Read the update

Version 1.2.0 · Current release

Organization governance, approval control, and customer response visibility.

COnnect 1.2.0 turns communication management into a governed business workflow: people belong to departments, roles decide long-term access, data scope limits visible records, and high-risk access can require temporary approval.

1Build organizationDepartments, employees, roles

2Define accessMenus, pages, buttons, data scope

3Review riskApproval rules, credentials, logs

4Follow customersOwners, tags, pending replies

Organization and permissions

Purpose: Make company structure, employee responsibility, and data access boundaries visible in the admin console.
Entry: Admin Console → Organization & Permissions.
Workflow: Create departments, maintain employee profiles, assign roles, choose data scope, and move employees through controlled departure and handover when needed.
Key rule: Role permissions control long-term access; organization scope controls which records an employee can see.
Common mistake: Do not treat a customer as an employee unless the account has an organization department and employee profile.

Approval gateway and risk logs

Purpose: Add temporary review to high-risk menus, pages, and button actions without replacing normal role permissions.
Entry: Admin Console → Governance Configuration → Gateway Rules, Authorization Center, Credentials, Risk Logs.
Workflow: Choose a resource, set the review level, let the requester apply after seeing a no-access prompt, then approve or reject from the authorization center or system message.
Key rule: If no enabled rule matches, the action is allowed by the gateway but still recorded in the risk log.
Common mistake: An approval credential is temporary. It does not give permanent role permission or bypass organization data scope.

Customer lifecycle and pending replies

Purpose: Keep customer ownership, activity, labels, follow-up events, and reply status visible for managers and employees.
Entry: Admin Console → User Center → COnnect Customers / Telegram Customers. App and PC Web show pending-reply customers in the communication workspace.
Workflow: Customer activity updates lifecycle labels, follow-up events explain status changes, and pending-reply reminders help employees respond before a conversation becomes stale.
Key rule: COnnect private chats and Telegram private chats are included. Muted conversations are excluded unless the customer mentions the employee directly.
Common mistake: Message count, chat records, owner list, and follow-up timeline should describe the same customer relationship. If they do not line up, the data should be reviewed.

Version 1.1.0

Subscription accounts, tasks, intelligent service settings, and Telegram operations.

COnnect 1.1.0 expanded daily operation tools around customer communication, content delivery, task collaboration, and supported Telegram administration.

Subscription accounts

Admins can create subscription accounts, publish rich content, manage visibility, and review reading or button-click statistics. Official subscription accounts can appear without requiring customer subscription.

Tasks

Employees can create tasks from chat context, assign owners, comment, complete work, and review task details on supported clients. Admins can review task volume and details.

Intelligent service settings

Teams can configure text-based intelligent service profiles, callback interfaces, open API credentials, connection tests, and message logs to connect their own text service.

Telegram customer operations

The current public channel integration is Telegram. Admins can manage company Telegram accounts and review Telegram customers, groups, owners, and chat records where supported.

How we publish updates

Only released capabilities are described as available.

COnnect release notes are written for customers, not internal planning. Future ideas, unverified integrations, and internal stage names are not shown as live product capabilities.

Accurate channel scopeTelegram is the current public external-channel integration. Other channels are not listed as available.

Clear access languageRole permission, organization data scope, and temporary approval are explained as separate controls.

Practical workflowsEach update names the entry path, normal flow, important rule, and common mistake.

COnnect product updates for secure communication and enterprise governance.