Human-reviewed sales engagement

Research the account. Draft the email. Keep the send decision human.

Yesware gives your AI agent a disciplined path from an ICP brief to cited account context and a reviewable cold-email draft. Unknown fields stay unknown, engagement signals are treated as clues rather than intent, and outreach never bypasses approval.

See the four states
npx -y @okki-global/okki-go-taroball
Sample taskPrepare five relevant accounts for reviewEvidence attached · send disabled
AI agent preparing evidence-led cold outreach

Four-state runbook

Copy is not install. A result is not approval.

  1. 01 Copynpx -y @okki-global/okki-go-taroball

    Success means the exact command reached your clipboard.

  2. 02 Run

    Execute it in a supported terminal. Read the package prompt and completion output before proceeding.

  3. 03 Configure

    Connect only approved data services, keep API keys in environment secrets, and define ICP exclusions plus suppression rules.

  4. 04 First result

    Test known accounts. Review entity identity, source recency, role relevance, unverifiable claims, and the proposed email before any send action.

Capabilities

A compact workflow for careful outbound

01

Account research

Apply firmographic criteria and explicit exclusions, then preserve domains, observation dates, source context, and unresolved fields.

02

Contact verification

Separate role relevance from address validity. Treat provider matches, hard-bounce risk, and current employment as distinct checks.

03

Message preparation

Draft from approved evidence without inventing familiarity, urgency, customer status, or private intent. Keep opt-out language visible.

04

Sequence review

Inspect cadence, suppression, SPF/DKIM/DMARC readiness, regional policy, and sender reputation before an operator enables outreach.

Data and security ledger

Inspect the behavior you depend on

Data sources

Config-dependent. Record each connected provider, its permitted use, field provenance, refresh behavior, and fallback order.

API keys

Operator-controlled. Use minimum scope and a secret store. Never place credentials in prompts, screenshots, repositories, or exports.

Runtime behavior

Verify locally. Review requested permissions, outbound connections, rate limits, retries, logs, and output destinations.

Retention and deletion

Policy-dependent. Define access, correction, suppression, retention, revocation, and deletion before production use.

Install FAQ

Know what happens after copy

Does the copy button install anything?

No. It only copies the exact npx command. You must run it in your terminal and inspect the installer output.

Does a returned contact mean the address is safe to email?

No. Identity, current role, address verification, suppression status, relevance, consent requirements, and regional rules need separate review.

Will the agent automatically send cold email?

No automatic-send claim is made. Keep research, drafting, approval, and sending as distinct states with a human-in-the-loop gate.

How should credentials be handled?

Store keys in runtime secrets with minimum scope, test with non-production access where possible, rotate exposed credentials, and revoke them when the connection is removed.

npx -y @okki-global/okki-go-taroball