> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/ai-app-builder/practical-guides/build-a-support-dashboard.md).

# Build a support dashboard

Create a workspace for finding, reviewing, and assigning support tickets.

### Prepare data

Use a Tickets table with Name, Status, Priority, Assigned to, and Customer fields. Connect Customers for customer details. Confirm how Customer links to its record. Include two Open test tickets and one Closed test ticket.

For starter ticket records, download the sample CSV. Add a Customer relationship and sample customer records separately for the customer-detail steps.

### Build the list and details

1. Select the source containing the tables.
2. Send this prompt, replacing field names as needed:

> Build a support dashboard using Tickets and Customers. Show Name, Status, Priority, and Assigned to in a Tickets list. Add search by Name and a Status filter. Open a detail view when I select a ticket and show its linked customer. Start read-only.

3. Confirm all test records appear.
4. Filter to Open: exactly the two Open test tickets should remain.
5. Open a ticket and compare its customer details with the linked source record.

{% @arcade/embed flowId="QdtEXlmnSHv5VUOY4KO4" url="<https://app.arcade.software/share/QdtEXlmnSHv5VUOY4KO4>" %}

### Add assignment

> Add an assignment action to the ticket detail view. Update only Assigned to on the selected ticket. Require a value and display the saved result.

Test the action on one ticket. Verify the source record changed and the other tickets did not. Configure and test the permissions for staff who may assign tickets.

{% @arcade/embed flowId="txYVRgIhEenGIqoFe7oA" url="<https://app.arcade.software/share/txYVRgIhEenGIqoFe7oA>" %}

### Refine and release

Use Edit in Preview for a label change and Theme for appearance. Check mobile navigation and form layout.

{% @arcade/embed flowId="YN8yPPZnPeZHpkMMRnuC" url="<https://app.arcade.software/share/YN8yPPZnPeZHpkMMRnuC>" %}

Finish with data and access testing and publishing checks. Before publishing, you can share a preview link for feedback.

If a source update fails, capture its inputs and error in Console.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/ai-app-builder/practical-guides/build-a-support-dashboard.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.