Internal comments
Internal comments are private team notes you pin on your live pages from the admin bar. Only your team can see them, until you choose to share them into a review. Internal comments are included on the free plan.
What they are for
They give your team the same pin-on-the-page workflow you already use with clients, but kept private. Typical uses:
- An internal QA pass before a page ever goes to the client.
- Notes between a designer and a developer on the same build.
- Content to-dos, such as placeholder copy or an image still to be swapped.
- Recording a decision on the page it applies to, rather than in a chat thread nobody can find later.
How to leave one
- Open any page on your site while logged in to WordPress.
- Use the internal feedback button in the admin bar to enter comment mode.
- Click the element you want to note, and write the comment.
Internal notes behave like ordinary pins: they anchor to the element, capture a screenshot and page context, and support threaded replies, statuses and assignees. Colleagues can also propose wording changes on them with suggest edits.
Where they work
Internal comments work on any page, not only single pages. That includes archive and listing pages, the blog index and search results, which is useful because those templates are exactly where problems are easy to miss and hard to describe in words.
Who can see them
New comments from the builder and the internal Feedback button start as Internal. Opening a client review link does not change that default. Internal comments stay hidden from clients unless you deliberately share them. Comments marked Private are visible only to their author, including on the Feedback screen, and are never sent to Reviso Cloud or AI tools.
Privacy is enforced on notifications too: if a thread is made internal after someone has replied, that reply is not emailed to a client who is not part of your team.
Sharing a note with the client
On the review’s edit screen, Share active internal comments with the client lets that review show internal notes that are still open. Notes already resolved before you enable sharing stay hidden. Turn sharing off to hide internal notes from that review again. Mark an individual thread Everyone to share it, or Private to keep it visible only to its author. Check the audience label on the Feedback screen before sharing sensitive notes.
Notifications and integrations
Webhooks carry a comment’s visibility, assignee, attachments and screenshot, along with the page context for notes left on archive pages. That means a Slack, Discord or automation workflow can tell an internal note apart from client feedback and route the two differently.
Common questions
Can clients ever see internal comments?
No, unless you share the thread into a review yourself.
Do internal comments cost anything?
No. They are included on the free plan.
Do I need an active review to leave one?
No. Internal comments are independent of client reviews, so you can annotate a page at any point in a build.