diff --git a/DEPLOYMENT.md b/DEPLOYMENT.md
index 91d8b7a..286c660 100644
--- a/DEPLOYMENT.md
+++ b/DEPLOYMENT.md
@@ -69,6 +69,31 @@ Check the container logs if something fails:
 docker compose logs -f
 ```
 
+### Auto-start on reboot
+
+The compose file already includes:
+
+```yaml
+restart: unless-stopped
+```
+
+That means the bot container will come back automatically after a reboot **as long as the Docker service itself starts at boot**.
+
+On the server, enable Docker once:
+
+```bash
+sudo systemctl enable docker
+sudo systemctl restart docker
+```
+
+You can verify both pieces with:
+
+```bash
+cd /DATA/AppData/discord-meeting-bot
+docker compose ps
+sudo systemctl is-enabled docker
+```
+
 ## Notes
 
 - The bot only responds to commands in the configured output channel, except `/set_output`.