Client Feedback in Pastel → a Fully Revised Website Draft from One Slack Prompt

Let the client pin comments directly on the website draft in Pastel, in their own words. Then one line in Slack — "client has provided comments in Pastel — ferry" — and the agent fetches every pin, maps each to its exact page and element, makes all the revisions, and prepares a new draft with a per-comment report.

On-trigger (per feedback round)

What was getting in the way.

Client feedback on a website draft arrives as a pile — emails, calls, marked-up screenshots — and someone has to translate it into a task list, chase every item, and hope nothing got lost. A round with a dozen-plus comments can stall a launch for days before the first fix even starts.

Context

Client website builds for local service businesses — review rounds run through the client's feedback canvas.

How the work runs.

  1. 01

    The client pins feedback in Pastel

    Comments land on the exact spot they're about, no interpretation needed. In the pictured round: seventeen comments across five pages.

  2. 02

    One line in Slack

    A human sends a single prompt. No transcribing, no ticket-writing, no "as per my last email."

  3. 03

    Fetch and map

    The agent pulls every comment and maps each pin to its page and element. Repeated themes get grouped: a complaint made five different ways becomes one sitewide fix, not five patches.

  4. 04

    Judgment calls flagged, not buried

    Anything with business risk (like a requested perk worded in a way that could undermine the team's advertising rules) is flagged in the channel with a proposed safe phrasing before it ships.

  5. 05

    New draft, with receipts

    The agent builds every revision, then posts a per-comment pass/fail report. The team reviews outcomes, not effort — and the client sees a new draft with every point addressed.

Evidence from the workflow.

Blurred Slack conversation: a one-line ferry request and the agent's report mapping seventeen client comments from Pastel across five pages, with grouped fixes and a flagged judgment call
A one-line request and the agent's ferry report — seventeen client comments fetched from Pastel, mapped to their pages, revisions already running, and a judgment call flagged for the humans (names and figures anonymized).

Each system has a role.

  • The client's feedback canvas — comments pinned directly on the website draft

    Pastel

  • The one-line trigger, judgment-call flags, and the per-comment report

    Slack

  • Where the revisions happen

    Website build platform

Why this is Coworker.

Takes assignments and reports back. You hand it work, it prepares and returns a result.

  1. 01

    A human triggers the round and stays the judge — flagged items wait for direction, and nothing is called done without the per-comment report. The client never has to learn a new tool or talk to an AI; they just leave notes on their website.

Impact / Outcomes

An entire feedback round turns into a revised draft from one Slack message

Pins map to exact pages and elements — nothing lost in translation

Repeated complaints collapse into single sitewide fixes

Risky requests surface with a recommendation instead of shipping silently

A per-comment pass/fail report closes the loop on every single point

← All use cases

Find where a workflow like this fits.

Start with the systems, work, constraints, and authority already present in your operation.