Event triggers let Revuloop send a survey automatically the moment something happens in your support or CRM tools: for example, the instant a Zendesk ticket is solved or an Intercom conversation is closed. No exports and no manual sends: the customer gets the right survey at exactly the right moment.
How It Works
- Connect a supported integration (Zendesk or Intercom).
- Create a trigger: "When this event happens, send this survey via this channel."
- When the event fires in the connected tool, Revuloop matches it, resolves the recipient, and sends the survey instantly, or after a delay you choose.
Every send is de-duplicated, so the same ticket or conversation can never survey a customer twice.
Supported Event Sources
| Source | Event | Typical use |
|---|---|---|
| Zendesk | Ticket solved | Post-resolution CSAT |
| Intercom | Conversation closed | Post-chat satisfaction |
More sources are being added. If you need a specific tool, contact support@revuloop.com.
Delivery Channels
| Channel | What happens |
|---|---|
| The survey link is emailed to the customer | |
| SMS | The link is texted (requires SMS messaging setup) |
| The link is sent over WhatsApp (requires WhatsApp setup) | |
| Link only | Revuloop resolves a link and forwards it to your webhook to route yourself |
Creating a Trigger
- Go to Settings → Integrations and open a connected integration (e.g. Zendesk).
- Find the Survey triggers section.
- Set the event under When this happens, choose the survey under Send this survey, and pick the channel under Via.
- Optionally adjust the recipient field path (pre-filled for most providers).
- Click Add trigger. It goes live immediately.
You can add multiple triggers per integration, pause any trigger with the power toggle, or remove it with the trash icon.
Advanced Options
Expand Advanced on the trigger form to fine-tune behavior.
Conditions
Only send when the event matches rules you set: for example, only survey high-priority tickets, or skip anything tagged spam. Add one or more conditions; all of them must match.
Delay
Wait a set time after the event before sending: for example, send a CSAT survey 60 minutes after a ticket is solved so the resolution has time to settle.
Cooldown
Limit how often the same person is surveyed, for example at most once per week per recipient.
Good to Know
- Security: every inbound event is verified with a cryptographic signature before it can fire a trigger.
- De-duplication: a single ticket or conversation fires a trigger at most once.
- Recipient required: email triggers need an email on the event; SMS and WhatsApp need a phone number. If it's missing, the send is skipped and logged.