Slack
Slack is how teams talk to John. Add him in your Slack workspace, then delegate in DMs and threads. Slack for John CEO is beta: the daily path is live, and we still label it as early access.
Telegram is the personal channel. See Telegram when you want a solo chat.
Install detail also lives on john.ceo/slack. This page is the product guide.
Before you start
Section titled “Before you start”- An activated John CEO account with work credits. Start here.
- Permission to install apps in your Slack workspace.
- One Slack workspace maps to at most one John CEO account. If that Slack team is already linked, the product will say so.
Install John
Section titled “Install John”- Open the john.ceo dashboard.
- Choose Install in Slack and complete Slack’s sign-in.
- Return to the dashboard and create your private workspace if you have not already.
- Wait until the workspace is running.
- Message
@Johnwith a real task.
If search across Slack (hosted Slack tools) shows that a reconnect or extra approval is needed, follow the banner on the dashboard. You can disconnect Slack from the dashboard at any time.
Where John replies
Section titled “Where John replies”- DMs and group DMs - message John directly. He reads and replies in that conversation.
- Channels -
@mentionJohn in a message or thread to start. - Active threads - teammates can keep replying in the same thread without mentioning him again.
- John does not reply to a channel message that has no
@Johnand is not already a John thread.
Teammates in the same thread share that conversation. What John reads in a channel stays in that channel. Direct messages never surface in channel answers.
Files, progress, and stop
Section titled “Files, progress, and stop”- Share files, PDFs, images, and (preview) videos in a conversation where John is already working. Ask him to review them.
- Long work can post progress updates in the thread. Newer progress replaces the last update instead of stacking.
- Tell John to stop in any language to halt a running task.
Voice notes and spoken replies are preview. Treat them as limited availability.
Slash commands and effort tiers
Section titled “Slash commands and effort tiers”/john help- short usage card/john status- workspace link status
In Slack you can steer how hard John thinks:
| Tag | Also | Use for |
|---|---|---|
!quick |
!q |
Short answers and light work |
!everyday |
!e |
Default for most messages (including Auto) |
!deep |
!d |
Harder reasoning |
!max |
!x |
Highest effort |
Pick the matching models in Settings. Telegram uses your Everyday pick.
The full AI Assistant experience inside Slack’s app container needs a paid Slack plan. On free Slack workspaces, DMs, threads, slash commands, and App Home still work.
Approvals in Slack
Section titled “Approvals in Slack”When John would send mail, change a record, or take another write in a connected app, he posts an approval card in the thread:
- Approve once, for this session, or always allow that kind of action
- Deny if you do not want it
“Always allow” now sticks so John stops re-asking about routine actions. Scheduled tasks that need approval also ask in Slack instead of silently stopping.
Telegram does not show the same in-thread buttons. Details: Approvals and Activity.
Scheduled briefs (beta)
Section titled “Scheduled briefs (beta)”You can ask John in a Slack thread to send a recurring brief. Delivery stays in that thread. This is beta. Do not expect posting to arbitrary public channels John has not been added to. Recipe: Recurring briefings.
Good habits
Section titled “Good habits”- Keep one thread per project or recurring job so context stays coherent.
- Say the outcome, the source apps, and whether he may send or only draft.
- Review anything legal, financial, or customer-facing before you treat it as final.