Asking for a review at the right moment
The moment is the whole feature. A won deal fires the request the day the job went well, once per customer, by SMS or email.
Want to see it first? Book a demo
- Triggered on won
- Once per customer
- Every customer asked the same way
The short answer
- In SalesCrew, a deal moving to won fires a review request by SMS or email, with the link to the review platform you care about.
- The once-per-customer rule is enforced by the product, and a suppressed contact is never messaged.
- The request goes to everyone the rule matches. Filtering happy customers into a review link and unhappy ones into a private form breaks the rules of several review platforms, so SalesCrew asks every customer the same way.
Trigger to logged
One customer's path from a won deal to a review request.
- 1
Trigger: a deal moves to won
Every stage change is written to the audit log with its actor. The move to won is the hook the request hangs on.
- 2
The rule decides who qualifies
Once per customer, a minimum time since the last ask, and never to a suppressed contact.
- 3
The request sends
By SMS through Twilio with consent and STOP handling, or by email from your mailbox pool inside your business-hours window.
- 4
Your team keeps an eye on the tone
A review ask is a customer-facing message from your business. Any agent-drafted version waits in the approval queue like every other external send.
- 5
A reply is a conversation, not a metric
If someone answers the request with a complaint, the reply lands in the shared inbox and pauses the cadence. That's the outcome worth having.
- 6
What gets logged
The stage change, the send and any reply, all on the contact timeline.
What gets configured
What you set for each object in your SalesCrew instance.
| Object | What you set |
|---|---|
| Won stage | Which stage counts as the trigger |
| Automatic request on won | The wording, the link and the delay after won |
| Channel for the ask | SMS through Twilio with consent and STOP handling, or email |
| Once-per-customer rule | The minimum gap between asks |
| Suppression | Contacts who should never be messaged |
Where it stops and a human starts
The request fires on its own, and you can still see every one of them. Each stage change and each send is in the audit log, so you know who was asked and when.
Your team owns the wording. An agent may draft it and the draft waits in the approval queue, because a review request is an external send and every external send is review by default.
The review itself happens on the platform your customer picks. Rules about incentives and about filtering feedback belong to that platform, and you should read the ones that apply to yours. This page is not legal advice.
Questions
- How does SalesCrew send review requests?
- A deal moving to won fires the request by SMS or email with the link to your review page. The once-per-customer rule and your suppression list decide who gets it, so nobody is asked twice.
- Does every customer get the same request?
- Yes. The request goes to everyone the rule matches. Sending only happy customers to a public review link breaks the rules of several major review platforms, so SalesCrew treats every customer the same.
- When is the right moment to ask?
- Close to the moment the work went well, and once. A recurring ask trains people to ignore you, which is why SalesCrew enforces the once-per-customer rule rather than leaving it to memory.