Skip to content
Community support guides

Guides · Member conversations

Support messages for learning communities

Use clear welcome messages for onboarding, resources, membership access, and community participation. Ask for context that helps the next step, without treating a form as account verification.

Welcome a learner or new member

Name the program and ask what the person is trying to do. Course resources, replay locations, session questions, and access issues should be easy to recognize.

Hi {user}, welcome to {server} support.

What are you trying to do: start the program, find a lesson or replay, join a session, or resolve an access issue?

Tell us the relevant program or cohort and what is blocking you. We will use the approved guidance and bring in a person when needed.

Do not share passwords, one-time codes, or account tokens.

Ask about membership access privately

Request the program and the blocked area. Use the organization’s approved account-linking or verification flow for personal checks. An email or username can help locate a record but does not, on its own, authorize disclosure.

Hi {user}, this is your access request #{ticketNumber}.

Tell us which program you joined and which resource or community area you cannot open.

Personal account checks follow our official verified support flow. Do not post payment-card details, passwords, or identity documents here.

Prepare a useful coaching request

Ask for the relevant program, the question, and material the member wants reviewed. Explain the approved submission process and route personal coaching judgment to the coach.

Hi {user}, let’s prepare your coaching question.

Which program or session is this about? What would you like the coach to review, and what have you tried?

Share only the material needed for the review through the approved submission route. Our program team will confirm the next step.

Keep appeals and exceptions clear

Acknowledge the question, identify the applicable published rule, and let the appropriate program or community owner decide an exception. Preserve the conversation context for that review.

Hi {user}, your program or community review request is #{ticketNumber}.

Explain the decision or rule you want reviewed and the relevant context.

The responsible team will consider the request. We will keep the explanation and next step in this conversation; an exception is not confirmed until that team decides.