Request reviews after support
When a ticket is solved in Help Scout, send a review request from Senja.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Help Scout Explore Help Scout →
TriggersFires when a new support ticket or chat conversation starts in Help Scout.
Fires when a ticket's status changes in Help Scout.
Fires when a ticket in Help Scout is assigned to an agent.
Fires when a ticket in Help Scout breaches its response SLA.
Creates a new ticket in Help Scout.
Updates a ticket's status in Help Scout.
Assigns a ticket in Help Scout to an agent.
Posts a reply or internal note on a ticket or conversation in Help Scout.
Senja Explore Senja →
TriggersFires when a customer leaves a new review in Senja.
Fires when a review is edited or answered in Senja.
Fires when a customer answers a feedback survey in Senja.
Invites a customer to leave a review with Senja.
Adds or updates a customer contact in Senja.
Posts a public reply to a review in Senja.
More Help Scout + Senja workflows
See all Help Scout + Senja integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Request reviews after support” between Help Scout and Senja?
Yes — describe it in the box above and Knit's Integrations Agent researches Help Scout and Senja's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Can a bad review open a ticket?
Yes. When a low-rated review arrives in Senja, Help Scout can create a ticket.
Can solved tickets ask for a review?
When a ticket is solved in Help Scout, Senja can send a review request.