Review responses

Draft replies to public reviews, approved before posting.

A public review, good or bad, is read by the next customer as well as by the one who wrote it. This workflow drafts a reply to each new review in your tone, and nothing is posted until a named person has approved it.

A blue speech-bubble card and a white reply card hang from a brass rail that ends at a stop beside a red cord, and an owner's stamp waits on the other side of the cord.
A review and a drafted reply, stopped at the owner’s checkpoint before anything is posted.

Where this work slips today

Three messages lie apart on paper: an open slate blue envelope, a blue speech bubble and a lined form sheet. Beside each one is an empty dashed outline where a reply has not been written.
Reviews in three places, each still waiting for a reply.

Reviews arrive on several sites, and replying is one more task for whoever has a spare moment. Some get no reply, some get a rushed one, and a critical review can sit unanswered or be answered in a tone the owner would not have chosen.

How this runs

A rated message leads to a prepared reply, a rust checkpoint, the message paired with its reply and the closed green ledger. Dots under the stages count the five steps.
A new review, a drafted reply held at the checkpoint, the approved reply posted and the record. The dots under each stage count the steps below.

On Ateles, each new public review becomes a task that moves through a workflow we define with you before anything runs. Each step has a named owner, an agent or a person. The steps below are the intended design, not a record of work already running.

The five steps

  1. A new review appears. A review on a site you have connected, such as your business listing, is picked up. That becomes a task in the shared record, with the review and the reviewer’s public name.
  2. The agent drafts a reply. A short reply in the tone you approved: thanks for a good review, and for a critical one an acknowledgement and an offer to talk directly. It never discusses a client’s private details in public, and it can do only what its permissions allow.
  3. The checkpoint. A public reply always waits for approval. A named team member approves, edits or stops each draft, and a critical review goes to the person you named for it.
  4. The approved reply is posted. Only the text that was approved is posted, and only after that approval. Nothing is posted automatically.
  5. The record keeps it. The review, the draft, the decision and the reply as posted stay in the record, so the next reply can check what was said before.

Who does what

The agents do the preparing and your team does the deciding. That line is drawn before anything runs, and nothing crosses it without an approval.

  • The agents prepare. Picking up each new review, drafting a reply in the tone you approved, and noting which reviews already have one.
  • Your team decides. Whether to reply, what the reply says and who answers a critical review. A review that mentions a dispute or anything unusual goes to a named person.

Example: an agency

A client leaves a three-star review of an agency, saying a project ran late. The review becomes a task, and an agent drafts a reply that thanks the client, acknowledges the delay and offers to talk directly, without discussing the project in public.

The draft waits at the checkpoint. Because the review is critical, the agency’s rule sends it to the account lead, who edits a line and approves it. Only then is the reply posted. Each step stays in the record.

What the record holds, in order:

  1. The review as it appeared
  2. The reply the agent drafted
  3. The account lead's edit and approval
  4. The reply as posted

See what you could delegate.

A free, no-commitment 30-minute conversation. You leave with a clearer picture, whether or not you work with us.

A calendar card with one gold square filled in, beside a small blue notebook with a pencil lying across it.