When should internal support happen in public, and when should it be private? Here’s how to think about it and how Ravenna supports both.
When a teammate needs help, where should they go?Should they post in a shared support channel like #ask-it?
Or should they send a direct message to someone they know can help?The answer depends on the situation and how your team prefers to work.
This guide breaks down the pros and cons of each approach and shows how Ravenna makes it easier to support both.
Private requests in Ravenna don’t go to an agent’s personal DMs.
Instead, teammates message the Ravenna bot. To the requester, it feels like a one-on-one conversation. For agents, it keeps personal inboxes clear and ensures all requests flow into the right workspace queue.
✅ Benefits
Low barrier to entry
Messaging the bot feels just as simple as DM’ing a person.
Feels safe
Great for sensitive or awkward issues like HR, hardware, or access.
Agent focus
Agents aren’t interrupted in their own DMs—all requests appear in triage channels or the queue.
Organized flow
Even private conversations stay trackable in the same system as public ones.
⚠️ Tradeoffs
Less visibility
The request isn’t visible to the wider team unless surfaced.
Easy to overlook
Without clear processes, private messages can still be missed.
Perception of one-to-one
Some teammates may assume a DM guarantees instant attention.
Default to public, allow private when it makes senseUse public channels as your default for transparency, knowledge sharing, and balancing support.But leave room for private requests, people need a clear path for situations where privacy or comfort matters.With Ravenna, you can support both approaches without losing visibility, dropping requests, or overloading your team.If you’d like to see Ravenna in action, get started with our quickstart guide.