Skip to main content
Back to products
Service

Shared Inbox for teams that need more than a basic tool

Repzo’s shared inbox turns disconnected conversations into managed work with policy-driven routing, real-time collaboration, and CRM context baked in.

Support, sales, and success teams that need one queue for email and future messaging channels.

Inbox policies for support, sales, and success queues

Identity resolution to existing CRM contacts

One-click ticket creation from active conversations

Shared Inbox
All4
Unassigned
Mine
Snoozed
Inboxes
Support
Sales
Sarah Chen2m

Order #4821 delivery issue

Hi, my order hasn't arrived yet and it's been...

James Miller15m

Question about enterprise pricing

We're evaluating your platform for our team of...

Repzo Billing1h

Re: Subscription renewal

Your subscription has been renewed successfully.

Alex Torres3h

Bug report: Dashboard widget

The revenue chart shows incorrect data for Q2...

SC

Order #4821 delivery issue

VIP

sarah.chen@acme.com

Open
SC
Sarah Chen2m ago
Hi, my order #4821 hasn't arrived yet. The tracking shows it's been stuck in transit for 3 days. Can you help?
SLA: First reply due in 12m
I’m checking the carrier handoff now. I’ll confirm the latest scan and send you an updated ETA in a moment.
AutomationContact matched
Order
#4821
Priority
High
Reply to Sarah...

What this page is built around

Unify customer conversations across channels with routing, identity resolution, SLA enforcement, and ticket creation from one inbox.

Capabilities

Core workflows teams can run inside Shared Inbox

These pages are anchored in the actual product shape across the frontend routes, backend models, and documented workflows in this workspace.

Teams typically use shared inbox to:

  • Run support@ and success@ mailboxes with ownership rules
  • Manage pre-sales inquiries in a shared revenue queue
  • Convert inbox conversations into trackable support tickets

Route incoming conversations by inbox rules and assignment strategy

Keep agents aligned with real-time updates and shared visibility

Apply SLA policies inside the conversation workflow

Connect channel accounts without leaving the admin experience

Workflow

How teams typically move through shared inbox

1

Connect a mailbox or channel account to an inbox

2

Route and assign new conversations with the right policy

3

Resolve, escalate, or convert conversations into tickets without context switching

Related modules

Stronger when connected to the rest of the platform

Each feature page links back to adjacent workflows so search traffic lands on a real product ecosystem rather than an isolated marketing leaf.

Lead Management

Manage your entire lead lifecycle from first touch to conversion. Import from multiple sources, score leads, and convert qualified leads into deals with one click.

Explore module

Help Desk

Full-featured ticketing with SLA policies, escalation workflows, canned responses, and multi-channel support to keep your customers happy.

Explore module

Team Chat

Built-in messaging with channels, direct messages, and threaded conversations — so your team can collaborate without switching tools. Reactions, typing indicators, and instant delivery keep everyone in sync.

Explore module

FAQ

Questions teams ask before adopting Shared Inbox

Is this just an email viewer?

No. The inbox includes routing, identity resolution, SLA handling, and operational assignment rules.

Can conversations become tickets?

Yes. Agents can create linked tickets directly from a conversation when formal tracking is needed.

Can different teams run separate inboxes?

Yes. Each inbox can have its own type, default team, auto-assignment mode, and SLA policy.