Sharles

Offer members the opportunity to progress in level according to their involvement and activity. Each level level unlocks access to a specific role. For example, a member at level 0 has no role, while a member at level 5 can get the “Tier 1” role, at level 10 the “Tier 2” role, and so on.

be able to choose an opening and closing times for tickets (this could be used for a support example: opening at 9 am from this time members can open a ticket closing at 11 pm tickets can no longer be created at that time

As said in the title, the function would be used to assign roles according to the number of members joined thanks to the link of a member already present in the server! (for example, a member invites 10 members, he gets the @rôle role! (and if possible, have a function to choose the room and mark the number of member invitations of each member on the server)

When a member wants to mutate one on their living room, the mute should be done on the lounge not on the server,

It's all in the title. being able to change the person who took care of the ticket. With a command or as a button on the bot message.

Maintenance system suggestions! The maintenance system is almost perfect, even if in a sense it is perfect because if you do maintenance to redo the permissions or to block certain rooms because of a bot bug, for example if I have a couting bot. I know that it works like classic maintenance, it creates a maintenance role but for the room in particular and it allows members to see the room but not to write and an emblem that says that the room is blocked Something that means that the last message is always up for maintenance.

The current maintenance system is very good because it allows everything to be blocked quickly. But sometimes it's not necessary to block the entire server. For example, if only one room is a problem (such as a counting room where the bot bugs), it would be practical to be able to activate maintenance only on this room. This would avoid having to block everything for a single problem. I therefore propose a maintenance system per salon: • You can choose to block one or more rooms. • A special maintenance role is created to manage access. • The rooms remain visible to members, but writing is blocked there. • An automatic message is displayed to indicate that the room (s) are temporarily blocked. With imagine with an overview of what I thought with an embed as an example.

Add a closerequest command for tickets with the possibility of entering the reason for the closure. This command allows you to ask the user if they want to close the ticket and allows the members of the ticket team to do something else. The ticket closes by itself if the person clicks yes.

Create a ticket with a drop-down menu of the user's choice in the dashboard

If there is maintenance on the server, there should be an option for users to pass the verification after the maintenance.