Skip to content
ONE3.ai

Office · Module

Chats

Team messaging next to the record, with Digital Employees as members

Planned · Year 1 (W2)Sold as: CoreC-44

Chats is team messaging where work happens next to the record: channels, threads, DMs and record channels for a deal, ticket, project or client. Digital Employees can be channel members, and messages become tasks and governed Action proposals.

Chat that knows what it is about

Chats is eligible from W2 and planned for build in W3. In Year 1, Slack, Microsoft Teams and WhatsApp notifications plus in-app comments stand in for it. When Chats arrives, it covers the daily basics teams expect: public and private channels, DMs and group DMs, threads, reactions, mentions, edits with history, search, pinned messages, scheduled send and voice messages.

Record channels

One click creates a channel for a deal, ticket, project, client sub-account or employee onboarding. Membership follows the record's permissions, but a channel never grants record access by itself. Record events such as a stage change, an SLA warning or a signed envelope can post into the channel with filters. Shared channels bring in guests from client organisations with an external badge and their own retention policy.

From message to governed work

Any message can become a task or an Action proposal, such as updating a record or scheduling a meeting, with a diff and risk tier. Slash commands like /task and /approve invoke Actions directly. A message can be marked as a decision and sent to the Decision Journal. Announcement channels support read receipts for policy acknowledgements.

Digital Employees as members

Add a Digital Employee to a channel and it responds to mentions within its skills and autonomy, always with an agent badge and disclosure. Agents post only where they are members and never DM people unprompted unless their role is configured for it. Internal posts are R2; posts into shared external channels are R3 and approval-gated until earned.

Huddles and bridges

Audio huddles with screen share and camera run on the same LiveKit stack as Meet and can escalate to a scheduled meeting. A WhatsApp bridge is planned to mirror a client conversation into a record channel and transcribe Indian-language voice notes, where platform policy allows (verify).

Compliance built in

Retention per channel type, legal hold on channels and custodians, permission-scoped compliance export, admin redaction with a reason and guest controls are planned. Slack and Teams history can be imported with channel, user and file mapping, subject to export availability (verify).

Features

What Chats includes

Channels, DMs and threads

Public and private channels, DMs, group DMs, threads, reactions, mentions and edits with history.

Realtime delivery

WebSocket delivery with per-channel ordering and gap fetch; the database stays the durable truth.

Files as Drive files

Shared files are scanned and inherit permissions from the channel.

Search

Search across the messages and files you can access.

Record channels

A channel per deal, ticket, project, client or onboarding, with membership following record permissions.

Record events in channel

Stage changes, SLA warnings and signed envelopes posted with configurable filters.

Shared channels with guests

Client organisation guests with external badge, allowed domains, expiry and separate retention.

Huddles

Audio huddles with screen share and camera, escalating to a scheduled Meet meeting.

Slash commands

Invoke Actions such as /task and /approve from the message box.

Announcements with read receipts

Policy acknowledgements tracked per member.

Slack and Teams bridges

Notifications and approvals bridged to Slack and Microsoft Teams, continuing the Year-1 substitute.

Presence states

Available, busy, in a meeting, do not disturb, away and offline, with calendar-driven in-meeting status.

Retention, hold and redaction

Retention per channel type, legal hold, compliance export and admin redaction with reason.

History import

Import Slack and Teams history with channel, user and file mapping (verify export availability).

Workflow

Message to governed work

  1. 1

    A message is posted and fanned out to channel members in real time.

  2. 2

    If an agent is mentioned or a rule matches, the agent runs within its skills and autonomy.

  3. 3

    The agent or user creates a proposal: a task, a record update or a meeting.

  4. 4

    The Action Bus applies tier checks and approvals.

  5. 5

    The record changes and links back to the original message.

AI

AI skills and Digital Employees

Agent answers to mentions

Digital Employees respond within granted skills; external channel posts are approval-gated.

Message to task or proposal

Pre-fills a task or record update from a message.

Summaries and catch-up digests

Channel and thread summaries on demand or as a scheduled digest.

Decision capture

Proposes Decision Journal entries from marked messages.

Translation

Hindi and Tamil to and from English on demand, after evals.

Digital Employees that use this module

They act through the same governed Actions as people; risky steps wait for approval.

Frequently asked questions

What do I use for chat in Year 1?

Slack, Microsoft Teams and WhatsApp notifications and approvals plus in-app comments. Native Chats is planned for W3.

Does joining a record channel give me access to the record?

No. Record access makes you eligible for the channel; the channel never grants record access.

Can clients join channels?

Yes, as guests in shared channels with an external badge. Guests cannot be added to private internal channels.

Will agents message me unprompted?

No. Agents post only in channels where they are members and do not DM people unprompted unless their role is configured for it.

See Chats in your workflow

Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.