IO Chat™, reach the person where they already are.
Task notices, coaching messages and report links are delivered as a direct message carrying a signed link. Opening the link returns the recipient to IO, where the response is recorded against the task. Delivery goes out; the answer comes back through IO, not through the chat window.
Reply and acknowledge, not a conversation.
Seen, and accepted as mine. The task has a named owner from that point.
A question raised against the task, visible to whoever prescribed it.
Recorded as a disagreement with the reason, rather than as silence that reads as refusal.
Accepted with an intended date, which is what the execution record and the baseline attach to.
What has to be true for a message to arrive.
Delivery resolves the recipient through the connected tenant directory. If the person does not exist there, a contractor outside the tenant, a stale address, a mailbox that was never provisioned, the message cannot be delivered, and IO records the failure rather than assuming it landed.
That is a real failure mode and it is worth stating, because a task notice nobody received looks identical to a task notice everybody ignored unless the platform distinguishes between them.
The design intent is not to become another chat product. It is to remove the excuse that the task was never seen.
See it before you talk to anyone.
Two quarters of recorded activity across sixteen seats. One click, no install.