Clarify Feedback Instantly with Claro

Feedback is often rushed, unclear or emotional, and each vague comment costs a round trip. Claro handles this differently from a plain rewrite: rather than guessing what “this feels off” meant, it asks the client to choose between three specific options — then hands your team the clarified result.

What Claro can do for you

• Turn a vague comment pinned to an element into three specific options the author can preview and pick, then write the result up for your team.
• Open every page review with a Strategic Overview of what is being checked and why, brief the specialists, and close with a summary: overall impression, recurring themes, top priorities and next steps.
• Pass a task thread to the right specialist when you select Send to Claro, so the answer comes from Pixel, Lexi, Navi, Index or Glitch.
• In workspace chat (Beta), create and assign tasks, hand work to the specialists, run workflows, remember standing rules for your workspace, and ask for your approval before anything changes on a site.

Claro Personality Snapshot

Claro is Clarity & Strategy, and it opens every review, while the other specialists are the ones you choose. It’s also the only one that doesn’t make anything. Pixel designs, Lexi writes, Glitch repairs; Claro is the orchestrator, deciding what the work actually is, who it belongs to, and handing it over. It sits a level above the specialists and never does their job itself, even when it could. When a review starts you’ll see it announce itself in the sidebar, Claro here, bringing clarity, and then get out of the way while they work.

Its instinct is to go under the request rather than take it at face value. Asked to move a button, it wants to know what moving the button was meant to solve — the problem, not the proposed fix. That’s the same instinct behind the three options: where intent is genuinely unclear, it would rather put two or three concrete readings in front of you than guess well and be confidently wrong.

In conversation it’s short. Warm in the way a capable colleague is over Slack rather than over email — no preamble, no sign-off, no restating your question back at you, and a brief answer to a brief question. Length gets earned by the work rather than taken as standard. When it hands clarified feedback to your team it shifts register slightly, opening a discussion rather than issuing instructions, because the point is to get the team talking about the best approach rather than to close the matter.

How it actually works

How a comment is scored

Scoring is the mechanism behind everything else, and it’s more precise than “vague or not”. Each comment is rated on two things: specificity — does it identify the exact element, page or feature — and actionability — could a developer or designer act on it as written.

When Claro steps in

• Vague client feedback
• Emotional or shorthand team notes
• Manual task creation with incomplete detail, where the task is pinned to an element
• Input flagged by other specialists

Typical triggers are comments like “doesn’t feel right”, “not sure about this section”, “make it pop”, “punch this up”, or “make this text better”. Well-intentioned, but not something a developer can act on without asking.

What comes with each task

Alongside the clarified wording, every task carries the technical context a developer would otherwise have to request.

What the three options look like

While Claro checks a comment, the thread shows Claro is checking. If the comment is too vague, Claro replies on it and offers the options. Everyone else on the project sees This comment is pending clarification review by the author.

Every option is something the client can watch apply to the element in one click, and they come in two kinds.

Each option is titled in the client’s own language, naming the outcome rather than the technique — “Make the headline stand out” rather than “increase the font weight” — followed by a sentence or two on what will look different and why it helps. Nothing technical — no setting names, no numbers — appears in what the client reads.

Previewing a change before committing

Options apply live to the element, so the client sees the result rather than imagining it. Colour, visibility, alignment and emphasis apply directly; size and spacing changes step up or down by a proportion of the element’s current value, so the result stays in keeping with the existing design rather than jumping to an arbitrary number.

Every option acts on the element the comment is pinned to, or something inside it — never a neighbouring or parent element.

What your team receives

Once the client has picked an option, Claro writes the result up for whoever has to act on it. It isn’t a rewritten version of the original comment — it’s a short message built from what the client actually chose.

It comes in three parts. An opening line saying the feedback was followed up and with whom, naming the client where their name is known. Then the interpreted changes as a numbered list, one short sentence each. Then a closing line inviting the team’s view on the best way to handle it.

The tone is deliberately collaborative rather than instructional — it’s opening a discussion, not issuing a work order. Everything is described as a visual outcome or an improvement for the visitor, never in technical terms, so it stays readable for anyone on the thread while being specific enough for a designer to act on.

Working with the clarified task

The resulting task is anchored to the exact element on the canvas, so the conversation stays attached to what it’s about.

Instructions:

1. Open the task from the element it’s pinned to.
2. Reply with updates, change the status or priority, reassign it to another teammate, or add tags.
3. Watch for related findings — the specialists stay active and will flag follow-up issues arising nearby.
4. Review the original comment alongside the clarified version. Both remain visible in the task thread.

Where Claro works

Claro appears in more places than most people realise, and behaves differently in each.

In page reviews

