Skip to main content

Chat with the COO

Home (/) opens chat with the COO. A compact How your company runs strip sits above the Home dashboard (expand it for the operating diagram). Use Chat with to switch employees. My Org holds the full architecture diagrams, org chart, departments (Design), and standups — How the company runs · Org and departments.

Send work​

  1. State the outcome in one message when you can (tell the COO the outcome first — count, deadline, budget, what must not happen). Do not open Workflow Builder until you inspect a Goal Plan step. Routine step retries and provider fallbacks do not need a follow-up message; only policy, auth, or a scope change will ask you.
  2. Attach files with the paperclip (documents, images, audio, video). Attachments go to Knowledge and inbound files.
  3. Replies render markdown. Generated images, audio, and video play inline while you are logged in.
  4. Small tool icons under a reply show what the employee used (knowledge search, email, notify, browser, and so on).

History and Browser session side panes start closed. Use the icons next to New chat. New chat archives the current thread.

On Home (/) and employee chat, the message box toolbar (next to the paperclip) includes:

  • Microphone icon — click, speak, pause 3 seconds after you finish; the transcript sends. Slow Caller uses this path (not a live call).
  • Speak checkbox — Piper plays the full assistant reply in chunks (no audio attachment in the thread).
  • Phone icon — live WebRTC when Channels → Voice is enabled on that employee (COO included). Slow Caller without Voice does not show Call.

See Channels and Hire AI employees.

How the COO delegates​

Clear specialty asks (“research X”, “draft a social post”) are handed to the matching employee with full context. Vague “help me” may stay with the COO.

The COO creates Kanban cards for specialty work. Watch the board and the bell when something needs you.

COO-native asks (list workflows, standups, tools, Kanban) usually stay with the COO.

If you want a specialist to reach you, say so (“have Research contact me”). That employee rings the bell with a link to their chat. Ordinary live replies should not spam the bell — ask them to notify you when async work finishes.

WhatsApp and Slack​

Configure Channels on the employee. Replies start with the employee name.

Slow Caller WhatsApp test: pair QR → from the allow-from number send text, then a voice note. Expect From: + text, and a voice-note reply. Not a live call. See Channels.

Platform Help​

For how-to, switch to Platform Help. It answers from product docs first. It may suggest the COO or Workflow Builder for live data or graph edits, but it should not bounce you with only “talk to X”.

A scored example of telling the COO the outcome first (seeded pipeline, live research, CRM approval path): Example stress test run.