Review requests

Satisfied clients are asked for a review at the right moment.

A review is easiest to ask for just after a good visit, class or purchase, and just as easy to forget that week. This workflow prepares a short request at the right moment for the clients you choose to ask, and leaves out the ones you do not.

A white card with a row of five dots, four filled in ochre and the fifth an empty outline, with a blue envelope lying across its lower corner.
A prepared request for a review, held for the owner's approval.

Where this work slips today

A calendar card with one gold square, then a dashed outline of an envelope where no request has been prepared, then a card with a row of five empty gold rings.
A completed visit, no request prepared, and no review.

Asking for reviews depends on someone remembering to do it. It happens when there is a free moment, and it is easy to ask the wrong person: a client with an open complaint, or one who was asked only recently.

How this runs

A calendar and card lead to a prepared envelope, a rust checkpoint, a rating card with its envelope and the closed green ledger. Dots under the stages count the five steps.
A completed visit, a prepared request held at the checkpoint, the request sent and the record. The dots under each stage count the steps below.

On Ateles, each client who may be asked for a review is a task. The task moves through a workflow we define with you before anything runs, and 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 client may be asked. A completed visit, class or purchase in your own tools marks a client as someone you may ask. That becomes a task in the shared record.
  2. The agent checks the rules and prepares a request. It checks the rules you set, for example who should not be asked, and prepares a short request for the right moment. It can do only what its permissions allow.
  3. The checkpoint. Anything sent outside the business waits for approval by default, so a named team member approves, edits or stops each request.
  4. The request goes out. Once approved, the request is sent to the client.
  5. The record keeps it. Who was asked, when, the message and the decision stay in the record, so the next request can check who has already been asked.

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. Checking each client against your rules, preparing a short request for the right moment, and noting who has already been asked.
  • Your team decides. Whom to ask and whom to leave out, and the tone of each request. A client with an open complaint, or anything unusual, goes to a named person.

Example: a fitness club

A member finishes a block of classes at a fitness club. The club’s system marks the member as someone it may ask. The member becomes a task, and an agent drafts a short request for a review in the club’s usual tone.

The request waits at the checkpoint. The club’s manager approves it, edits a line or stops it. If the member has an open complaint, the rule the club set sends the case to a named person. Each request and decision stays in the record.

What the record holds, in order:

  1. The completed block of classes
  2. The request the agent drafted
  3. The manager's decision
  4. The rule that sends a member with an open complaint to a named person

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.