Temply setup and usage guide.

1. Temply overview

Temply is made up of three main surfaces. The main Discord bot runs temporary voice features inside guilds. The website provides the landing page, dashboard, billing, legal, status, shard, FAQ, and documentation pages. The support bot runs ticketing, moderation, verification, automod, and premium role syncing in the support server.

2. Main bot first-time setup

Use the main setup flow in Discord to configure the server. Temply supports guided setup using embeds and dropdown-based configuration so admins can choose the join channel, category, setup mode, feature visibility, logging, and statistics without relying on a single confusing command wall.

• Choose the join-to-create voice channel.
• Choose the category where temporary rooms should be created.
• Select the room generation mode.
• Configure optional outputs like log channels and statistics channels.
• Enable or disable room-owner features for that guild.

3. Room generation and cleanup

When a member joins the configured hub channel, Temply creates a temporary room, moves the member into it, and tracks ownership and server settings for that room. Once the room becomes empty, Temply cleans it up automatically.

4. Room controls and panel behavior

The room panel is the main user-facing control surface. Depending on what the guild has enabled, members may be able to rename the room, set a member limit, adjust bitrate, change region, lock the room, hide the room, trust or untrust users, reject access, kick members, transfer ownership, and use linked text features.

If a feature is disabled by the server, Temply hides it from the panel and blocks the related action path.

5. Slash commands and guided controls

Temply supports slash commands alongside the room panel. Some commands, such as bitrate and region, use guided selection flows so users do not need to type raw values manually. Admin and support commands are permission-gated separately from normal room-owner actions.

6. Dashboard and website access

The dashboard uses Discord OAuth sign-in. Once signed in, users can see guilds where they have sufficient management access and where Temply is installed. The dashboard can be used as an alternative to parts of the in-Discord setup flow, including configuration changes and some premium options.

7. Premium system

Temply premium is tied to active billing state. Premium can unlock per-guild branding features such as nickname, avatar, banner, and bio controls for the bot profile in a guild. Plan caps are enforced by tier:

• Premium: 1 guild
• Premium Plus: 3 guilds
• Premium Max: 15 guilds

If a subscription ends or becomes inactive, Temply can automatically remove premium access, clear premium branding assignments, and remove premium support roles.

8. Main bot logging and statistics

The main bot supports server-scoped logging and a statistics board. If logging is enabled, Temply sends embed-based server events to the configured log channel. If the statistics board is enabled, Temply keeps a server-only statistics embed updated in the selected channel.

9. Support bot setup

The support bot is configured separately for the support server. It can provide ticket panels, verification, moderation commands, automod, premium role syncing, support logs, join and leave logs, and ticket archives. Staff-facing ticket controls are tied to the configured support staff role or equivalent moderation permissions.

10. Support tickets and transcripts

The support bot supports ticket creation, claim, close, priority, rename, add and remove member actions, reopen, and transcript export. Transcript generation now happens in memory only. Temply attaches the transcript to the response, can archive it to a configured archive channel, and stores transcript metadata in PostgreSQL instead of keeping permanent transcript files on disk.

11. Verification, moderation, and automod

The support bot can run a rules-based verification flow, staff moderation commands, moderation logs, and automod. Automod can act on blocked words, obfuscated blocked words, links and invites, mass mentions, mention spam, excessive caps, repeated character spam, duplicate spam, and fast message bursts.

12. Status and shard pages

The website includes operational pages so admins and users can check health without going into Discord first.

• /status shows the live state of the website, bot layer, and database layer.
• /status/shards shows shard fleet information for the Temply bot cluster.
• The status experience is designed to update live and reflect overall service health cleanly.

13. Data and infrastructure

Temply uses PostgreSQL for persistent service data and Redis for runtime caching and coordination. The main bot, website, and support bot all depend on that shared infrastructure. Stripe-backed billing state and Discord OAuth are also part of the wider system where relevant.

14. Troubleshooting

• If a room control is missing, check whether the feature is disabled for that guild.
• If dashboard access looks wrong, refresh the guild list or recheck guild permissions and bot presence.
• If premium looks out of sync, verify the billing status and let the sync flow catch up, or use the support tooling to force a sync where appropriate.
• If support tickets seem stuck, check whether a stale ticket record exists or whether the old channel was manually removed.
• If something feels unavailable, check the status and shard pages first.