Workflow · Alpha
Design one reusable sequence together, then run outreach as a controlled mode.
Understand address confidence, representative previews, user-owned sending setup, and manual or scheduled Email Outreach delivery.
Separate qualification, contact readiness, and sending
Email availability
Qualification comes first. Your agent can then collect a business email, direct ownership sources, and optional technical signals. Nothing is sent in this step.
Email Outreach
A separate operational mode in the same acquisition loop: user-owned sending setup, reusable-sequence campaigns, one representative preview, and content-free receipts. The coding agent can guide the design, while Dashboard confirmations control activation and sending.
Manual in the Dashboard
Open an ICP Profile, choose Edit, select an Email policy, confirm the alpha notice, and save. Coding agents cannot turn Email on through MCP.
Run the workflow in six stages
Choose whether to find email evidence during research, save first and enrich later, or keep Email off. Contact uncertainty never blocks a qualified lead from the List.
Open direct ownership sources first. Once an email is available, LeadCue can use it; technical checks remain supporting evidence and do not need to become a user decision.
LeadCue sends available addresses within the mailbox operating limit and updates future sending from real provider outcomes such as replies, bounces, complaints, and opt-outs.
Templates contain short names such as {{productName}}. Every name has a separate source and exact requirements; your coding agent executes those requirements and never guesses from the name. It keeps revising until you confirm the exact sequence.
Use Google Workspace/Gmail or Microsoft 365/Outlook, then review the scope, rules, and one representative real preview—not every rendered message. Before any draft or send, sync Sent activity, replies, and the exact connected provider account and mailbox; a mismatch blocks the run. Aliases never create extra mailbox capacity.
The default next step creates mailbox drafts and stops. Sending those drafts is a later confirmation. Automatic sending remains a separate choice: confirm a schedule and create a recurring task without an immediate run.
Use the operating controls as hard boundaries
A search snippet is not ownership. public_exact requires an opened direct source page.
DNS and SMTP checks can run through the bundled verify_email tool, especially for inferred addresses. If it is unavailable, research and saving continue. SMTP acceptance never means Delivered.
Sent means the provider accepted the API request. A real hard bounce blocks and suppresses that address; a soft bounce limits future use; replies stop follow-ups. Sender authentication failures affect sender health, not recipient validity.
Mailbox sync records the live provider, provider account email, and mailbox email without storing message content. LeadCue compares that observation with the configured sender graph; a mismatch or stale identity blocks capacity use, draft creation, and sending until the correct connection is synced.
You can shape and confirm the reusable sequence before connecting a mailbox. LeadCue records setup receipts only—not passwords, OAuth tokens, DNS secrets, or purchase pricing.
{{variableName}} is defined once from saved Lead evidence and can be reused by several emails. Actions produce a named value once, before the first email that needs it; later emails reuse that same name.
New senders begin at 10 real cold emails/day and grow about 25% after each healthy sending day, up to 40/day. Bounce, provider deferral, and complaint signals can hold, cool, or pause a mailbox; open rate does not. Manual, scheduled, and other mailbox activity share the same sender budget; provider maxima are not recommended operating limits.
Manual mail, other tools, campaigns, follow-ups, and every From alias all consume the same rolling mailbox allowance.
Variables are defined once for the Sequence. Actions appear only when a new value must be generated. If evidence is missing, a timeline action fails, or an exact template cannot be rendered, LeadCue validates a content-free receipt against the prepared recipient and step, skips that item, and continues the unchanged Campaign without asking you to approve it again.
One hard bounce blocks that address immediately but does not freeze a whole small-sample mailbox. Two distinct hard bounces, or a 2–3% rate after 50 sends, hold volume; 3% or more cools the daily limit. A campaign can still pause at four distinct hard bounces above 3%.
A ready sender also needs a recent recipient-side check: SPF, DKIM, and DMARC pass, and the signing domain matches the sending domain. Connecting a mailbox still does not approve a campaign.
After a mailbox hold, you review the content-free bounce, complaint, and authentication evidence. Recovery restarts at 10 real cold emails/day and requires a fresh Sent and reply sync before the next run.