# Massing Bot
This guide will walk you through the process of creating a bot for mass messaging from scratch, outlining each step along the way.
If you have any questions throughout or get stuck, feel free to visit our [Support Server](https://discord.gg/5qRpsctzjB).
In this example, the guide will walk you through the step-by-step process of creating an information embed, similar to the one shown below:
***
## Step 1: Create an Information Embed/Message & Send Initial Instructions
First, you will need to put down a "Send Message" block:
Send Message Block
Once you put the module down, you can then start customizing the message to your liking:
{% tabs %}
{% tab title="Message Customization" %}
Customization within the Message Block
{% endtab %}
{% tab title="Ephemeral Replies" %}
> Enable or disable the ability for users who are not the interaction author to see the response. Note this only hides replies to an interaction, not general messages.
{% hint style="info" %} **(!) Note (!)** : Using the **flags** section, you can make a message visible only to the user who executed the command or interacted with a dropdown menu or button. However, this functionality only applies to messages that are sent as **replies**.
{% endhint %}
{% endtab %}
{% endtabs %}
***
\
Once your info message or embeds are set up, you're ready to move on to creating the actual ticket!
> There are two main methods for opening a ticket:
>
> * Creating a command that users can type to open a ticket.
> * Allowing users to press a button or select an option from a dropdown menu.
>
> Both methods follow a similar setup process, but the button and dropdown menu approach is a bit more complex—so we’ll focus on that.
1. First, navigate to the **Components** section and click **Add Component**. From there, you can choose whether you want to create a **button** or a **dropdown menu**. While both options work well, I recommend using a dropdown menu—it tends to look cleaner and more organized, especially when offering multiple ticket categories.
2. After adding your component, you’ll need to insert a **"Create Channel"** block. For the channel name, you can use a format like:
`w2p : {interaction[user.username]}`
This will automatically include the username of the person who opened the ticket, making it easy to identify who the ticket belongs to.
{% hint style="info" %}
To configure the permissions for the channel, see the "Customize Channel Block" tab below:
{% endhint %}
{% tabs %}
{% tab title="Create Channel Block" %}
{% endtab %}
{% tab title="Customize Channel Block" %}
**For the permissions, you can use as follows:**
> Role/User ID
>
> {user\[id]}
>
> Allow :
>
> View Channel , Send Messages
\
Add Permission:
> Role/User ID
>
> {interaction\[guild.id]}
>
> Deny :
>
> View channel
{% endtab %}
{% endtabs %}
3. Next, to send a message into the newly created ticket channel, add a **"Send Message"** block. Change the **Channel Type** to **Channel ID / Variable**, then paste in the **Channel ID variable** from your **Create Channel** block. This ensures the message is sent directly into the correct ticket channel.
{% tabs %}
{% tab title="Channel Variable" %}
{% hint style="info" %}
**This is where you can find your channel variable:**
{% endhint %}
\
\
{% endtab %}
{% tab title="Message Block Configuration" %}
{% hint style="info" %}
This is where you will paste your Channel Variable:
{% endhint %}
{% endtab %}
{% endtabs %}
4. Next, return to the **Send Message** block you just added and attach a **Button Component**. This button will allow users to submit their ad when clicked.
To set this up, simply add a **Modal Block** and connect it to the button. This will open a form-style popup where users can enter their ad details.
5. Next, add **two Send Message** blocks, and place a **Pin Message** block underneath each one.
6. In each **Send Message** block, insert one of the variables from your modal. You can find these variables in the modal block here:
{% hint style="info" %}
I recommend placing your **ad content variable** in the **first Send Message** block, and your **invite link variable** in the **second**. This keeps the information organized and makes it easy for staff to review both the ad and the invite separately.
***
Note: Your variable names will vary based on what you entered for your **Field Identifiers** in the modal.
{% endhint %}
7. For each **Pin Message** block, change the **Message Type** to **Selected Message**. Then, enable the **Message Selector** and link it to the corresponding **Send Message** block.
8. Next, add one final **Send Message** block below everything. In this block, send the link to your **access server** so users know where to go next.
And that’s it — your ticket system is now complete!
***
## Step 2: Creating a Checkpoint
1. Creating a checkpoint is simple! Just create a **new command** and set the **trigger** to whatever you want your checkpoint name to be.
2. Next, add a **Send Message** block and place your **checkpoint layout** inside it.
And that’s it — your checkpoint is ready to go!
***
## Step 3: Finalize and Select Sep Time command
Will be updated soon...
---
# 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://docs.botwiz.dev/botwiz-guides/botwiz-guides-1/apm-guides/massing-bot.md?ask=
```
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.
