Explain what support can help with
Use a short welcome message and a small set of choices: getting started, resources and replays, access, sessions, or account questions. Adapt the labels to the service people joined.
Ask for the minimum useful context
A resource question may need a cohort and session date. An access issue may need the program and affected area. Direct identity and payment verification to the approved secure flow rather than asking for secrets in a ticket form.
Set the expectation for the conversation
Explain that AI can use approved knowledge and configured workflows, and that a person can take over when needed. Do not promise an instant completed action for every request.
Publish and test the member journey
Follow the supported Discord panel setup. Check the labels, private ticket access, welcome message, and handoff from a member’s perspective before sharing the entry point widely.