# Test it like a member

Before you tell your community "we have a ticket system now," walk through it yourself as a non-staff user. It takes about five minutes and catches problems that are hard to find later.

## The checklist

Use an alt account, a friend, or join your server with no admin role (remove yourself from your admin roles for the test, then add yourself back at the end). The point is to use the panel as a regular member, not as an admin who bypasses every check.

{% hint style="info" %}
**Quickest way to test as a member:** ask a friend to be online for 5 minutes, or temporarily remove your admin role, then add it back after.
{% endhint %}

### 1. Can a member see the panel channel?

Open the channel where your panel lives. Confirm a non-staff member can see the channel and the panel message.

If they can't, your channel permissions are too restrictive. Edit the channel and ensure `@everyone` (or the role you intend) has **View Channel**.

### 2. Does clicking the button do something?

Click the panel button as a member. You should see one of two things within a second:

* A new ticket channel appears in the Tickets category, *or*
* A short form pops up asking questions, *and then* a new channel appears after submitting.

Neither happened? See [Panel buttons do nothing or show "interaction failed"](/docs/troubleshooting/interaction-failed.md).

### 3. Can the member see their own ticket?

In the new ticket channel, confirm the member can:

* See the channel (it should appear in their sidebar).
* Send messages.
* See the welcome embed Ticket King posted.

If the member can't see the channel they just opened, Ticket King's permissions are too restrictive. Most commonly: the Ticket King role is below the role granting access. Drag it up in **Server Settings → Roles**.

### 4. Can your support team see the ticket?

Switch back to your staff account (or have a teammate check). Confirm your support team can see and post in the new ticket.

Can't see it? You haven't [added a support role](/docs/permissions-and-your-support-team/support-roles.md), or the support role is above Ticket King in the role list.

### 5. Does the close flow work?

As your staff account, run `/close` in the ticket channel. The bot should:

* Ask for a reason first if you have turned on "Close Requires Reason".
* Post a log message in your closed-tickets log channel.
* Either archive the channel or delete it, based on your settings.

→ [Closing a ticket](/docs/tickets/closing-a-ticket.md)

### 6. Did the log channel receive the entry?

Open your closed-tickets log channel. There should be an embed for the ticket you just closed, including:

* Ticket number.
* Who opened it.
* Who closed it.
* A link to the transcript.

No log entry? Either you haven't set a log channel ([Logging → Log channels](/docs/logging/three-log-channels.md)), or Ticket King can't post in it (check channel permissions).

### 7. Did the transcript work?

Click the transcript link in the close log. You should see a clean view of every message in the ticket.

Transcript missing or empty? See [A transcript is missing or empty](/docs/troubleshooting/transcript-missing.md).

## You passed. Now announce it.

Once all seven boxes are checked, your ticket system is real. Tell your community:

* Pin a message in `#general` linking to the `#tickets` channel.
* Add a short blurb in your welcome message for new members.
* Brief your support team on how to claim, respond, and close.

## Next: where to go from here

{% content-ref url="/pages/chwnamUwR0ML1b28tT03" %}
[Where to go next](/docs/getting-started/where-to-go-next.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ticketking.xyz/docs/getting-started/test-it-like-a-member.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.