Lead Inbox & Replies
The Lead Inbox (/inbox) is where outbound meets inbound — approve AI drafts before they send, read and reply to lead responses, and action follow-up sequence steps due today. Everything runs in a split-pane workspace so you can move fast without losing context.
What it is
Lead Inbox consolidates three daily workflows into one page with tabs:
| Tab | Label in app | Purpose |
|---|---|---|
| Approvals | Pending | Review, edit, approve, or reject AI-generated email drafts |
| Replies | Replies | Leads who replied to your outreach — read and respond |
| Follow-ups | Follow-ups | Active sequence steps due today |
Tab counts update live as drafts queue, replies arrive, and follow-ups become due.
You can also approve from the dedicated Approvals page or lead detail — Inbox is the unified daily driver.
Who uses it
| Role | Typical use |
|---|---|
| Rep | Morning approve pass, reply handling, send due follow-ups |
| Admin / Owner | Quality spot-check on drafts before they leave the org |
Approvals tab (Pending)
The first tab — labeled Pending in the UI — is your approvals queue.
Each item is a pending outreach draft tied to a lead:
- Draft type badge: First Touch, Reply, Sequence, or Follow-up
- Lead name, company, and scores in the list
- Split view: draft list on the left, composer on the right
Approve a draft
- Open Lead Inbox → Pending tab (default).
- Select a draft from the list.
- Review subject and body; edit inline if needed.
- Optional: use Rewrite with Claude presets (shorter, formal, direct CTA, friendlier) or custom instruction.
- Preview desktop/mobile rendering.
- Click Approve & Send.
Email sends from your configured org domain with signature appended. Status updates and the next draft auto-selects.
Reject a draft
Click Reject — draft is discarded; lead returns for re-draft or manual handling depending on pipeline state.
Batch approve
On Pending, multi-select drafts and Approve selected to send in batch (use when drafts need minimal edits).
Dev email redirect
In development, sends may redirect to a dev inbox — the composer shows → dev redirect on the To line.
Replies tab
Shows email_events with event_type = replied, newest first.
Each row:
- Lead name and company
- Reply preview snippet
- Timestamp
Select a reply to read the full message in the detail pane and jump to the lead’s Conversation thread. Reply from lead detail or compose where integrated — replies track in the thread and cancel active follow-up sequences when appropriate.
Follow-ups tab
Lists leads on active sequences where today’s date matches a sequence step due date and the step has not yet sent.
Each item shows:
- Lead identity and scores
- Current sequence step (e.g. Step 2 of 3)
- Step timing from sequence definition (Day 3, Day 7, etc.)
Action follow-ups by approving the generated follow-up draft (often appears in Pending first) or managing the lead on detail.
Split-pane workflow
- List pane — tabs + searchable queue
- Detail pane — composer (Pending), reply reader (Replies), or follow-up context (Follow-ups)
- Mobile — toggles between list and detail views
URL supports ?tab=pending|replies|follow-ups and ?lead=[id] to deep-link a specific lead’s pending draft.
Step-by-step: morning inbox routine
- Open Lead Inbox.
- Pending — approve or rewrite first-touch and follow-up drafts due to go out.
- Replies — respond to overnight replies (highest intent).
- Follow-ups — confirm sequence steps due today are approved in Pending or sent.
- Check My Work for assigned tasks not tied to drafts.
Step-by-step: handle a reply
- Switch to Replies.
- Select the reply — read full body in detail pane.
- Click through to lead detail for full conversation history and approach angle.
- Compose reply (or approve AI reply draft if queued in Pending).
- Sent reply logs in thread; follow-up sequence cancels if lead engaged.
Why this matters
- No missed replies — every reply event surfaces in Replies
- Human gate on send — Pending tab enforces approval before any email leaves
- Full context — scores and draft type visible while approving
- Brand consistency — org email signature applied on send
- Engagement tracking — opens/clicks inform reachability on the lead record
Tips
- Pending = Approvals — same workflow as the Approvals page, optimized for send-day throughput.
- Rewrite before reject — one Claude rewrite often fixes tone without re-running the pipeline.
- Batch approve homogenous drafts — e.g. sequence step going to 20 similar leads.
- Follow-ups due ≠ Pending empty — drafts may still need generation; run pipeline on leads if Pending is unexpectedly quiet.
- Deep link with
?tab=replies— share with teammates when handing off a hot reply.
Related articles
- Approvals & Sending — approval philosophy and alternate entry points
- Managing Leads — lead detail conversation and comments
- Getting Started — end-to-end outbound workflow
- My Work — assigned tasks separate from inbox drafts