Add respondents to follow-up surveys when tickets close
When a ticket status is updated to resolved in Freshdesk, add the customer as a respondent in Collect.chat to send a satisfaction survey.
See all Freshdesk + Collect.chat integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How 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.
Freshdesk Explore Freshdesk →
TriggersFires when a new support ticket is created in Freshdesk.
Fires when a ticket's status changes in Freshdesk.
Fires when a ticket in Freshdesk is assigned to an agent.
Fires when a ticket in Freshdesk breaches its response SLA.
Creates a new ticket in Freshdesk.
Updates a ticket's status in Freshdesk.
Assigns a ticket in Freshdesk to an agent.
Posts an internal or public comment on a ticket in Freshdesk.
Collect.chat Explore Collect.chat →
TriggersFires when a form is submitted in Collect.chat.
Fires when a respondent finishes a survey in Collect.chat.
Fires when an existing response is edited in Collect.chat.
Creates or updates a form or survey in Collect.chat.
Looks up a specific form response in Collect.chat.
Adds a respondent or contact to a form in Collect.chat.
More Freshdesk + Collect.chat workflows
Generate support tickets from form responses
When a customer submits a web form in Collect.chat, automatically create a detailed support ticket in Freshdesk for team review.
See details
Attach survey updates as comments on open tickets
When a customer updates an existing survey response in Collect.chat, automatically post the new feedback as a comment on their ticket in Freshdesk.
See details
See all Freshdesk + Collect.chat integrations → · Browse the full workflow library →
Common questions
Can Knit build “Add respondents to follow-up surveys when tickets close” between Freshdesk and Collect.chat?
Yes — describe it in the box above and Knit's Integrations Agent researches Freshdesk and Collect.chat'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.
How are survey responses transferred into support tickets?
Submitting a completed survey in Collect.chat automatically creates a new ticket in Freshdesk containing all the respondent's answers.
Can ticket updates prompt custom survey distributions?
When a ticket status changes in Freshdesk, you can automatically add the customer as a respondent in Collect.chat to collect feedback.