Client feedback and private team notes
Feedback is useless when it is detached from the post it is about. Every post carries its own conversation with the client, and a separate margin that only the team can read.
- A conversation thread on every post, shared with the client
- Internal notes the client can never see
- Slack sync, and exactly three workflow emails
Two audiences, two tabs
The conversation tab is what the client reads and writes. The internal-notes tab is for the team alone, and it is kept off every client-facing screen by the server — not by a checkbox someone has to remember. The tabs name the audience before a word is typed.
Internal notes save themselves as you type. There is no Save button to miss.
| Conversation | Internal notes | |
|---|---|---|
| Who reads it | Your team and the client | Your team only |
| Who writes it | Both sides | Your team |
| Used for | Change requests, questions, answers | Reminders, context, shorthand |
| Sending | Enter sends a message | Saves itself as you type |
What the client can and can’t see
- They see: posts sent to them for review, the conversation on each, and every decision
- They don’t see: drafts, internal notes, or the team’s planning view of the month
The line is drawn on the server, so a new screen can’t forget it. A draft doesn’t exist for a client until it is sent to them.
Notes on a specific slide
Clients can point at the exact image or video they mean, so “change the third photo” arrives attached to the third photo.
Slack, if that’s where your team lives
Link a client workspace to a Slack channel and the conversation flows both ways, with approval updates posted as they happen. Slack sync comes with the Agency plan.
Three emails. That’s it.
A client gets an invitation when you add them and an email when a batch of posts is sent for review; your team gets one when the review is complete. There are no per-comment emails and no daily digests — exactly three kinds of email, so the ones that arrive get read.
| Who gets it | When | |
|---|---|---|
| Invitation | The client | When you add them as an approver |
| Ready for review | The client | When you send a batch of posts |
| Review complete | Your team | When every post in the batch has a decision |
Resubmitting a fixed post doesn’t send another email: the client is already reviewing, and the post is back in their queue.
Why feedback belongs on the post
Feedback in email, chat and a shared doc has to be found, matched to the right version and copied into the fix. Feedback on the post is already in the right place, next to the thing it is about, with the history of every round above it. The approval workflow guide has more on running revision rounds.
Collaboration, answered
Can clients see internal notes?
Never. Internal notes are removed before any post data reaches a client, on the server.
Do clients get an email for every comment?
No. There are exactly three emails: the invitation, the review request and the review-complete notice to your team. Comments show on the post and, if you use it, in Slack.
Does Slack sync work both ways?
Yes. Messages in the linked channel and on the post stay in step, and approval updates are posted as they happen. Slack sync is on the Agency plan.
The whole workflow.
- Content calendar
- Client approvals
- Post previews
- Publishing
- Media
- CollaborationYou’re here
- Analytics
Get next month approved before it starts.
Start free with one client. No card needed — upgrade when the client list grows.