> ## Documentation Index
> Fetch the complete documentation index at: https://www.voiceflow.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Check support request status

> Answer a customer's follow-up using the request your application already saved. This walkthrough reads a Zendesk ticket and returns its permitted status information.

Answer a customer's follow-up using the request your application already saved. This walkthrough reads a Zendesk ticket and returns its permitted status information. It does not create a new ticket or change the existing one.

## Before you begin

- The [Zendesk connection](/docs/guides/integrations/zendesk/overview#connecting-zendesk), or the corresponding read operation for your help desk.
- A customer authenticated by your application and a stored mapping between that customer and the request. A customer-supplied ticket number or email is not an access check.
- A test ticket you can inspect. The example uses **8422**, the illustrative request created in [Create and route support requests](/docs/guides/integrations/help-desks/create-and-route-support-requests). Use your actual returned ID.

#### Studio

Open the test project in [Agent studio](https://creator.voiceflow.com). Have your application populate the permitted ticket ID before the lookup. For a controlled builder test, use a dedicated test record; do not treat a fixed sample ID as production authorization.

#### Developer

Use a [Voiceflow bearer credential](/docs/api-reference/authentication) with access to the test project and Environment. Keep it on your backend or development machine. Set:

```sh
export VF_TOKEN='YOUR_VOICEFLOW_BEARER_TOKEN'
export PROJECT_ID='YOUR_PROJECT_ID'
export ENVIRONMENT='main'
```

Install the current [Voiceflow CLI](/docs/cli/install) 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.

## Read the customer's request

### 1. Authorize the requested case

Look up the request in your backend's authenticated customer-to-case mapping. Continue only if the signed-in customer may access it. If the ID is missing or the association fails, use your support fallback without querying another customer's ticket.

[Recognize returning customers](/docs/guides/integrations/help-desks/recognize-returning-customers) explains the identity boundary. A tool Trigger can describe the policy; it cannot enforce access by itself.

### 2. Read the existing ticket

#### Studio

Add **Zendesk → Find ticket** to the relevant Playbook or **Global tools**. Set **ticketID** to the verified case ID. Give its Trigger a specific purpose: read the current status of a request the customer is permitted to access.

Native Zendesk Find ticket editor and its ticketID input — Use the authorized ticket ID to read the existing request.

Run a follow-up question and inspect the tool result. Use **Capture response** if subsequent steps need the ticket ID or status.

#### Developer

#### API

```sh
curl --fail-with-body --silent --show-error \
  --request POST "https://realtime-api.voiceflow.com/v1/stable/integration/zendesk/execute?projectID=$PROJECT_ID&environmentAlias=$ENVIRONMENT" \
  --header "Authorization: Bearer $VF_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{
  "toolName": "zendesk_find_ticket",
  "inputs": {
    "ticketID": 8422
  }
}'
```

#### CLI

```sh
vf --output-format json integration execute --integration zendesk \
  --project-id "$PROJECT_ID" --environment-alias "$ENVIRONMENT" \
  --tool-name zendesk_find_ticket \
  --inputs '{
  "ticketID": 8422
}'
```

Require `success: true`, `error: null` and `truncated: false` before using `output.data`. An HTTP 200 alone does not establish that the provider action succeeded.

Confirm `output.data.id` matches the authorized ticket. Check the requester against your permitted customer association before returning its status. The example ID is not a valid substitute for that access check.

### 3. Return only permitted information

Explain the returned status in the context of the request. For example, an illustrative result with `status: "open"` permits “Your request is still open.” It does not establish a response time or that a replacement has shipped.

Do not send the entire provider result to the customer. Internal notes and private fields stay private. **Find latest comment** can return a private note; inspect visibility before using any comment as a customer update.

## Verify the status answer

- Compare the displayed reference and status with the same ticket in the help desk.
- Test an authorized customer's request, an unknown ID and a request belonging to a different customer. The last two must not disclose case details.
- Confirm that the follow-up caused no ticket creation or update.

For other providers, use their stored conversation or request ID: [Intercom conversation reads](/docs/guides/integrations/intercom/overview#reading-conversations), [Gorgias ticket reads](/docs/guides/integrations/gorgias/overview#managing-tickets), [Chatwoot conversations](/docs/guides/integrations/chatwoot/overview#managing-conversations) or [Freshchat conversations](/docs/guides/integrations/freshchat/overview#managing-conversations). Verify the provider-specific customer association before the read.

### The lookup cannot confirm a status

Separate a missing case from an unavailable connection.

Check the connected account, permitted request ID and returned action error. A missing record or failed tool call is not evidence that the issue is resolved. Tell the customer you could not confirm the status and offer your support path. Do not search through unrelated customer tickets or create a replacement request automatically.
