TrolyPage

An autonomous Marketing & Sales operating system for businesses that want AI-powered omni-channel growth.

Contact Info

Follow Us

Social Media Publishing 3 min read

Discord Scheduled Events for SaaS Office Hours: A 30-Minute Runbook

TrolyPage

Nov 22, 2026
6 views
Discord Scheduled Events for SaaS Office Hours: A 30-Minute Runbook

Choose the room by how customers will participate

A UK SaaS founder wants to run an office hour for customers who are setting up approval rules. Assume a small customer Discord, one host, one producer and roughly 12 expected attendees. The agenda and counts are illustrative. Give this session one deliverable: each attendee leaves with a rule they can test in a demo workspace.

Use a Voice Channel for a small clinic where attendees can ask follow-ups aloud, subject to your channel permissions. Use a Stage in a Community server when there are named speakers and most attendees will listen. Stage moderators manage who comes up to speak. If the session lives in a text channel or a webinar tool, the scheduling menu also offers Somewhere Else. Check the current options and permissions in Discord’s Scheduled Events guide and its Stage Channels FAQ.

Copy this run sheet for a small Voice Channel clinic

When, UK local timeOwnerAction and evidence
Two days beforeProducerCreate “Office hours: Test your first approval rule.” Specify Tuesday 16:00, the intended customer room and one prework question: “What should wait for approval?”
15:45Producer and backup hostRehearse from a normal attendee account with the customer role. Verify that it can find and join the correct room. Test the invite path only if external guests are intended.
16:00–16:05HostStart the event. Show one approval rule in a workspace with sample records and paste the test prompt into the companion text channel.
16:05–16:25Host and producerTake two questions, work through one example and let attendees try their own rule. The producer logs unanswered questions without copying customer data.
16:25–16:30Backup hostPost the three-step test, who will answer outstanding questions and when. The producer records attendance and access issues.

Test the link as the person receiving it

Discord distinguishes direct event links, which require permission to view the event, from event server invites, which can let non-members join the server. For a customer-only clinic, share the direct link with members in the appropriate channel. In the rehearsal, make sure the customer role can join and an account without that role cannot enter the restricted room. Give the backup host the event permissions they need and test that they can operate the event and channel before the day.

Exception for restricted demonstrations

When the screen would show private customer records, switch to a demo workspace with invented data or save the case for a separate private support conversation. If attendee access fails, the producer can share an approved text-channel summary and a rescheduled time with the intended audience. Avoid widening channel permissions during the session as a quick fix.

Check what people could do after joining

Keep interest counts, actual attendance and completed tests separate. For example, 12 people indicate interest, eight show up and five confirm that their rule held back a sample submission. That tells the founder that three attendees might need follow-up. The producer can also log “could not join” separately from “joined and could not run the test” so the next event fixes the right problem.