BOTS AI SERVICES TUTORIALS SCAM REPORTS CONTACT

AXIA Setup Tutorials

Getting started

Start with the server base. Then move on to sales, payments, service and extra systems.

  1. Acesse o Discord e use /botconfig no servidor onde o bot está instalado.
  2. Open Definitions and configure name, icon, default color, main channels and roles.
  3. Set up a payment method before sending sales boards.
  4. Create products or dashboards only after channels, roles, and logs are ready.
  5. Do a thorough test by purchasing an inexpensive product before releasing it to the public.

Permissions

/permissao → Painel de permissões

The permissions system defines who can use administrative commands. Configure this before handing the bot over to other team members.

  1. Use /permissao para abrir o painel.
  2. Click Add and select the user or role that can manage the bot.
  3. Use List to check who is authorized.
  4. Use Remove when someone leaves the team.
Attention: do not give permission for public office. Anyone with access will be able to touch sales, payments, panels and sensitive settings.

Menu /botconfig

/botconfig

O /botconfig é o centro de administração. A partir dele você acessa vendas, proteção, automações, atendimento, filas, sorteios, cloud, engajamento, status e tools.

To configure systems

Open the desired category, adjust the fields and return using the return button when finished.

To publish dashboards

Configure title, description, channel and roles before clicking Send Panel.

General settings

/botconfig → Definições

Use this area to configure the base that will be used by multiple systems.

  1. Open Bot to adjust general information, default color, visual name and identity.
  2. Open Channels to define logs, purchase channels, feedback channels, and auxiliary channels.
  3. Open Positions to define administrative positions, customer positions and staff positions.
  4. Open Payments to define accepted methods and credentials.
  5. Open Invitations e Suggestions only if these systems are used on the server.

Channels and roles

/botconfig → Definições → Canais/Cargos

Channels and roles are the backbone of systems. Without this, tickets may open in the wrong places, logs may not be sent and staff may not see private channels.

  • Create an administrative log channel.
  • Create a public channel for sales, verification or service panels.
  • Create categories for tickets, purchases, queues or analyzes when necessary.
  • Define staff position, customer position and special positions before activating systems.

Bot Status

/botconfig → Status

Configure the presence of the bot to make the application more professional. Use short and objective texts, such as the store name, number of systems or support message.

  1. Open Status.
  2. Choose the type of activity: playing, watching, listening or competing.
  3. Define the main text and, if applicable, image or presence icon.
  4. Save and wait a few seconds for Discord to update.

Customization

/botconfig → Personalização

Use this area to leave the bot with the server's identity. Configure emojis, default color, banners, images and visual texts.

  1. Configure the main color of the server.
  2. Register custom emojis used in buttons and logs.
  3. Configure default images for dashboards, if the system allows.
  4. Review all published dashboards after changing branding.

Sales system

/botconfig → Vendas

The sales system controls the store, products, cart, stock, coupons, keys, purchase messages, deliveries and public panels.

  1. Activate the sales system.
  2. Configure purchase terms, questions button, extra message and cart behavior.
  3. Configure at least one payment method.
  4. Crie produtos com /criar ou painéis com /criar_painel.
  5. Upload the dashboard to a public channel and make a test purchase.

Create products

/criar → /config

Each product has a name, price, description, stock, images, delivered position, signature, purchase button and advanced settings.

  1. Use /criar nome: Produto para criar o produto.
  2. Use /config id: ID_DO_PRODUTO para abrir o painel do produto.
  3. Configure name, price and description.
  4. Open Stock to add deliverable items.
  5. Open Advanced Settings to adjust banner, thumbnail, color, coupon, signature and buy button.
  6. Click Update Message to reflect channel changes.

Stock

/config → Estoque

Inventory defines what will be automatically delivered after approved payment. It can be an account, code, key, link or any delivery text.

  1. Abra o produto com /config.
  2. Click Stock.
  3. Choose to add by line, one by one or by file.
  4. Use backup before making large changes.
  5. Update the product message to show the correct quantity.

Sales panels

/criar_painel → /config_painel → /set_painel

Panels group multiple products into a single message. They are ideal for stores with categories, plans, or many items.

  1. Use /criar_painel para criar um painel.
  2. Use /config_painel para adicionar produtos e personalizar título, descrição e imagens.
  3. Use /set_painel para publicar o painel no canal escolhido.
  4. After changing product or inventory, update the published dashboard.

