Email and Discord, one queue
Shared inboxes and Discord threads land in one list, each with an owner, a status and its history.
Product
Customers email you and ask in your Discord. Every conversation lands in the same place, with an owner, a clock and the full context.
Shared inboxes and Discord threads land in one list, each with an owner, a status and its history.
Response targets per tier. Only the person who asked restarts the clock.
Switch to a note, @mention a teammate, and keep the context in the thread.
Slice the queue by channel, status or owner, then act on many at once.
Your own statuses, labels and fields, like product area or impact.
FAQ
Email and Discord today: shared inboxes like help@ and billing@, and Discord forum and public threads. Slack, Microsoft Teams and live chat are next on the roadmap.
It answers from your docs and past threads, shows the sources it used, and hands anything it can't answer confidently to a teammate with a summary. You choose which channels and tiers it may reply to, and whether replies need a review first.
Each thread has a requester: the person who opened it. Other people can chime in and you'll see their messages, but only the requester's replies restart the response clock, so one busy thread doesn't skew your numbers.
Yes. Assign threads, leave internal notes with @mentions, filter by owner, and run bulk actions. Every workspace has its own members, statuses, labels and fields.
A few minutes. Forward your support address, add the bot to your Discord server, and existing conversations are imported, so your team starts with a full queue instead of an empty one.
Connect your support inbox and your Discord server, and let the AI agent take the first reply today.