Novu Connect - Ship agents where your users already work
by•
Novu Connect lets any AI agent have two-way conversations across Slack, Teams, WhatsApp, Telegram, and email without building each channel integration yourself. Bring your own agent logic, model, or code. Novu handles the communication layer: delivery, identity resolution, threading, routing, and channel-specific formatting, so your agent can reach users where they already work.
Replies
daily.dev
Novu
@nimrodkramer Thanks for jumping by to support! The team at Daily been a huge inspiration for what we've done over the years.
Congrats! Curious how does Novu Connect handle context continuity if the human switches mid-conversation from one channel to another
Novu
@crystalmei We modeled our product to have the "Conversation" entity agnostic to channels, and can also support multiple channels. So a conversation can start in one channel, and continue in another!
Congrats on the launch. The “agent-to-human last mile” framing is strong, especially because teams already live in Slack, Teams, WhatsApp, and email. The part I’d love to understand better is the governance layer: when the same user talks to an agent across multiple channels, how do you handle identity mapping, audit logs, and permission boundaries so the agent has enough context without exposing too much history to every operator?
Novu
@studentzuo Novu Owns the channel credentials layer aswell, we offer components like <SlackConnectButton /> for you to use, and once a user adds an app to slack, we will store the slack credentials and user ids on each platform. Once a message arrives, we are able to map it to the user on your db ⚡
The bring-your-own-agent boundary is the part I’d test first for support/community workflows, because the communication layer can’t silently become the agent brain. I’d use this for an agent that follows up with members across Slack and email after a launch. If a teammate pauses or disables that agent, does Novu Connect stop outbound channel delivery immediately while preserving the existing thread history?
Novu
@hazy0 Yes, history will still be there, unless you will explicitly remove it. Bring your own agent was key to us, the field evolves so fast, and we have to give developer the flexibility 💪
That split makes sense: stopping delivery immediately while keeping the thread gives teams a clean incident switch without losing customer context. The next thing I’d look for is a visible audit event when an agent is paused, so the support team can tell why follow-ups stopped.
Novu
@anusuya_bhuyan I don't think that dashboards are gone, but the interaction with them will change significantly. Conversation first.