Write the ticket
Set the subject, the comment and the priority, add tags with the survey's own tag, and fill the custom fields every ticket from this workflow should carry.
Open a Zendesk ticket for each survey answer that needs a reply, with the answer as an internal note, the customer as the requester and the tags your triggers already use.
A complaint in a survey deserves the same reply as one in an email. With the Zendesk integration, an answer that needs someone becomes a ticket, with the customer as the requester, so an agent can reply from Zendesk.
The answer goes in as an internal note, which only agents see, and Zendesk doesn't email it to the customer. Tags such as usertick and the survey's own tag let your views and triggers route the ticket.
A workflow decides which answers open tickets: every answer to a survey, only the urgent ones, or only the complaints the AI found, and the ticket links back to the answer in Usertick.
A workflow step writes the ticket, and Zendesk takes it from there.
Set the subject, the comment and the priority, add tags with the survey's own tag, and fill the custom fields every ticket from this workflow should carry.
The ticket names the customer as the requester, keeps the answer in an internal note and links to the answer in Usertick, so the agent has the whole story before replying.
Each ticket the step creates carries these.
Connecting creates nothing by itself. A workflow decides which answers open tickets.
In Usertick, open Settings, then Integrations, select Zendesk, enter your subdomain and sign in. Usertick asks to read and create tickets and users.
Set the subject, the comment, the priority, the tags and any custom fields.
A test run on a real answer creates a ticket marked [Test]. On a sample answer, it checks the step and creates nothing.
Zendesk comes with every plan, along with the workflows that create the tickets. Free runs 1 workflow per survey.
Not for the comment. Usertick adds it as an internal note, which only agents see, and Zendesk doesn't email it to the requester.
No. Each ticket carries an external ID, and a retry finds the ticket it already created instead of opening another.
No. The ticket links to the answer, and the answer's status in Usertick stays with your team.
No. Zendesk connects with a sign-in, and Usertick refreshes its access by itself.
The tickets stay in Zendesk, and Usertick revokes its access. Workflow steps that used the connection stop sending until another one is assigned.
Start free, see what your customers mean, and get each answer to the person who can act on it.