Skip to content
Hazelsong

Read and decide

Take out the phone number. Change nothing else.

A testimonial arrives with a client's phone number in it, or an opposing party's name, or a case number. You can take that span out and publish the rest — and the reader is told that something was removed.

Start collectingSee the plans

PlanEvery plan.

How it works

Removing a detail, step by step

  1. It proposes the spans; you approve them

    The detail is found and offered with a reason. Nothing disappears from your page because a model thought it should.

  2. What is left is what they wrote

    The removed span becomes [removed]. Every other character is the character your customer typed.

  3. The reader knows

    A published testimonial with a removal says so under it. A quotation with a silent hole in it is a different sentence from the one somebody wrote.

Your dashboard · Pending
Customer name

Every word arrives as they wrote it — even the 555-0142 they meant to leave out.

Read this before publishing"555-0142" A phone number. Take it out before this goes on your site.Read automatically when it arrived. It points; you decide.
A version with parts removed is readyEvery word arrives as they wrote it — even the [removed] they meant to leave out.
ApproveRejectPublish this version instead
Drawn from the product's own markup and labels, with example words — not a real customer.

Safe by design

The rule that makes it safe to have

Clear boundaries

What it will not do

Every capability page ends with this list. It is the part that says what you are actually buying.

  • It will not fix a typo, improve grammar, or shorten a sentence.
  • It will not remove a span without telling your reader that it removed one.
  • There is no API field, no dashboard control and no admin path that can change a testimonial's text.

Where it lives in the code: lib/redact.ts

Questions

Asked about this

From Help, where every answer is written from the product as it runs.

Can I fix a typo in a testimonial?

No. There is no route in this product — no dashboard control, no API field, no administrator, no support request — that can change a testimonial's text. That is the rule the whole product is built around, and it is checked in code rather than promised in a policy.

Then what do I do about a phone number somebody left in it?

Remove that span. The span becomes [removed], every other character stays exactly as written, and the reader is told something was taken out. If the proposal differs from the original by a single word anywhere else, the whole proposal is discarded rather than applied.

Can I shorten a long testimonial for a widget?

Not by storing a shorter version: nothing here can keep a cut-down copy as though it were what somebody wrote. What a layout may do is show less of it — the compact, marquee, toast and sidebar layouts stop a long testimonial at six lines, and there is no control that opens the rest. Every other layout shows the whole of it, so the choice to make here is the layout.

A customer asked me to take theirs down. What happens?

Delete it, and it is out of every widget, wall, image and API answer at once — a real delete, the record and the files both. There is no archive here: a testimonial is pending, approved or rejected, and once it is approved the dashboard's own way to take it off your pages is Delete. Reject is the button while it is still pending.

More on the testimonials themselves

Next to this

Works together with

Read for riskEvery one, before it can be publicPermissionRecorded in writing, and enforced hereTranslationPublished in another language, marked as translated

This is running now

Open a project and use it. Nothing on this page is a roadmap.

Start collectingEverything it does