A production-ready bot that automatically plays a welcome sound (or TTS message) whenever a new member joins a Discord server’s voice channel. It removes the manual hassle of greeting, standardizes onboarding vibes, and creates a polished first-touch experience. Built for reliability and scale, the Discord Welcome Sound Bot supports per-guild rules, playlists, and seamless audio output.
Created by Appilot, built to showcase our approach to Automation!
If you are looking for custom Discord Welcome Sound Bot, you've just found your team — Let’s Chat.👆👆
What it does: Plays configurable welcome audio or dynamic TTS the moment a user joins, with per-channel rules, language presets, and fallback behaviors.
What it automates: Repetitive greeting, role-specific intros, announcements, and onboarding nudges—all hands-free.
Benefits: Consistent community experience, higher engagement on first join, and fewer moderator interruptions during busy hours.
- Per-guild policy engine: map roles/channels to specific audio, TTS voices, or playlists.
- Ultra-fast join detection and sub-second audio start for a “live” feel.
- Runs headless in Docker; CI/CD ready with environment-based configuration.
- Observability baked in: metrics, logs, and audio health checks for quick troubleshooting.
- Scales with sharding; compatible with Lavalink or native @discordjs/voice pipelines.
- Real Devices and Emulators: Optional Android controller app (via Appilot) to trigger/test join flows on mobile Discord clients; emulated scenarios validate audio cues across environments.
- No-ADB Wireless Automation: Headless, network-only orchestration; zero device tethering—configure and operate entirely over API/webhooks.
- Mimicking Human Behavior: Randomized greeting delays, rotation of clips/voices, and natural volume fades prevent repetitive, bot-like patterns.
- Multiple Accounts Support: Operate multiple bot tokens or clusters safely with isolated configs, rate-limit guards, and shard-aware schedulers.
- Multi-Device Integration: Tie in Android test rigs, desktop runners, or cloud containers; orchestrate from Appilot or your CI pipelines.
- Exponential Growth for Your Account: Improve first-session retention with memorable audio greetings, nudging users to stay, explore, and engage.
- Premium Support: SLA options, onboarding assistance, and prioritized fixes for production communities.
| Feature | Description |
|---|---|
| Per-Guild Rules Engine | YAML/JSON policies bind roles/channels to audio packs, volume, cooldowns, and time windows. |
| TTS & Multilingual Voices | Generate greetings with SSML/TTS; auto-select language based on member locale or guild defaults. |
| Playlist & Soundboard Mode | Cycle curated tracks or trigger context-aware clips (welcome, tips, announcements). |
| Shard-Aware Scaling | Horizontal scale with Discord sharding; graceful hot reloads and rolling restarts. |
| Observability & Alerts | Structured logs, Prometheus metrics, health endpoints, and alert hooks (Slack/Discord). |
| Fallback & Retry Logic | Smart retries on voice connection/encoder errors; backup audio paths preserve UX. |
- Input or Trigger — The automation is initialized from the Appilot dashboard or environment config. On
voiceStateUpdate/member join, a policy lookup decides which audio/TTS to play. - Core Logic — The bot joins the member’s voice channel using
@discordjs/voice(or Lavalink), streams FFmpeg-encoded audio, and applies volume/crossfade rules. - Output or Action — A welcome clip or TTS message plays instantly; optional follow-ups (DM, rules link, role hint) are sent to guide onboarding.
- Other functionalities — Built-in retries, cooldown windows, structured logging, and parallel shard processing ensure resilience under load.
- Language: TypeScript/JavaScript (Node.js), Python (optional utilities)
- Frameworks: discord.js v14, @discordjs/voice, Lavalink (optional), Express (health/metrics), Robot Framework (optional tests)
- Tools: Appilot, FFmpeg, Docker, PM2, GitHub Actions, Accessibility hooks (audio cues), Firebase/Redis (optional state)
- Infrastructure: Dockerized runners, cloud-based containers, proxy networks (for external TTS), sharded clusters, task queues, parallel execution.
discord-welcome-sound-bot/
│
├── src/
│ ├── index.ts
│ ├── bot/
│ │ ├── client.ts
│ │ ├── events/
│ │ │ ├── voiceStateUpdate.ts
│ │ │ └── ready.ts
│ │ ├── audio/
│ │ │ ├── player.ts
│ │ │ ├── tts.ts
│ │ │ └── mixer.ts
│ │ ├── policy/
│ │ │ ├── loader.ts
│ │ │ └── evaluator.ts
│ │ ├── infra/
│ │ │ ├── logger.ts
│ │ │ ├── metrics.ts
│ │ │ └── health.ts
│ │ └── utils/
│ │ ├── env.ts
│ │ └── errors.ts
│ └── web/
│ └── server.ts
│
├── policies/
│ ├── default.yaml
│ └── examples/
│ ├── role-based.yaml
│ └── channel-windows.yaml
│
├── audio/
│ ├── welcome.mp3
│ └── playlist/
│ └── *.mp3
│
├── config/
│ ├── settings.example.env
│ └── tts.json
│
├── scripts/
│ ├── build.sh
│ └── deploy.sh
│
├── docker/
│ ├── Dockerfile
│ └── compose.yaml
│
├── tests/
│ ├── policy.spec.ts
│ └── audio.spec.ts
│
├── logs/
│ └── bot.log
│
├── package.json
├── tsconfig.json
└── README.md
- Community managers use it to greet newcomers with a short intro, so they can increase first-session retention and reduce moderator load.
- Event hosts use it to play custom intros for stage channels, so they can standardize branding and timing.
- Gaming guilds use it to auto-announce party rules, so they can avoid repeating instructions in voice chat.
- Education servers use it to play course or office-hour reminders, so students know where to go next.
How do I configure this for multiple servers?
Provide a policy file per guild (or a multi-guild policy with guild IDs). The rules engine resolves the correct audio/TTS and cooldowns at runtime.
Does it support TTS and different languages?
Yes. You can enable TTS with SSML, pick voices per guild or role, and auto-select language based on member locale when available.
Can I run this on Docker with auto restarts?
Absolutely. A Dockerfile and compose stack are included, with health endpoints for liveness/readiness and PM2 for graceful restarts.
What if audio fails to start?
The bot retries with exponential backoff, switches to a fallback audio path, and logs structured error details for quick diagnosis.
- Execution Speed: Sub-500ms policy resolution; audio join + start targeted under 1.2s on typical guilds (cold starts may vary).
- Success Rate: 95%+ successful play initiations measured over rolling 30-day uptime with retries enabled.
- Scalability: Shard horizontally to support 300–1000+ guilds; optional Appilot rigs can coordinate Android test devices for end-to-end validation at scale.
- Resource Efficiency: Optimized FFmpeg invocations and connection pooling keep CPU/RAM low; idle shards sleep audio pipelines.
- Error Handling: Structured logging, retry with jitter, health checks, alert hooks, and circuit breakers protect user experience during outages.
