Build a customer-service agent that answers policy questions and creates a Zendesk ticket when a request needs your support team. This walkthrough uses the fictional Northstar Supply store: the agent collects the issue, confirms the customer’s details and sends one ticket to Zendesk. Ticket creation is asynchronous support, not a live chat handoff.

Before you begin

  • Access to create or edit a Voiceflow project and connect integrations.
  • A Zendesk account authorized to create tickets, plus its subdomain URL, such as https://your-company.zendesk.com.
  • A test requester whose email you control. The .example addresses in the screenshots are fictional and cannot receive mail.
  • A staging website if you want to try the published chat widget. Keep the first tests away from customer traffic.
Running Create ticket changes the connected Zendesk account. A draft conversation uses the published connection unless you add a separate draft connection. Choose your test account before running the tool; another run can create another ticket.

Configure the support workflow

1

Create the support agent

From Projects, click New project, name it Northstar Ticket Support, choose Chat, then Start from scratch. You can also use an existing customer-service agent. Keep Main selected while preparing this example.

Open Knowledge base → Add data source → Plain text and import your approved shipping and returns policy. For practice, use these fictional rules:

  • Standard delivery takes 3–5 business days after dispatch, within Canada.
  • Unused items in their original packaging can be returned within 30 days of delivery.
  • Order status, replacement decisions and refund processing require the support team.

Wait for processing to finish. In Agent, enable Knowledge base under System tools. This lets the agent answer the routine questions before offering a ticket for work it cannot complete.

2

Connect the Zendesk account

Open Integrations in the project sidebar and choose Zendesk → Connect. Enter your Subdomain URL, click Connect and complete the Zendesk authorization.

Inspect the connection details. Published connection is used by published conversations. Add draft connection lets you connect a sandbox for draft tests; without it, draft conversations use the published account. Confirm both destinations before testing or launching. See Zendesk connection setup.

3

Attach Create ticket to the agent

Return to Agent. Click + beside Global tools, choose Zendesk and select Create ticket. The tool must appear in the agent’s Global tools list; adding a tool to the project alone does not attach it to the agent.

Open the attached tool. In Trigger, describe when it should run:

Create ticket trigger
markdown
Create a support ticket after the customer confirms their name, email and request. Do not call for a policy question that the Knowledge base can answer.

The required inputs are subject, description, requesterName, requesterEmail and comment. Keep customer-specific defaults empty so each conversation supplies its own details. Leave the optional priority and custom fields off for this example. The Zendesk reference lists the connector’s other operations.

Configure the attached ticket tool, including its trigger and customer inputs. Photo:
4

Define collection and confirmation

In Global prompt, set the agent’s role to Northstar Supply customer support. Tell it to answer only from approved knowledge and never invent order status, issue refunds or promise a response time.

In Instructions, enter:

Ticket workflow instructions
markdown
Answer shipping and returns questions from the Knowledge base.

For an unresolved request, ask for the customer’s name, email and issue. Ask for an order number only when relevant. Summarize the request and ask whether to create a support ticket.

After confirmation, call Create ticket once. Use the confirmed name and email as requesterName and requesterEmail. Write a short subject and a factual description and comment. Leave optional priority and custom fields unset.

If the tool succeeds, share the returned ticket ID. If it fails, say the ticket was not confirmed and offer your support email. Never make up a reference or immediately repeat a failed creation.

Replace your support email with your real fallback contact. These instructions govern when the agent attempts the action; the checks below verify its behavior with your configuration.

Keep the collection, confirmation and failure instructions together. Photo:

Test ticket creation

1

Confirm one complete request

Click Run. Describe a damaged order and give a test name and email you control. For example: “My mug in order NS-1042 arrived cracked. I’m Maya Chen. Can support help replace it?”

Supply the requested contact details. The agent should summarize the issue and ask for confirmation before creating a ticket. Confirm once, then inspect the tool result.

Check the customer’s details and consent before the ticket tool runs. Photo:
2

Verify the record in Zendesk

Open the connected Zendesk account and find the new ticket. Compare its requester, email, subject and comment with the confirmed request. Check that the reference shared in chat identifies this ticket and that the test created one record.

If no ticket appears, inspect the tool error and selected connection before retrying. If the result is uncertain, check Zendesk first: repeating the action can create a duplicate.

3

Check cancellation and routine questions

Start fresh Run conversations for these checks:

  • Cancel: provide an issue, then decline confirmation. No ticket should be created.
  • Missing email: ask for help without contact details. The agent should collect the email before calling Create ticket.
  • Policy question: ask “How long does standard delivery take?” The agent should answer from the policy without creating a ticket.

Check Zendesk as well as the chat response. A reassuring reply alone does not prove whether an external action ran.

Launch and verify customer traffic

Review the Published connection again, replacing a sandbox connection when you are ready to send real requests to your support team. Confirm your support email and policies are correct, then Publish the tested Main draft.

For a new website agent, open Widget → Installation, copy the project’s generated snippet and add it before your website’s closing </body> tag. Follow any Turn off private mode → Confirm & copy code prompt only when the agent is ready for public conversations. Keep the generated client authentication intact; never insert a private API key. Widget installation covers site settings.

In a fresh website conversation, submit one clearly labeled test request and verify the ticket in the published Zendesk account. Open Transcripts to review the corresponding conversation. Clean up test records using your Zendesk process.

For a person to take over the conversation immediately, configure Human agent hand-off separately. Creating a support ticket does not connect a live representative.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.