# Inbox and follow-up automation

> Manage conversations and personal email outreach with researched prospects, reviewed drips, Billing and reply handoffs.

Human entry point: /dashboard/products

## What an authorized agent can help with
- Read authorized conversations and follow-up work
- Draft a reply or automation for review
- Choose the starting point in New automation: CRM & pipeline, Email outreach, or Inbox. See [automation choices](https://api.agents.datagran.io/v1/inbox/docs.md#choose-an-automation) for supported triggers and channels
- In Home, choose Automations under Inbox, then New automation → Email outreach for Audience, Message and Review. Automations also remains available inside Inbox
- Choose New automation → CRM & pipeline → Personal email sequence for Home pipeline stages or connected Datagran CRM People stages. Stage changes queue a contact; review a Billing estimate before preparing emails and approve the drafts before sending
- Gather the [outreach input checklist](https://api.agents.datagran.io/v1/inbox/docs.md#gather-the-inputs): workspace, audience, roles, offer, voice, approved claims, optional sample, sender, timing, budgets, batch size, tracking and reply handling
- Help review sourced companies, decision-makers, candidate work addresses and ZeroBounce verification before approving recipients
- Help shape Sonnet's personal angle and distinct messages from approved claims, tone and writing samples; unsupported facts need more research
- Request and review additional batches of 10, 20, 50 or 100 people through the console while existing work continues
- Inspect valid contacted people, actual agent work, drip progress, individual email activity, reply intent and campaign costs

## Limits and checks
- Inbox owns message scheduling, sending and flow control
- Email outreach is enabled across tenants; each project still needs Inbox access, administrator approval, a verified mailbox with send/receive permissions and Billing capacity
- Native CRM stage triggers require the project Inbox crm.read grant and credential. Salesforce changes can use mapped Home pipeline stages. Other CRM contact integrations do not automatically provide stage triggers
- Enable stage trigger starts enrollment only. Each contact enters once after activation; existing contacts are not imported. Native CRM checks are periodic. An observed stage exit skips a waiting contact, but does not cancel a prepared batch or active drip
- Basic automatic follow-ups send WhatsApp or SMS. Their manual email and call options create team tasks. No-reply follow-ups also require selected Home pipeline stages
- Recipient consent, channel readiness and tenant policy must be checked before sending
- The Inbox tool gateway is trusted-server only; public documentation is not direct model access
- An automation draft is not an active follow-up policy
- Email outreach launch is a separately reviewed console workflow, not an extra gateway capability or delegated Home read tool
- Follow the [readiness checks](https://api.agents.datagran.io/v1/inbox/docs.md#check-readiness-and-resolve-blockers): Home Product access and Product roles, Integrations → Email, Usage & billing, current estimates and recipient review
- Save first if needed, then use Send from → Connect Gmail or Outlook in the saved automation. Return after connecting, refresh accounts, select the ready project account and choose Use this email. Research stays in place. Review the preparation estimate to finish missing emails; fresh valid checks and saved drafts are reused. Attaching an account starts no paid work or send and cannot replace an existing sender. Save email automation saves setup; Start research for N people begins paid work; Approve N people and queue emails authorizes sending
- Approve each batch's recipients, copy, 5–20 distinct email steps, timing and budget; new batches do not restart completed work
- Prospect discovery can send the first step separately to approved valid alternate addresses; later steps use the primary address. CRM preparation uses the single saved email in its reviewed contact snapshot. Each email has separate tracking
- Open and click detection can include automated activity; neither proves human reading or buying intent, and acceptance does not prove delivery
- Inbox contact cards can link a CRM person and add phone, email, role, notes and extra fields; no accessible CRM shows setup choices with Datagran CRM first
- Calling requires the current CRM phone, a matched Home customer and project lead, a ready calling connection, operator readiness, Billing and contact permission
- Every reply pauses the drip; high intent or uncertainty goes to Inbox, rejection stops outreach and opt-out suppresses the person and all addresses
- Routine AI answers need an approved paid allowance and do not resume the drip; continuation needs a fresh review of replies and remaining steps
- Research, verification, drafts, revisions and reply reviews use current Billing quotes and actual usage; shared verifier credit waits are uncharged and never buy credits automatically

## Related surfaces
- [crm](/docs/products/crm.md)
- [connections](/docs/products/connections.md)
- [groovy](/docs/products/groovy.md)
- [voice-agents](/docs/products/voice-agents.md)

## Product-owned discovery to verify
Home does not check whether these external URLs are deployed. Fetch each anonymously and require HTTP 200 with the expected content type before relying on it; any non-200 response, including 403, 404 or a redirect, means use the authorized product UI and report machine discovery unavailable.
- [inbox_index](https://api.agents.datagran.io/v1/inbox/llms.txt) (text/plain)
- [inbox_agent_guide](https://api.agents.datagran.io/v1/inbox/agent.txt) (text/plain)
- [inbox_setup_guide](https://api.agents.datagran.io/v1/inbox/docs.md) (text/markdown)
- [inbox_openapi](https://api.agents.datagran.io/v1/inbox/openapi.json) (application/json)
- [inbox_catalog](https://api.agents.datagran.io/v1/inbox/agent-resources.json) (application/json)

For live tenant access, use authenticated `GET /api/platform/agent-workspaces`, `GET /api/platform/agent-catalog?tenant_id={tenant_id}` and `GET /api/platform/project-status?tenant_id={tenant_id}&project_id={project_id}` in that order. Check product-specific readiness before acting. These public docs are not an execution grant.