Review request scripts that work

On 13 July 2026 the federal government asked every angler in the South Atlantic to comment on a proposed change to blueline tilefish catch levels. Plain-language summary, single portal, hard deadline, named contact, thirty days.

By the middle of the following week it had seven comments. Seven, on a rule affecting a whole fishery, from the best-structured request for public input anybody publishes. Which settles a question guides spend a great deal of time on: the wording of the ask is not the constraint. What that request does have is a design worth copying line for line, because every element in it exists to remove a reason not to respond. What follows is that design, applied to a review request, and then the actual messages. Adjacent pieces are grouped on the getting-booked hub.

What does that request actually contain?

Six parts, and most review requests carry two of them.

It opens by stating that a plain language summary of the proposed rule is available, and gives the address where it sits.

It names the identifier the comment must carry, so nothing has to be described from memory.

It gives two submission methods, an electronic portal with step-by-step instructions and a postal address with a named recipient.

It sets a deadline in the dates section: written comments must be received no later than 12 August 2026.

It warns that comments sent by any other method, to any other address or individual, or received after the comment period, may not be considered.

And it ends with a named person, a telephone number and an email address for further information.

The rule is published by the Federal Register.

Lady J Sportfishing, MA

What did all that design produce?

Seven comments, checked a week in.

The Federal Register record for that proposed rule shows the docket carrying seven comments when the count was last checked on 18 July 2026, five days after publication.

The docket is public, the comment period ran a full thirty days, and the subject is a catch level that directly affects what a South Atlantic operation can sell.

Nobody could reasonably argue the request was badly written, badly routed or hard to find.

Which is the useful lesson, and it is not a flattering one for anybody selling review-request wording as the lever.

The number of responses tracks the number of people asked and how directly it touches them, far more than it tracks the phrasing.

So a guide's leverage is coverage and timing, and the script's job is simply to avoid giving anybody a reason to stop.

The coverage side of that is worked through in the getting reviews piece.

Which part do guides always leave out?

The warning that the response is public.

The federal request states that all comments received are part of the public record and will generally be posted for public viewing without change.

It goes further and says that all personal identifying information, confidential business information or otherwise sensitive information submitted voluntarily will be publicly accessible.

It then offers a route for anybody uncomfortable with that, noting that anonymous comments are accepted and telling the reader to enter a placeholder in the required fields to remain anonymous.

Almost no review request tells the client that what they write will sit under the business's name in public, permanently, attached to whatever their account displays.

Saying so costs one sentence and removes the most common private reason people do not respond, which is uncertainty about who will see it.

It also makes the request read as honest rather than as a favour being extracted.

The portal that hosts those public comments is regulations.gov.

What is the deadline actually for?

Removing the option to deal with it later.

The rule states that written comments must be received no later than 12 August 2026, which is a specific date rather than a period.

Then it says what happens to a late one, which is that it may not be considered.

Both halves matter. A date without a consequence is a suggestion, and a consequence without a date is a threat.

A review request has no equivalent consequence, and inventing one would be pressure, which is the thing the platform rules exist to prevent.

What it can have instead is a reason the timing matters to the reader rather than to you, which is that the day is fresh and they will remember what it was actually like.

That is true, costs nothing, and does the same work without manufacturing urgency.

The supporting material for that rule sits on the NOAA Fisheries action page.

Why give only one route?

Because a choice is a place to stop.

The federal request offers two routes and immediately narrows them, warning that comments sent by any other method, to any other address or individual, may not be considered.

That is a request with a boundary drawn around it, and the boundary is what makes the instruction followable.

A review request offering the profile, the website form, an email reply and a text message is offering four opportunities to think about it.

One link, going to one place, with nothing between the tap and the box, is the whole design.

Anything that adds a step, including a landing page explaining why reviews matter, is a step at which people leave.

Test the link yourself from a device that is not signed into your own account, because that is the journey the client is making.

The profile that link should land on is set up in the profile setup piece.

Bottom Line Sportfishing, DE

The message for the day after

Four sentences, sent the morning after the trip.

Good morning. Yesterday on the west shoreline the wind laid down about ten and we found fish in the last two hours, which was worth the wait.

If you have five minutes, an honest account of the day on our Google listing genuinely helps a one-boat operation, and whatever you write is what is useful.

Anything you post there is public and stays under my business name, so write it however you would tell a friend about it.

Here is the link, and either way it was a good day to be out there.

Note what the four sentences do: they prove you remember the specific day, they ask once, they disclose that the result is public, and they close without pressure.

Note also what is absent, which is any suggestion of what to mention, any offer of anything, and any reference to stars.

The debrief that produces the detail in that first sentence is described in the trip debrief piece.

The message for the weekly batch

Three sentences, sent to everyone who fished that week.

Thanks for coming out on the eleventh, the water was a lot clearer than it had been and you handled that first drift better than most.

If you have a minute, a review on our Google listing helps people work out whether we are the right boat for them, and an honest one is the useful kind. Whatever you write is public and stays there.

Link below, and I hope we get you back out.

The weekly version is shorter because it is going out in a batch, and a batch message that tries to be personal in six sentences reads worse than one that is brief and specific in three.

The date and the one true detail are what stop it reading as a template, and both come from a list you kept during the week rather than from memory on the day.

Everything else is identical for every recipient, which is the point, because identical is what compliant looks like.

Which channel carries it is settled in the text versus email piece.

The message for a returning client

Two sentences, and it acknowledges the history.

That is four seasons now, and yesterday was the best conditions we have had in October in a while.

If you have never left a review and would be willing to, the link is below, and an honest one from somebody who has fished with me repeatedly is worth more than a dozen from people who came once.

