# Discord tickets & embeds

> Post custom embeds in your Discord servers, let customers open a ticket from a button on your server, and how customers link their Discord account.

Source: https://joely.io/documentation/integrations/discord-tickets
Last updated: 2026-11-10

## Embeds

| What you need | |
|---|---|
| Permission | Send portal embed to Discord channels |
| Prerequisite | A [connected Discord server](https://joely.io/documentation/integrations/discord.md) |

Compose an embed with a live preview, then send it to a channel of any of your [servers](https://joely.io/documentation/integrations/discord.md#several-discord-servers). Pick the server first: its channels and custom emojis follow.

| Button action | The button… |
|---|---|
| **Link to the portal** (default) | Opens your portal |
| **Simplified form on Discord** | Opens a Discord form to [open a ticket](#tickets-from-discord) |

The last action you used is kept for the next embed.

## Tickets from Discord

Customers open a regular Joely ticket without leaving Discord. Staff handle it on the dashboard, and the customer can follow it on the portal.

- **Setup:** post an [embed](#embeds) with **Simplified form on Discord**. Nothing else to turn on.
- **To stop:** delete the message, or post the embed again with **Link to the portal** and delete the old one.
- A button left on a server you removed answers that it is no longer linked to a support portal.

### The form

The customer clicks the button and fills in a Discord form. Every bot answer is visible to them only, in their Discord language (else English). Slow purchase loading first shows a **Fill in the form** button.

| Field | Rule |
|---|---|
| Script | Their 24 most recent purchases on your store. With more, **My script isn't listed** sends them to the portal. With one, the form is titled with it. |
| Subject | 100 characters max |
| Description | 4,000 characters max |
| Minimum lengths | Your [ticket form](https://joely.io/documentation/tickets/configuration.md) minimums still apply. A refused ticket shows the reason; the customer clicks the button again. |

Custom fields, ticket types and files are not asked. Customers who need them use the portal.

### Confirmation DM

The customer sees the ticket number and a portal link. Your bot then DMs the ticket number, subject, script and an **Open ticket** button. Staff replies arrive in that conversation, and the customer can [reply from it](https://joely.io/documentation/integrations/discord-notifications.md#replying-from-a-dm).

The ticket is created in every case. The confirmation says what happened to the DM:

| Outcome | What the customer gets |
|---|---|
| Sent | An **Open my DMs** button |
| Discord notifications off for your shop | **Turn on Discord notifications**: it turns them on and sends the DM. Joely never does it by itself. |
| Their DMs closed for your server | Where to open them (their privacy setting), and a **Retry** button |
| Your bot cannot reach them (not on this server, say), or the DM is unconfirmed | A pointer to the portal |

The ticket sidebar shows the customer's Discord DM status from creation.

### No purchase found

| Situation | What happens |
|---|---|
| **Allow Tickets Without Package** on | A general ticket, with no script |
| Script required, **Allow Manual Order ID** on (default) | Sent to the portal to type an order ID |
| Script required, typed order IDs off | The bot says this shop only accepts tickets about a purchase. No portal link: the portal would refuse it too. |
| No active Tebex store | A general ticket, purchases never mentioned. If a script is required, nobody can open a ticket, here or on the portal. |
| Purchases cannot be loaded | Sent to the portal |
| Discord account linked to several customer accounts | Sent to the portal |

### What staff see

A **Discord** badge in the ticket list and header. Workflows can match the [ticket source](https://joely.io/documentation/automations/conditions.md#ticket-source).

## Account linking

The bot recognizes a customer by the Discord account linked to their customer account on your portal.

- One Discord account can receive DMs for several customer accounts, such as two Cfx.re identities.
- Such an account cannot open a ticket from Discord: the bot sends it to the portal.
- Staff can sign in to the dashboard with Discord, one identity per account. They connect Discord separately for [DMs](https://joely.io/documentation/integrations/discord-notifications.md#staff-dm-notifications).

### Link my account

A customer with no linked account gets a **Link my account** button. It opens your portal's Discord link page.

1. They sign in with Cfx.re if needed.
2. They check the Discord account shown (avatar and @username) and confirm. No Discord sign-in is asked.
3. They go back to Discord and click the button again.

- The link works once, for 5 minutes. After that, the page asks them to authorize with Discord.
- Whoever confirms links **that** Discord account to their own customer account.
- The result page names the linked account and offers to disconnect it.
- Customers with a real email get an email naming the linked account.
