EchoPilot and Slack

Not every outcome of a meeting is a task. Often it is a message: telling the team what was decided, confirming something to a channel, passing on the part that affects someone who was not there.

Slack is the destination for that, and it is the one where the review step matters most, because a message is the only kind of action other people see immediately.

What gets posted

A message, with the full wording. When you dictate something to send, EchoPilot keeps what you actually said rather than compressing it into a headline. Dictate three sentences of context and three sentences of context are what gets drafted. A summary of your own message is not what you asked for.

The card shows a short headline so you can recognise it in the queue, and the body underneath is the message itself.

Nothing is posted until you approve it

Every other destination creates something private to you. Slack posts in front of your colleagues, so the approval step is doing real work. Read the message, edit the wording, change the destination, or discard it. Nothing reaches Slack until you confirm.

There is no setting that turns this off.

Connecting

Connect Slack in Settings through OAuth, choosing the workspace and the channels EchoPilot may post to. Credentials are encrypted at rest, and you can disconnect at any time. Disconnecting stops future cards routing to Slack and leaves everything already posted alone.

When Slack is chosen

EchoPilot routes here when you name it: “send that to Slack”, “post it in the channel”, “message the team”. Left unnamed, a commitment goes to a task destination instead, because most things people say in meetings are work to do rather than announcements to make.