That last clause is true and is not a request for specific content, because it says nothing about what the review should say.

A returning client is also the person most likely to write something with texture in it, since they have a basis for comparison.

Ask once, never twice, and never make the request a condition of anything about the next booking.

If they decline or ignore it, the relationship is worth more than the review and the subject is closed.

The rebooking conversation that runs alongside this is set out in the rebooking ask piece.

What can never appear in any of them?

Six things, and the first two feel harmless.

Any suggestion of what to mention, including the species, the boat name, the town or the word excellent.

Any offer of anything, including a discount on a future trip, a hat, or priority on a date.

Any reference to a star rating, which converts an open request into a specification.

Any second ask to somebody who did not respond, which turns a request into pressure by repetition.

Any suggestion that the review is needed, owed, or would be a personal favour.

And any variation in who receives it, since the message going only to the good days is the failure the whole system is designed to avoid.

The published prohibitions behind those six are set out in the reviews strategy piece.

Where do the scripts fall down?

Seven failures, and most are structural rather than verbal.

Sending it a month later, when the client cannot remember the date, the water or the captain.

Sending a template with no specific detail, which reads as a broadcast and gets treated as one.

Writing six paragraphs, which converts a small request into an obligation.

Apologising for asking, which tells the reader the request is an imposition.

Offering four ways to respond, which is four places to defer.

Linking to a page that explains the importance of reviews before the box appears.

And never sending it during the busy months whatsoever, which is the failure that dwarfs every wording question.

The addresses that make sending possible are gathered per the email capture piece.

What do you send after a blank day?

The same message, and the honesty is the whole point.

The trip where nothing was caught is the one every operator wants to skip, and skipping it is the prohibited move rather than the tactful one.

It is also the trip most likely to produce the review that persuades somebody, because a client who was looked after on a hard day says so in a way nobody can fake.

The message changes only in its first sentence, which acknowledges the day without excusing it.

Yesterday was as tough as it gets out there, and you stuck at it longer than most people would have.

Then the same ask, the same disclosure that it is public, the same single link, and the same close.

What must not appear is an explanation of the conditions, because an explanation reads as a request for a particular kind of review.

Say less about the fishing and more about the person, and send it at the same hour as every other one.

The rest of that day, from the water to the ramp, is a separate discipline entirely.

Who should the message come from?

A person, with a name, and a way to reply.

The federal request ends with a named official, a direct telephone number and an email address, which is the opposite of how most automated messages end.

That closing element does something specific: it establishes that a human is at the other end and that replying is possible.

A review request sent from a no-reply address undoes half its own work, because it announces that the sender does not want a conversation.

Send from the address you actually read, sign it with the name on the boat, and accept that some people will reply instead of reviewing.

Those replies are worth more than the reviews in the short run, since they are where you learn what went wrong before anybody publishes it.

A client who tells you privately that the meeting point was confusing has handed you a fix rather than a rating.

Answer every one of those within the day, because the reply is the relationship and the review is only its record.

What do operators not expect here?

That disclosure helps rather than deters.

Telling somebody their words will be public feels like a reason for them to decline, and it reads as respect rather than warning.

The federal request goes further still by offering anonymity outright, and the offer does not appear to suppress participation so much as define it.

The second surprise is how much of the message is doing structural work rather than persuasive work, since the specific detail exists to prove the message is not automated.

The third is that the strongest sentence in any of these scripts is the one saying an honest account is the useful kind, because it is the only sentence that makes the request safe to accept.

The fourth is that shorter consistently beats warmer, which most people only believe after sending both.

And the fifth is that nobody has published a response rate for any of this, so anyone quoting one is quoting themselves.

What to do with the replies that arrive is covered in the testimonials piece.

Does the wording matter at all?

At the margin, and only after coverage is solved.

No published figure exists comparing review-request wordings for guiding operations in any market, and none is asserted anywhere here.

The federal example establishes an upper bound on what design alone can do, which is that a professionally structured request to a whole fishery produced seven responses in five days.

What wording can do is avoid the specific failures above, each of which gives a willing person a reason to stop.

What it cannot do is manufacture willingness in somebody who was never going to write one.

So the order of work is coverage first, timing second, wording third, and most operators do it in reverse.

Anybody selling you a script as the fix has the order backwards too.

The reply you write when a difficult one arrives matters far more, and that is in the negative reviews piece.

How would you check yours?

Read it aloud, then send it to somebody who does not fish.

Read the message aloud and stop at any sentence you would not say to the client's face, because those are the sentences that read as marketing.

Send it to a friend outside the trade and ask them what they think they are being asked to do, which surfaces ambiguity you cannot see.

Tap your own link from a phone not signed into your business account and count the steps to the box.

Check the message against the six prohibitions above, item by item, rather than by impression.

Then leave it alone for a season, because changing it every month makes any comparison impossible.

Only the send list is worth revisiting, and it should be growing.

The equivalent scripts for reaching people who fished with you years ago are in the past-client scripts piece.

The scripts, in order

One detail, one ask, one disclosure, one link, no conditions.

Open with something only somebody who was there could say, taken from the week's list rather than from memory.

Ask once, in a single sentence, and say that an honest account is the useful kind.

Tell them plainly that whatever they write is public and permanent under your business name.

Give one link that lands directly on the box, tested from a signed-out device.

Close without pressure, without a star reference, without an offer and without a second ask.

Send it to everybody who fished that week, on the same day, in the same words.

Then leave the wording alone and grow the list, because the list is what moves the number.

The field where you can answer the questions those clients arrive with is covered in the profile questions piece.