Memory
Knows what's happened with this contact
Reads Account research, prior Activities, sales-config snapshot, and the cohort tags already on this Contact — so the draft references the right context, not a generic template.
Powered by the Outreach Writer on the Vertiqa OS
Never lose a deal because you forgot to follow up.
Vertiqa's Outreach Writer drafts the three follow-up emails and LinkedIn notes that close deals — Day 0, Day 4, Day 9 — and queues them in an Approval Inbox so nothing goes out without your review.
Shipped in v1.37 Sales Loop Agents Phase A
The spine of every Vertiqa agent
Every agent runs inside the same system of record — bounded by what it remembers, what it is allowed to do, and what gets written down.
Approval
Stages every draft in an Approval Inbox
Email 1 lands in EmailComposer with a sender selector, three-email preview, and approve / edit / reject controls. Nothing is sent until you click Send.
Audit
Writes evidence on every decision
Sequence step, variant key, artifact reference, sender domain, and message id are written to Contact Activity. Day 4 and Day 9 follow-up tasks are created on Kernel send-acknowledgement.
What it does
Four concrete behaviors, every one traceable to a shipped v1.37 Sales Loop Agents Phase A capability — no roadmap features, no aspirational claims.
Decides whether this contact is ready for outreach
Vertiqa's Outreach Writer dispatches only when the contact's Account research is approved and the contact is not flagged do-not-contact, has not been recently messaged, and clears the deterministic eligibility checks — otherwise it returns a refusal artifact you can act on, not a ready draft.
Drafts three emails, two LinkedIn notes, and a Notes-for-Founder pack
Vertiqa's Outreach Writer produces three plain-text emails (Day 0, Day 4, Day 9), a LinkedIn connect note, a LinkedIn follow-up note, and a structured Notes-for-Founder set with send blockers, positioning reminders, a demo scenario, disqualification listen-fors, and subject-line variants.
Refuses to ship anything that violates a guardrail
Vertiqa's Outreach Writer runs a deterministic safety scan against forbidden tokens, required guardrails, and unsupported claim themes after generation — if anything fails, it writes a refusal artifact rather than a ready draft, so a borderline message never lands in the Approval Inbox as if it were ready.
Hands you Email 1 in EmailComposer, then closes the loop on Day 4 and Day 9
Vertiqa's Outreach Writer stages the approved Email 1 in EmailComposer with a sender-domain selector. When you click Send, Contact Activity is written with sequence step, variant key, artifact reference, sender domain, and message id — and Kernel acknowledgement creates Day 4 and Day 9 manual follow-up tasks so the next touch is never lost.
What this agent will not do
- Never sends an email without your review. Email 1 always stages in EmailComposer; Day 4 and Day 9 are manual follow-up tasks, not auto-sends.
- Refuses to draft when research is missing, pending, or rejected, when a contact is marked do-not-contact, or when deterministic safety checks fail. Refusals are returned as artifacts you can read, not silently dropped.
- Phase A is a manual-send compliance boundary. It does not run autonomous campaigns, manage suppression lists, or make your sending CAN-SPAM-compliant on its own — those are on the Sales Loop Phase B roadmap, not in this surface today.
Works with the kernels you already use
The Outreach Writer reads and writes through the same Kernel surfaces your team uses — no separate vendor system, no shadow data store.
CRM Contacts and Accounts
Eligibility and personalization read from the same records your team works in.
Approval Inbox
Three-email preview tabs, sender-domain selector, approve / edit / reject controls.
EmailComposer
Email 1 stages here with a sender-domain selector; Send is yours.
Contact Activity timelines
Every approved send writes sequence step, variant key, artifact reference, sender domain, and message id.
Agent Library
The `outreach_writer` run is visible on the Library page like every other Vertiqa agent.
Gmail / Outlook send (where configured)
Manual Send from EmailComposer — never an automated dispatch.
Frequently asked
Where is my data stored?
Inside the same Vertiqa Kernel that powers every other agent and surface in your org. Outreach drafts, research artifacts, and approval decisions live in your organization's Kernel — not in a separate vendor system. Tenant isolation, org scoping, and permission gates are tested at the endpoint level for every Phase A route.
What gets stored when the agent runs?
The agent writes one outreach artifact per run (three emails + two LinkedIn notes + Notes-for-Founder), plus timeline and audit evidence on every decision. When Email 1 is sent, Contact Activity records the sequence step, variant key, artifact reference, sender domain, and message id. Refusals are stored as refusal artifacts, not silently dropped.
What happens if I reject a draft?
Rejection is a first-class outcome in the Approval Inbox. The artifact is marked rejected, nothing is sent, no Activity is written for the unsent email, and the decision is captured in timeline / audit evidence. You can also edit before approving — the edit is what stages in EmailComposer.
Can I edit the email before it sends?
Yes. The Approval Inbox supports approve, edit, and reject. Edits made there are what land in EmailComposer; the manual Send from EmailComposer is what writes Contact Activity. The agent never sends on your behalf.
Which verticals is this built for?
Phase A is built for relationship-driven service businesses where every prospect contact matters. The current pack vocabulary, sales-config snapshot, and ICP scoring fit life-insurance practices, travel advisors, and senior-living advisors particularly well — see /life-insurance, /travel-advisors, and /senior-living-advisors for vertical context.
Built for relationship-driven service businesses
The Outreach Writer ships with pack vocabulary, sales-config snapshot, and ICP scoring tuned for these verticals first.
Never lose a deal because you forgot to follow up.
Book a demo to see the Approval Inbox, Day 0 / Day 4 / Day 9 drafting, and the manual-send compliance boundary on a real org.