n8n workflow · 13 nodes · sentiment, drafted reply, forced escalation
MSP Review & Reputation Engine
Routine reviews get fast drafts. The ones that could hurt someone go to a person first.
status running · private n8nrole designed + built end to end
Four real reviews fired at the live webhook, including a five star review that still escalates because it names a technician.
What it solves
Review replies are public and permanent. A reply that admits fault, promises a refund, or names an employee in a dispute creates legal exposure a marketing team cannot take back, and sentiment scores do not catch those cases. The guard here is a code check with a one-way rule: the model can raise an escalation, never lower one.
Who it serves
MSPs and multi-location businesses answering reviews on Google and G2.
Who it is for
The marketing owner who wants drafting handled without inheriting the risk.
How it works
- A review arrivesA webhook catches it and normalizes platform, rating, branch, and text.
- Claude reads and draftsSentiment, themes, and a reply in the brand voice, held to a word cap and a banned-phrase list.
- The guard decides, in codeRating at or below three, any mention of legal action, money, or a breach, or any review naming a staff member forces escalation. The model can raise an escalation, never lower one.
- The reply is checked tooA draft that admits fault, promises money, guarantees anything, or invents a contact detail is sent back for revision rather than queued.
- A person approvesEvery surviving reply waits on a signed approval link. The workflow has no ability to post.
- Everything logsRating, sentiment, whether it escalated and why, the action taken, and who approved it land in a ledger.
Built with
n8n Claude (Sonnet) deterministic guard data-table ledger built via MCP