Temply
Documentation
A practical guide to setting up Temply, managing temporary voice channels, using the dashboard, handling Premium, and understanding support and recovery tooling.
Temply has two public-facing surfaces most users care about: the main temp-voice bot and the website. The main bot handles room creation, ownership, controls, recovery, and server-specific automation. The website handles the landing page, dashboard, Premium checkout, documentation, FAQ, and public status pages.
Run the guided `/setup` flow in Discord to configure the basics for a guild. Temply uses embed-driven setup instead of a single long command wall, so admins can work through the major choices cleanly.
Temply supports multiple room generation modes, including default, sequential, predefined, clone, and dynamic behaviour. Built-in presets such as Community, Gaming, Support, and Dynamic give admins a strong starting point before fine-tuning the details.
Once a member joins the configured entry voice channel, Temply creates a room, moves them into it, and tracks the room as managed state. When the room is empty, Temply cleans it up automatically. The system is designed to behave well even during bursts of joins and leaves within the same guild.
The room panel is the main member-facing control surface. Depending on what the guild enables, owners may be able to rename, set a limit, adjust bitrate, change region, lock or unlock, hide or unhide, create or remove linked text, trust users, reject access, kick members, transfer ownership, claim a room, or use LFM tools.
Temply can remember room-owner behaviour and apply it later. This can include remembered room names, favourite limits, preferred templates, and trusted users. Members can also use defaults so new rooms feel consistent without repetitive setup every time.
Temply includes ownership continuity logic so rooms feel more stable. If the owner leaves, Temply can start a return grace period, transfer ownership to the longest-present remaining member if needed, and restore the original owner if they return inside the restore window.
Temply includes recovery tooling for both live use and admin intervention. It can repair panels, repair room status posts, clean orphaned text references, heal missing ownership state, and rebuild room metadata after Discord-side issues or manual interference.
/recover room repairs the room you are currently in./recover guild scans and repairs managed rooms across a guild./recover statistics refreshes board and cache state./temply-status shows live room health and setup outputs.Temply supports optional server-specific logging and an optional statistics board. Logging is useful for moderation and visibility, while the statistics board keeps a live overview of room counts and related health indicators for that guild.
The website dashboard uses Discord OAuth. Once signed in, users can see guilds where Temply is installed and where they have sufficient permissions, then manage supported parts of the guild configuration from the web instead of returning to Discord for every change.
Temply Premium controls per-guild branding features such as nickname, avatar, banner, and bio. Premium is enforced through plan caps and entitlement logic.
Temply supports both monthly and lifetime billing flows for all three tiers. Monthly uses subscription checkout and lifetime uses one-time checkout.
The support bot is configured separately and focuses on support-server workflows. It can run ticketing, verification, automod, moderation logging, transcript archiving, Premium role syncing, and related support operations.
Support tickets can be claimed, closed, reopened, prioritised, renamed, and exported. Transcript generation happens in memory, can be attached to responses, and can be archived to a configured channel while metadata is stored in PostgreSQL.
The Temply website includes public service visibility tools so people can check health before assuming the bot is fully down.
/status for website, bot, and database health./status/shards for bot shard visibility.