Clarify Feedback Instantly with Claro
Turn vague or emotional feedback into clear, actionable tasks — by asking the client the right question.
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.
Claro Personality Snapshot
Claro is Clarity & Strategy, and the only member of the team switched on by default — the others you choose, this one is already there. 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
| Stage | What happens |
|---|---|
| 1. Scoring | Every new comment is assessed for how clear and actionable it is — whether it identifies the exact element, and whether a developer or designer could act on it as written. |
| 2. Options | Where a comment is vague, Claro offers exactly three specific options, written in plain client language rather than technical terms, each applied in one click. |
| 3. Summary | Once the client picks, the clarified feedback is turned into direction your team can act on — describing what will look different rather than naming the setting behind it. |
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.
| Clarity | Example | What happens |
|---|---|---|
| Very low | “Fix this”, “broken”, “looks bad” | Clarification offered. |
| Low | Some context, but a critical detail missing | Clarification offered. |
| Clear enough | Actionable, with minor judgement needed | Passes through untouched. |
| Fully specific | Exact quoted text, or technical values | Passes through untouched. |
When Claro steps in
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.
| Captured | Why it matters |
|---|---|
| Screenshot | Shows the page as it was when the comment was left. |
| Element location | Identifies the exact element, not the general area of the page. |
| Device, browser and resolution | Explains issues that only occur on certain setups. |
| Canvas source | Whether the feedback came from WordPress or a live site. |
What the three options look like
Every option is something the client can watch apply to the element in one click, and they come in two kinds.
| Kind | What changes | Available on |
|---|---|---|
| Wording | The element’s actual text is rewritten and swapped in live. | Single text runs only — a heading, button, link, label or paragraph. |
| Look | Size, colour, weight, spacing, alignment or emphasis. | Both text runs and containers. |
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:
Where Claro works
Claro appears in more places than most people realise, and behaves differently in each.
| Where | What it does | How it starts |
|---|---|---|
| Collaborate URLs | Scores comments and offers three clarification options. | Automatic. |
| Page reviews | Opens the review with a plain summary of what’s being checked and why, then briefs the specialists before they start. | Automatic whenever a review runs. |
| Inbox | Brings the InnerCircle into a task thread — clarifying, suggesting, sanity-checking. | Switch on AI mode in the comment editor. |
| Workspace chat | Acts as project manager across every project, site and task, delegating work to the specialists. | Open the chat. |
| Onboarding | Introduces itself and guides initial setup. | Automatic during onboarding. |
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
AI mode joins an existing thread, so it answers with the task’s history in front of it rather than from scratch.
Instructions:
In workspace chat
This 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.
White-label behaviour
Working with the other specialists
| Agent | Contribution during feedback |
|---|---|
| Pixel | Validates whether visual feedback aligns with the design system. |
| Lexi | Reviews copy clarity where feedback affects CTAs or headlines. |
| Navi | Checks accessibility — contrast compliance, structure, keyboard and screen-reader use. |
| Glitch | Checks for broken links, missing assets, faulty form structure, and console errors where console output was captured. |
@innercircle, so feedback is processed. Discover Getting The Most Out Of The InnerCircle.
Frequently asked questions
Do I need to activate Claro manually?
No. It runs automatically on comments containing vague or ambiguous phrasing.
Why does it give options rather than just rewriting?
Because the client knows what they meant. Three specific choices in plain language resolve the ambiguity properly, rather than guessing at it.
Can I review the original comment?
Yes. The original and the AI-written task are both visible in the task thread.
What language are the options written in?
Plain, non-technical language. Technical terms never appear in what a client reads — an option is titled by the outcome it produces, not the technique behind it.
Where does Claro work?
Four places. Automatic clarification on Collaborate URLs; on-demand replies in the Inbox; as project manager in workspace chat; and during onboarding. It doesn’t run on Kanban boards or in design and image projects.
What happens when I select Clarify?
It confirms you want the original feedback clarified. The resulting task appears beneath the comment and is attached to the task thread.
Why is there no wording option on some elements?
Wording changes are only offered on single text runs. On a container, section, image or icon you’ll get three styling options instead.
Does the brand kit affect the options?
Yes. Where a project has a brand context set, options are grounded in that business — copy fits what the company does, and colour options use the brand palette.
Why do some vague comments pass through?
Scoring accounts for context. A comment pinned to an element already carries its location, so “make this bigger” can be actionable where it wouldn’t be in an email.
Can I dismiss a suggestion?
Yes. Ignore or dismiss it and the original comment remains untouched.
Can Claro change my client’s website?
From workspace chat it can install plugins and write settings, but destructive actions are gated — they come back as a pending approval for you to accept or cancel.
What happens on a site that isn’t WordPress?
You still get the advice and the deliverable. Claro will say plainly that the site can’t be changed and what would enable it, rather than reporting a change that didn’t happen.
Can a change Claro routed be undone?
Yes, at three levels: a single element from the copy saved before the change, a page through WordPress’s own version history, and a whole site only from a backup plugin installed on that site.
Will clients see the Atarim name?
Not in a white-labelled workspace. Claro presents itself under your agency’s branding instead.
Do other agents contribute?
Yes. Claro leads the clarification, and Pixel, Lexi, Navi and Glitch may add insight where the feedback touches their domain.
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. In the Inbox you switch AI mode on in the comment editor rather than it running by itself.
- 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 — check the AI icon is enabled, or tag @innercircle.
- 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.
Tips & best practices
- Encourage clients to leave any feedback — Claro thrives on vague input.
- Let the client pick from the options rather than choosing for them.
- Use shorthand internally and let Claro handle the rewrite.
- Review clarified tasks during stand-ups or sprint grooming.
- Confirm interpretations before implementing them.
- Ask clients to quote exact wording for copy changes — it lifts clarity immediately.
- Use the preview to show clients the result before committing to it.
- Set up the brand kit first — it makes the options specific to the client's business.
- Switch on AI mode in the Inbox when you want help working through a thread.
- Read approval requests properly before accepting — they're real changes to live sites.