Cart

/botconfig → Vendas → Carrinho

The cart controls the flow between selecting product, editing quantity, reviewing summary, applying coupon and generating payment.

  1. Configure the cart expiration time.
  2. Define whether the cart will be in a channel, topic or private message.
  3. Test adding more than one product to the same cart.
  4. Check that the increase, decrease and cancel buttons work correctly.

Coupons and keys

/botconfig → Vendas → Cupons/Keys

Coupons apply discounts to purchases. Keys allow redemptions with time, position or configured plan.

  1. In Coupons, create name, percentage, minimum value and number of uses.
  2. In Keys, configure delivered position, duration time and log channel.
  3. Generate keys only after configuring the plan correctly.
  4. Use /resgatar para testar uma key antes de divulgar.

Subscriptions

/config → Configurações Avançadas → Assinatura

Subscriptions are expiring products. The buyer receives a temporary role or access and can renew before it expires.

  1. Abra o produto com /config.
  2. Enter Advanced Settings and then Subscription.
  3. Activate the subscription and set the duration in days.
  4. Configure the position that will be delivered to the buyer.
  5. Test purchase, renewal, expiration and removal of position/channel.

Repost, restock and sales extras

/botconfig → Vendas

These features help keep the store alive: automatic repost of panels, new stock notification, recent purchases and feedback after purchase.

  1. Use Repost to automatically resend panels at set intervals.
  2. Use Restock to notify you when a product receives new stock.
  3. Activate Recent purchases if you want to show store activity.
  4. Configure Feedback Mention only if you want to remind the customer to rate.

Payment methods

/botconfig → Definições → Pagamentos

Configure payment methods before releasing sales. The ideal is to maintain an automatic and a manual form of security.

Automatic

Mercado Pago, IMAP, PayPal, Asaas or integrations that confirm payment without manual action.

Manuals

Semi-automatic PIX, internal balance or staff conference when there is no gateway configured.

Mercado Pago

/botconfig → Pagamentos → Mercado Pago

Mercado Pago generates QR Code PIX and automatically approves purchases when payment is confirmed.

  1. Create or access your Mercado Pago account.
  2. Copy the production token.
  3. Paste the token into the bot payment panel.
  4. Activate the method.
  5. Make a test purchase with a low value and check if the order approves on its own.

IMAP

/botconfig → Pagamentos → IMAP

IMAP reads bank confirmation emails to approve payments. It is recommended for Nubank, Inter and PicPay when the automatic gateway is not available.

  1. Use the email that receives notifications from the bank.
  2. Create a application password in the email provider when necessary.
  3. Enter the bank, email, application password and PIX key that will receive payments.
  4. Enable IMAP and send a test payment.
  5. Check if the bot found the email and approved the correct purchase.
Important: application password is not the normal email password. It's a separate password created in the security settings of Gmail, Outlook, or an equivalent provider.

Semi-automatic PIX

/botconfig → Pagamentos → SemiAuto

The semi-automatic PIX shows the PIX key and lets the team check the payment manually. Use as a backup plan when automations are not active.

  1. Register PIX key, recipient name and payment instructions.
  2. Define the channel or position responsible for approving requests.
  3. Instruct the customer to send proof in the cart or ticket.
  4. After checking, approve or deliver manually.

PayPal and Asaas

/botconfig → Pagamentos → PayPal/Asaas

PayPal and Asaas expand payment options for customers who prefer card, balance or external methods.

  1. Create the application in the provider panel.
  2. Copy the credentials requested by the bot.
  3. Save to payments panel.
  4. Activate the method and generate a test purchase.
  5. Check approval, error and cancellation logs.

/gerarpix command

/gerarpix

Use /gerarpix para criar cobranças avulsas fora do carrinho. É útil para taxas, pedidos personalizados ou vendas combinadas manualmente.

  1. Enter value and user, if the command requests it.
  2. Choose the configured method.
  3. Send the QR Code or copy and paste code to the customer.
  4. Track automatic or manual approval depending on the method used.

Ticket system

/botconfig → Atendimento

Tickets organize support, manual purchases, complaints, questions and private consultations. Configure each option with attendant position, category and messages.

  1. Open Support.
  2. Create or select a ticket option.
  3. Configure button, description, category, log channel and attendant position.
  4. Set up initial questions if you want to collect data before the service.
  5. Submit the panel in a public channel and test opening/closing ticket.

