Use cases
The same automation pattern creates different risks for an SDR, founder, agency operator, or RevOps owner. Start from the decision and approval boundary.
Build a bounded prospect list, verify role relevance, draft a connection note, and route responses to a person. Managers should define daily limits, message approval, negative-reply handling, and account protection before a campaign is enabled.
Choose this when: representatives need repeatable preparation while retaining ownership of relevance and replies.
Translate a narrow market thesis into a small test instead of scaling a vague audience. Keep founder voice intact, record why each person belongs, and stop follow-ups as soon as the context changes or the recipient declines.
Choose this when: learning quality matters more than list volume.
Separate client accounts, credentials, suppression data, templates, and approval records. Confirm who controls source selection, message sign-off, sending limits, reply ownership, retention, and deletion before accepting a brief.
Choose this when: operators manage multiple policies and sender identities.
Inspect schema mappings, secret storage, retries, rate limits, campaign state transitions, exports, audit events, and failure recovery. Use test identities and a sandboxed destination before touching a production CRM.
Choose this when: reproducibility and governance are first-class requirements.
| Question | SDR | Founder | Agency | RevOps |
|---|---|---|---|---|
| Who approves the audience? | Manager | Founder | Client owner | Policy owner |
| Who approves messages? | Rep or manager | Founder | Named client reviewer | Business owner |
| Critical stop event | Reply or opt-out | Context change | Client instruction | Invalid state |
| Primary audit artifact | Review queue | Learning log | Client ledger | Event log |
Check LinkedIn account conditions, regional communications rules, email authentication, sender reputation, consent context, suppression obligations, and connected-provider terms for your actual use. This guide does not certify a campaign as compliant or safe.
Copy the installer, run it in a controlled environment, and review a small known cohort before expanding scope.
npx -y @okki-global/okki-go-taroball