Four real reviews. Two got a drafted reply, two never reached one.

Fired at the live webhook. What follows is what the workflow actually returned, including the reasons it refused to draft.

rv-1001 · Google · Boca Raton
Dana W. ★★★★★

We moved 40 workstations over a single weekend and opened Monday like nothing happened. The cutover plan was clear and the help desk picked up fast when two people could not print.

positivecutover planning, help desk responsivenessreply passed the checks
drafted reply, parked for a manager

Thank you, Dana! Moving 40 workstations in a single weekend and opening Monday without a hitch is exactly the outcome we aim for. We're glad the cutover plan came together smoothly and that the help desk was quick to jump in when those printing issues came up. We'll pass this along to the Boca Raton team. If anything else comes up, reach us at support@mindcore.example or (555) 010-4477. Thanks for sharing your experience!

approved by a human, ledger row 1
rv-1002 · G2 · Newark
Priya R. ★★★★

Solid day to day support and the monthly reporting is genuinely useful. Onboarding took longer than quoted, and we chased a few times before the last two laptops were imaged.

mixedreply drafted, waiting on a manager
rv-1003 · Google · Boca Raton
Mark T. ★★

Ticket sat for two days while our shared drive was down. We are speaking to a lawyer about the invoice for that month and we want a refund.

escalated to a humanno reply drafted
reason: rating 2 at or below 3; legal threat; money claim; model flagged it
rv-1004 · Google · Newark
Elena S. ★★★★★

Our tech Marcus talked my whole front desk through the new phones without once making anyone feel stupid. Rare and appreciated.

escalated to a humanno reply drafted
reason: names a staff member; model flagged it

A glowing five star review, and it still stops here. Praise that names an individual is a decision about a person, so it goes to someone who knows whether Marcus wants his name in a public reply. Sentiment never lowers a rule.

The model reads the review and drafts. The code decides what happens next, and re-checks every escalation rule after the model has spoken so a confident answer cannot talk its way past one. Nothing in this workflow can post. A reply only ever waits, and the ledger records who approved it.