Ticket feedback

/botconfig → Atendimento → Feedback

Feedback allows the customer to evaluate the service after closing the ticket.

  1. Choose the channel where reviews will be published.
  2. Choose the model: evaluation, standard card or container.
  3. Customize texts and appearance if the panel allows.
  4. Close a test ticket and check if the evaluation request appears.

Opening hours

/botconfig → Atendimento → Horários

Opening hours control when new tickets can be handled and can block after-hours conversations.

  1. Set days of the week and start/end time.
  2. Configure service ended message.
  3. Configure service started message.
  4. Test an open ticket before, during and after the configured time.

/close command

/fechar

O comando /fechar deve ser usado apenas dentro de canais de ticket. Ele finaliza o atendimento, envia logs e inicia o fluxo de feedback quando configurado.

  1. Enter the ticket channel.
  2. Use /fechar.
  3. Confirm closing if the bot asks for confirmation.
  4. Check if logs, transcript and feedback were sent correctly.

Automatic actions

/botconfig → Automações

Automatic actions control server events without manual commands: welcome, messages, reactions, autorole, anti-fake, auto-thread, auto-lock, chatbot, recruitment and more.

  1. Open Automations.
  2. Choose the system you want to configure.
  3. Activate the status only after filling in channels, positions and messages.
  4. Test with a controlled account or channel before releasing to everyone.

Welcome, messages and news

/botconfig → Automações

These systems send automatic messages on defined events: member entry, scheduled messages, auto-reactions and news.

  1. Configure send channel.
  2. Write panel title, description, and text.
  3. Use variables such as user, server or role when the system allows.
  4. Activate and test with a real event or test command.

AutoRole and Server Tag

/botconfig → Automações → AutoRole

AutoRole automatically delivers roles. It can also be used to deliver a position to whoever uses the server tag.

  1. Open AutoRole.
  2. Configure the default role for new members if desired.
  3. Configure the role for members using the server tag.
  4. Enable automatic removal to remove the role when the person removes the tag.
  5. Configure logs without mentioning members directly, to avoid unnecessary markup.

Auto-Lock and Auto-Thread

/botconfig → Automações

Auto-Lock locks channels at configured times or situations. Auto-Thread automatically creates threads to organize conversations.

  1. In Auto-Lock, choose locking channels and times.
  2. Configure opening and closing messages.
  3. In Auto-Thread, choose channels where threads will be created.
  4. Set default name, initial message and creation rules.

Chat bot and AutoResponder

/botconfig → Automações

Chat Bot responds to conversations using a configured API. AutoResponder responds to fixed triggers like keywords and phrases.

  1. For Chat Bot, configure API key, prompt and allowed channels.
  2. Define whether it only responds to mentions or any message in the allowed channel.
  3. For AutoResponder, create a response, define triggers and choose search mode.
  4. Configure cooldown to prevent spam.
  5. Use the test button before activating on public channels.

Engagement and levels

/botconfig → Engajamento/Níveis

Engagement systems encourage members to chat, participate and climb the rankings.

  1. Configure valid channels for scoring.
  2. Set cooldown to avoid message farm.
  3. Configure rewards by level, position or ranking.
  4. Use /rank para conferir a classificação.

Raid Boss

/botconfig → Engajamento → Raid Boss

Raid Boss turns community messages into damage against a boss. When the boss is defeated, participants can receive temporary rewards.

  1. Configure the boss channel, where progress will be shown in real time.
  2. Configure the notifications channel, where events and rewards will be announced.
  3. Set boss life, message damage, cooldown and daily limit.
  4. Configure the list of bosses, themes, images and rewards.
  5. Define temporary position, reward duration and participation criteria.
  6. Activate the system and follow the first cycle with the team.

Cloud Auth

/botconfig → Cloud

Cloud Auth verifies members via OAuth2 and can enable actions such as registering authorized users and pulling members to a server where the configured bot is present.

  1. Open Cloud no /botconfig.
  2. Configure dashboard channel, verified role and log channel.
  3. In the Discord Developer Portal, add the Redirect URI below:
https://axiasolutions.com.br/api/auth/discord/callback
  1. Copy the Client Secret from the application and save it in the dashboard.
  2. Configure the bot used to pull members, if using this function.
  3. Customize the panel title, description, banner, thumbnail and emojis.
  4. Activate the system and click Send Panel.
  5. Carry out a test check and check if the position was delivered.

