The Messages app is Assembly Studio’s built-in communication channel. Your team uses it from the Dashboard; your clients use it from the Portal. Threads are scoped to clients (or companies) — everyone on your team can see and reply to any client thread, but clients only see their own.If your firm currently sends client communication over email and you want to consolidate, Messages is usually the first app to lean into.
Messages handles team-to-client and team-to-company communication. It doesn’t handle:
Client-to-client messaging. Multiple clients can’t talk to each other through Messages. If your firm runs a cohort, a community, or any multi-client conversation pattern, Messages isn’t the right tool. A custom-built app with a community pattern is.
Threaded discussion or topic-based channels. Messages is a single thread per client. If you want Slack-style channels inside your Portal, that’s a custom build.
Messages and custom-built apps are complementary. A common pattern:
The custom app handles the workflow (a project tracker, a request portal, a check-in app)
Messages handles the conversation that emerges from the workflow
A request portal built with the app builder captures structured requests. The follow-up conversation about a specific request lives in Messages. You don’t need to rebuild messaging inside your custom app — just point users at Messages when they need to chat.