Start with the questions already on the page
Record members’ questions with the thread link, date, topic and participation limits. Separate technical explanations from purchase and support questions; they may need different people.
A relevant thread is a useful choice when one bounded answer would move the discussion forward. The expert should address the question actually asked, identify the conditions that change the answer and leave further questions in the same conversation where appropriate. A thread about diagnosing a connection problem is not an invitation to introduce every feature of a product.
An AMA proposal needs a stronger reason to create a new event. Look for distinct questions the speaker can address. Record why a dedicated conversation would help, such as questions that span several threads. Repeated mentions alone do not establish a request for a session.
Check community publishing permission before choosing the format. Permission for an ordinary reply should not be treated as permission for an AMA.
Test the expert’s availability against the workload
Consider a hypothetical manufacturer whose repair engineer can explain how temperature affects battery performance. One existing thread asks whether a cold-weather reading indicates a fault. If the engineer can provide a careful general explanation but cannot stay for a live session, a relevant reply may be the manageable format. Individual repair decisions should go to the appropriate support route.
Now suppose several community discussions ask about storage, testing methods and the limits of performance measurements. An AMA could be worth proposing if the engineer can answer those topics, the community accepts the idea, and a colleague can coordinate follow-up. This is a planning example, not an account of an event.
Compare the options on three practical points:
- Member questions: an existing thread has a visible starting question; an AMA needs a clear subject with room for varied questions. Neither warrants questions written to create apparent demand.
- Expert availability: a thread may allow a bounded contribution; an AMA needs an agreed session window and a plan for questions outside that window. Confirm the speaker’s actual availability, including preparation time.
- Follow-up workload: a reply needs monitoring for clarification; an AMA may leave several unresolved questions. Estimate the work by question type and assign an owner before proposing the session.
If the speaker can only deliver prepared remarks, revise the proposal. If the follow-up owner has no access to technical or support answers, narrow the scope or use an existing discussion.
Write a proposal the community can assess
Send a short brief that makes the proposed contribution understandable. Avoid a campaign description that leaves the speaker and subject vague. Reddit’s AMA guide for newsrooms asks proposals to identify participants and expertise, discussion topics, and timing. These fields are a starting point; they do not establish that another community permits the event. Use the following brief:
| Field | What to record |
|---|---|
| Real speaker | Name, actual role, relevant expertise and the person’s confirmed participation |
| Answerable topics | Specific subjects, useful examples and topics outside the speaker’s authority |
| Member questions | Links to relevant discussions and the questions that support the proposed format |
| Community conditions | Current rules, required approval, timing, permitted materials and instructions for the session |
| Availability | Proposed window, preparation needs and how late questions will be handled |
| Unanswered-question owner | Named person, route to specialists and the process for updating an unresolved answer |
Use clear community collaboration roles to distinguish the speaker from the person coordinating the session and the person handling support. They can be the same person only if that person has the time and authority to do each task.
Keep event planning separate from any paid arrangement. A budget does not establish permission, member interest or a place on a community’s calendar. Assess the format on its usefulness and practical requirements, and obtain any required approval through the community’s stated process.
Reddit’s Moderator Code of Conduct prohibits moderators from taking moderation actions in exchange for compensation, gifts or favors from or on behalf of third parties. That boundary applies regardless of how an event is planned.
Community approval and platform rules both apply; no purchased moderation decisions, manufactured questions or promised attendance.
Decide what happens after the conversation
Before starting, agree how an answer moves from “needs checking” to a public update. Record the question link, what the speaker could answer, the unresolved point, the responsible person and the next update time. Do not turn an unanswered product question into an unsupported assurance.
For an existing thread, this can be a small follow-up record attached to that discussion. For an AMA, keep a question log so the coordinator can distinguish answered questions, requests outside scope and questions awaiting a specialist. If a later answer belongs in a support channel, explain the route without implying the public session has resolved the issue.
At the end, assess whether the chosen format allowed useful answers within the agreed scope and whether outstanding questions received the promised follow-up. Use those observations to decide the next contribution. A quiet session may still expose a useful question; a busy one may exceed the team’s capacity. Neither activity level alone settles which format to choose next.
Want to see how AI engines describe your brand today?
Get a free growth audit