Turn an unresolved customer issue into a support request your team can act on. This walkthrough creates a Zendesk ticket for a damaged order, assigns it to an approved support agent and reads it back. Creating the ticket does not issue a replacement or start a live conversation.
Before you begin
- A test project connected to the intended help desk. For the worked example, complete Zendesk ticket-tool authorization. Code users must complete its browser OAuth too.
- A test customer, their confirmed request details and an approved destination in the help desk. The example uses Maya Chen, order NS-1042 and
support@northstar.example; replace them with your test account’s records. - A way to retain the returned ticket ID with the verified customer and request. Use an existing saved request for follow-ups instead of creating another ticket.
Studio
Open the test project in Agent studio. Use a Playbook or Workflow for this support-request task.
Code
Use a Voiceflow bearer credential with access to the test project and Environment. Keep it on your backend or development machine. Set:
Install the current Voiceflow CLI if you choose CLI. Both examples below use VF_TOKEN. Standalone tool execution uses the Environment’s Draft; it does not attach a tool to an agent or publish it.
Create and route the request
Confirm what the customer needs
Collect the issue, requested outcome, requester name and contact address. Summarize them and ask for confirmation before creating the request. The example records a cracked mug and a request for replacement; it does not promise eligibility, stock or a delivery date.
Studio
Add Zendesk → Create ticket to the relevant Playbook or Global tools. Its Trigger should describe this unresolved request and require confirmation before the write. Supply subject, description, requesterName, requesterEmail and comment; put the customer issue and requested outcome in the initial comment.
Code
Keep the confirmed values on your backend. Read the action schema for your test Environment before executing zendesk_create_ticket. The five fields below are required; account-specific custom fields and priority are optional.
Create one request and retain its ID
Studio
Run the agent, describe the damaged order and confirm the summarized request. Inspect the Create ticket tool result. With Capture response, select the returned ticket ID from the actual result; have your application retain it with this customer’s case.
Check the new ticket in Zendesk. The connector creates status new.
Code
Require success: true, error: null and truncated: false before using output.data. An HTTP 200 alone does not establish that the provider action succeeded.
Retain output.data.id. The following steps use the illustrative ticket ID 8422; replace it with the ID returned by your call. Inspect the actual ticket and initial comment in Zendesk.
Do not automatically repeat creation after a timeout or uncertain response. First check whether the ticket was created, or the customer can receive duplicate requests.
Route the same request and read it back
Studio
Add Zendesk → Update ticket. Set ticketID to the saved ID, assignee to a permitted support-agent email and priority and status if needed. The worked example uses normal priority and pending status. Supply only the fields you intend to change.
Run the update once, then read the same ticket with Find ticket and confirm its assignee and priority in Zendesk.
Code
Require success: true, error: null and truncated: false before using output.data. An HTTP 200 alone does not establish that the provider action succeeded.
The first call changes the assignee, priority and status; the second reads the same ticket. Confirm the returned record and the actual destination in Zendesk before saying it has been assigned. A saved assignment is not proof that a person has responded.
Verify the customer outcome
- Exactly one request exists with the confirmed customer, issue and initial message.
- The saved ticket ID belongs to this customer’s request and is available for a later status check.
- The intended support agent receives the ticket. Give the customer the returned reference without promising a response time you have not established.
Studio
Publish the reviewed Environment and repeat the confirmation-first conversation in a fresh customer session.
Code
Code examples execute the actions once. To have the AI perform them, add and attach the tools, bind their inputs and compile the Draft, then run a confirmation-first conversation. For a published experience, publish that reviewed Environment and repeat in a fresh customer session.
For other providers, use Gorgias ticket creation, Chatwoot conversation creation or Freshchat conversations and routing. Use their request types and destination IDs; they are not Zendesk ticket fields.
The request exists but the destination is wrong
Check the returned ID and account-specific routing field.
Read the same saved request before changing it. Confirm the connected account and that the target assignee or group exists and is permitted there. Fix only the destination field, then read it back. Creating another request does not repair routing. For immediate two-way support, use Human agent hand-off.