Tools

/botconfig → Tools

The Tools system brings together extra tools in its own panel. Each person can configure their token, when the function requires an individual token.

  1. Open Tools no /botconfig.
  2. Use Customize to change title, description and banner.
  3. Use Restrict roles to define who can access the panel.
  4. Use Send Panel to publish to a channel.
  5. In the public dashboard, users must configure token before using tools that require it.

FF Queues

/botconfig → Filas

The queuing system organizes matches, bets, mediators, players, payments, streaming and entry/exit panels.

  1. Configure match modes, values ​​and number of players.
  2. Define mediator role and category/channel where rooms will be created.
  3. Configure Mercado Pago for automatic payment or intermediary PIX for manual flow.
  4. Submit the queue panel in a public channel.
  5. Test entry, exit, call mediator, define winner and end match.

Analysis system

Painel do jogador → Solicitar análise

The analysis system creates a queue for analysts to check player requests, such as match review or screenshot validation.

  1. Configure the channel where requests will be sent.
  2. Configure analyst position.
  3. In the player panel, enable the button Request analysis.
  4. When the player requests it, the analysis is queued.
  5. The analyst takes over and the message status changes as the service progresses.

Roulettes

/botconfig → Filas/Loja de coins → Roleta

Roulettes use coins from games to allow players to spin and compete for configured prizes.

  1. Configure the cost per turn.
  2. Register prizes, chance and quantity available.
  3. Define whether the reward delivers coins, position, manual item or personalized reward.
  4. Submit the roulette panel in a public channel.
  5. Test a turnover with an administrative account before releasing.

Sweepstakes

/botconfig → Sorteios

Sweepstakes allows you to create campaigns with prize, time, number of winners and requirements.

  1. Open the sweepstakes panel.
  2. Configure title, description, prize and duration.
  3. Define the channel where the draw will be sent.
  4. Configure job requirements, if any.
  5. Finish the draw and check if the winner has been announced.

VIP

/botconfig → Vips

The VIP system manages temporary positions, plans and query commands.

  1. Configure VIP plans and delivered roles.
  2. Use /setvip para entregar VIP a um membro.
  3. Use /meuvip para o membro consultar tempo restante.
  4. Use /removevip para remover manualmente.

Roblox / Robux

/botconfig → Roblox → Robux

The Roblox system organizes the sale of Robux by gamepass, group or configured methods, with calculation, panels and order tracking.

  1. Configure prices per 1000 Robux.
  2. Configure minimum and maximum purchase limits.
  3. Configure group, order categories and log channel.
  4. Customize button panel, texts and emojis.
  5. Send the panel and test a purchase simulation.

Middleman

/botconfig → Roblox → Middleman

Middleman mediates exchanges and negotiations. You can have automatic Trade Pix mode and Cross Trade with human staff.

  1. Activate the Middleman system.
  2. Configure Trade Pix rate and Cross Trade rate.
  3. Define MM position, proof channel and service categories.
  4. Customize the public dashboard.
  5. Submit the dashboard and test the full flow with two accounts.

Moderation

Comandos administrativos

Use moderation commands to keep the server organized. They should be restricted to trusted positions.

Common commands

/ban, /kick, /mute, /warn, /clear.

Channel control

/lock, /unlock, /nuke e comandos de cargo.

Recommendation: Keep moderation logs enabled for team auditing.

Disclosure and announcements

/anunciar → /dm

Use ads to send announcements in channels and DM advertising only when allowed by server rules.

  1. Use /anunciar para criar ou editar uma mensagem em canal.
  2. Configure title, description, buttons, images and sending channel.
  3. Use preview before officially submitting.
  4. Use DM advertising carefully, with short texts and without spam.

Social networks

/botconfig → Instagram/Tellonym/Twitter

Social systems simulate profiles, posts, comments or internal server interactions. Configure channels and permissions before activating.

  1. Choose the social network you want to activate.
  2. Configure main channel and log channels.
  3. Set creation, deletion, and moderation permissions.
  4. Test a post and interaction before publishing.

Backup

/botconfig → Backup

Backups protect bot settings, products, dashboards, inventory, and important data.

  1. Back up before major changes.
  2. Store the file in a safe location.
  3. Don't share backups with people outside the team.
  4. Test restore only in a controlled environment.