Community

Talk to the team, swap notes with other builders, see what is shipping next. Three channels, each for a different kind of question. Pick the one that matches the depth of your question and the urgency of the answer.

GitHub Discussions

Best for technical questions, feature requests, and long-running design conversations. Searchable, threaded, indexed by Google. If you have an opinion you want on the record, this is the place.

• Where. github.com/Message-com/message-app/discussions (live once the org repo is public).
• Reaction time. Team responds within one business day on weekdays.
• Good for. "Why does the conversation status state machine forbid X to Y?" or "What is the right pattern to migrate from Intercom data?"

Slack

Best for quick questions, casual discussion, and live debugging. Slower for archival value because Slack search is what it is, but the latency is unbeatable. Drop in to say hi.

• Invite. Link forthcoming on the dashboard's Help → Community menu.
• Channels. #general, #api, #widget, #ai, #feedback, #show-and-tell.
• Reaction time. Best-effort. Often within an hour during US business hours.

X (formerly Twitter)

Release news, blog posts, and the occasional behind-the-scenes thread. Less back-and-forth, more announcements.

• Handle. @messagecom
• Good for. Following ship-date threads, replying to release posts, sharing what you built.

RFCs and roadmap

Major changes go through a public RFC process inside GitHub Discussions. Anyone can comment, propose alternatives, or push back. We commit to responding to every substantive comment on an active RFC. The roadmap board lives in the same repo.

Show and tell

If you build something interesting on message.com, share it. We feature community projects on the blog and (when relevant) in the changelog. Past examples have included custom widgets, third-party Slack integrations, and Zapier-style middleware. Tag @messagecom on X or post in #show-and-tell.

Reporting bugs

• Public, reproducible. File a GitHub issue with a minimal reproduction.
• Workspace-specific. Use the in-dashboard Help → Report a bug button so we get the workspace ID and recent request logs automatically.
• Security. Email [email protected] with details. We respond within 24 hours, regardless of plan. See trust for our disclosure policy.

Code of conduct

All channels follow the standard Contributor Covenant. Be excellent to one another. Disagree with ideas, not people. Anyone consistently failing the bar is removed without ceremony.

Contributing

The widget bundle and the developer documentation site are open source. PRs welcome on both. The platform itself (server, dashboard) is not currently open source; that may change later, but we will not pretend otherwise in the meantime.