Skip to content
NewSee how

Triage replies in the Inbox (Unibox)

Work every reply from one shared inbox: filter by tab, read the row status pills, and understand each contact's journey status.

  1. Open the Inbox

    Every reply across all your mailboxes and campaigns lands in one shared Inbox. Open it from the main nav.

  2. Filter with tabs

    Switch between All, Unread, Replies, Completed, Active, Bounced, and Failed to focus on what needs attention.

    Filter with tabs
  3. Spot what needs you

    The Needs Approval tab carries an amber badge whenever drafts are waiting for review. Unread surfaces replies you haven't opened yet.

  4. Read the row status pill

    Each thread shows a pill summarizing that contact's journey: Active (still in the sequence: this includes paused contacts), or Completed with a reason.

  5. Open a thread

    Click a row to read the full conversation, with sender, campaign, and goal context in view.

  6. Check the journey footer

    A terminal or paused thread shows a journey card at the bottom of the conversation: Goal reached, Bounced, Unsubscribed, or Paused, along with the reason.

    Check the journey footer
  7. Act and move on

    Reply, then let filtering carry you to the next thread. Completed and unsubscribed contacts drop out of the active flow automatically: no cleanup needed on your end.

Pro tips

  • Triage from the Replies tab

    It isolates threads where a contact actually wrote back, cutting out the rest of the sending noise.

  • Paused still shows as Active

    A paused contact's row pill still reads Active: paused means temporarily not sending, not finished. Check the conversation's journey footer for the real reason.

  • Watch Bounced and Failed as an early warning

    A spike in either tab is a signal to check sender health and cleaning before it drags down your reputation.

  • 'Goal reached' is your win

    Completed · Goal reached means the campaign goal (a meeting or reply, for example) fired for that contact. Those are the ones to hand to sales.

Frequently asked questions

What is the Unibox?

One shared Inbox that aggregates replies across every connected mailbox and campaign, so you triage from a single place.

What do the tabs filter?

All, Needs Approval, Unread, Replies, Completed, Active, Bounced, and Failed: each narrows the thread list to that state.

What does the 'Active' pill mean?

The contact is still in the sequence. Paused contacts also show Active: they're in flight, just not sending right now.

What are the 'Completed · …' pills?

A contact's journey ended: Goal reached (a win), Bounced (undeliverable), or Unsubscribed (opted out).

Why does a thread show a Journey card at the bottom?

It marks a terminal or paused journey (Goal reached, Bounced, Unsubscribed, or Paused) with the reason and time.

Do completed or unsubscribed contacts keep getting emails?

No: those journeys have ended; the sequence stops for them automatically.

Where do out-of-office replies show up?

OOO is a thread status in the Inbox. Handling and auto-resume are covered in the out-of-office tutorial.

Inbox & Replies

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.