Discord
MAW Assistant in your own Discord server: it tells your community you are on air, and answers when they ask what is playing.
MAW Assistant is one bot with two places to live. In your direct messages it is your own assistant, and answers about your station — see MAW Assistant. In a Discord server of your own, which is what this page is about, it speaks to your community: it says when you go on air, how the broadcast went when you come off, and keeps one message up to date with what is happening right now.
What it does in a server
| What | How it works |
|---|---|
| Live notices | A message in the channel you choose when a broadcast starts, with who is on air and a Listen button to your page. |
| End-of-broadcast summary | When you come off air: how long you were on, the peak audience and the average. Anything that was not measured shows a dash and the reason, never a stand-in number. |
| A self-updating panel | One message the bot keeps editing — on air or off, listeners now, time on air, the current track when it is known, and your all-time peak. It is edited, never reposted, and it has its own channel setting, so you can give it a quiet channel of its own. |
| /nowplaying | Anyone in the server can ask, and the answer is public in the channel. |
Adding it to a server
In Control, open MAW Assistant and use Add MAW Assistant to a server on the station the server should follow. That takes you to Discord's own consent screen, where you pick the server and grant the permissions the bot asks for: read the channel, send messages, embed links, read message history — that one only so it can find its own panel message again — and mention everyone, which it uses only if you choose @everyone as the role to mention. It never asks for Administrator.
To add a bot to a Discord server you need Manage Server in that server. If you do not have it, ask someone who does — but note that the button in Control has to be pressed by the station owner, because the link is made against your workspace.
The link is made for the station you pressed the button on, so a server always knows which station it is talking about. Two stations in two servers means two links.
Setting it up in Control
Once the bot is in, everything else is set in Control, on the server's own row in MAW Assistant. The channels and roles are picked from lists read out of your server, so there is no id to copy and nothing to type.
- Notices channel — where the live notices and the summary go. Needed: without it nothing is sent.
- Panel channel — where the self-updating panel lives. It can be the notices channel, or one of its own.
- Staff channel — optional, for the things only your team should see.
- Role to mention — optional, and it can be
@everyone. - Events — which of them it sends, one switch each.
- Language — what it writes in, in this server.
A channel MAW Assistant cannot write in is not offered, and Control names it and says why rather than letting you choose a setting that could not work. If your server's lists cannot be read at all — the bot was removed, say — Control tells you that too, and the events, the language and the panel keep working.
Until a channel is chosen, nothing is posted — Control says so rather than pretending the link is working.
Which channel gets what
Two channels, on purpose: the things your listeners want to hear about, and the things only you want to hear about.
| Event | Channel | Default |
|---|---|---|
| A broadcast starts | Public | On |
| A broadcast ends, with the summary | Public | On |
| A programme is about to start | Public | On |
| The schedule changed | Public | Off |
| New audience record | Public | Off |
| Unexpected disconnection | Staff channel | On |
| Stream recovered | Staff channel | On |
| AutoDJ problem | Staff channel | On |
| MAWCast incident | Staff channel | On |
If no staff channel is chosen, the staff events are simply not sent — they never fall back to the public one.
A notice can mention a role, and that role is chosen in Control. You can choose @everyone, which pings every member of the server every time a notice goes out — it is off by default, and Control says what it costs before you pick it. For that ping to arrive the bot needs Discord's Mention Everyone permission: servers added before 23 September 2026 were not given it, so add the server again with the same button — the flow re-authorises it — or grant that permission to the bot's role in Discord.
What it never posts
- Storage warnings and anything about billing. Those are yours, and stay in Control.
- Rehearsal and DEMO broadcasts. A server only ever hears about real air time.
- Recordings, of any kind. MAWCast does not record your broadcasts, and MAW Assistant has nothing to post that would come from one.
How many servers your plan includes
| Plan | Discord servers |
|---|---|
| Starter | 1 |
| Air | 1 |
| Broadcast | 2 |
| Network | 2 |
The limit is checked twice: when you add a server, and again when something is about to be delivered. If a workspace ends up over its limit — after a downgrade, say — the newest links are paused rather than dropped, and Control says why.
If the bot is removed
Removing MAW Assistant from the server in Discord stops delivery at once. Control keeps the link and shows it as Removed, with its settings intact: add it back and it picks up where it left off. If the channel is deleted or its permission is taken away, the link is paused with that reason shown in Control rather than retried forever. If your subscription lapses, delivery stops and the bot stays where it is.
Disconnect in Control stops delivery from MAWCast's side. The bot stays in the server until you remove it there.
Still need help? Write to contact@mawcast.com.