Every page review opens with Claro rather than with a finding. It writes the overview — what’s being checked, on which page, and what the review is aiming at — and then briefs the specialists on that intent before any of them starts looking. The findings that follow are theirs; the framing around them is Claro’s.

This is why a review reads as a piece of work rather than a list of complaints. Someone has set out what was being looked for before anyone reports what they found.

In the Inbox

There’s no AI mode to switch on in the Inbox, and a plain Comment never goes to the AI. You bring it into a thread when you want it, and it answers with the task’s history in front of it rather than from scratch.

Instructions:

1. Open a task thread in the Inbox.
2. Type your message, then select Send to Claro beside the Comment button, or @-mention InnerCircle or a specialist. Whichever specialist the work belongs to is the one who answers — Glitch for something broken, Lexi for wording, and so on — with Claro routing rather than replying itself.
3. Ask it to clarify something, suggest ideas, or sanity-check your thinking — all based on the thread’s contents.
4. Read the answer in the thread. It is posted under the name of the specialist who answered, with a Thought process link above it that shows how they worked it out.

In workspace chat

Workspace chat (Beta) is the largest of Claro’s roles and the one the feedback-clarifier name understates. In chat, Claro works at workspace scope across every project, site and task your agency manages, acting as project manager while the specialists do the work at project level.

Working in workspace chat

Workspace chat is where you talk to Claro about anything across your workspace: clients, projects, tasks and workflows.

Opening the chat

Instructions:

1. Select Projects in the sidebar. The chat sits to the left of your projects.
2. On a smaller screen, select the round chat button in the bottom-right corner instead.
3. To talk about one project, select Manage on its card to open its dashboard. The chat there has three tabs: Chat, Tasks for that project’s tasks, and Assets for its pages and artifacts.
4. Select Collapse chat to give the page more room, and Expand chat to bring it back.

Asking for something

Instructions:

1. Type in the box that reads “What are we working on today? Type / to see what I can do”.
2. To see what Claro can do, type / and pick a suggestion. They are grouped into Talk to the site, Create and execute, Content and assets, Workflows, Know what’s happening, Push out and connect, and Undo and restore. The suggestion is added to your message, so finish the sentence before you send it.
3. To add files, select +, then Attach a file. A message can carry up to 10 images, PDFs, HTML, JSON or text files.
4. To point Claro at a project, drag its card from the grid onto the chat.
5. Send the message.

Starting over or going back to a conversation

Instructions:

1. Select New chat (the pen icon) to start a fresh conversation.
2. Select Chat history (the clock icon) to see earlier conversations. A conversation still working on a reply shows Running. One whose last reply failed shows Failed. Open it and select Retry to run that reply again.

Follow-ups and workflow runs

When Claro plans to come back to something, for example to check on work that takes a while, the conversation shows Scheduled follow-ups above the messages, each with the time it is due. At that time Claro picks the conversation back up. Show message takes you to the reply that set it.

When Claro runs a workflow for you, a run card under its reply follows the run step by step and shows how it ended. Select the card to see its steps, or Open the full run to see the whole trace. If a run of a scheduled workflow fails, the card offers Re-run.

Approving from chat

When Claro needs your go-ahead, it says what it wants to do and why, and usually offers the choice as buttons in its reply. Select one, or answer in your own words, and Claro records your decision.

Instructions:

1. To see everything waiting, select Approvals at the top of the chat. In a project, requests are grouped under This project and Workspace account.
2. On Pending, read what each action will do, then select Approve or Decline. Approving runs the action.
3. Open History to see what was decided and how it went. Select Refresh approvals (the circular arrow) if a status looks out of date.

Once every request from a conversation has a decision, Claro picks that conversation back up with the outcome.

Each reply uses credits, charged on what it actually uses, at least 1 credit a reply. You need at least 10 credits available for Claro to start a reply. Explore Credits & Usage

Working with the other specialists

Frequently asked questions

Common issues

• Claro didn't clarify a comment — it was probably clear enough already. Scoring decides whether Claro steps in.
• Nothing happens automatically in the Inbox — expected. A plain comment never goes to the AI. Use Send to Claro, or @-mention an expert or InnerCircle.
• Nothing happens on a board or design project — automatic clarification runs on Collaborate URLs only.
• The rewrite misses the point — dismiss it. The original comment is unaffected.
• The AI isn't responding — the message was probably posted with Comment. Use Send to Claro, or @-mention InnerCircle. If Send to Claro isn't shown, your role doesn't have access to the AI.
• You can't find the original comment — both the original and the clarified version stay in the task thread.

Conclusion

Claro closes the gap between what someone meant and what your team needs to act on — not by guessing, but by scoring each comment for clarity and asking the client to choose between three specific options when it falls short.

The practical shift is that you can encourage clients to leave feedback freely. Vague input is what Claro is for. Discover Reducing Feedback Cycles with Visual Collaboration.