Use cases by operating context
Cold outreach rules, platform terms, language, and buyer expectations differ by market. Start with the operator who owns the decision, then configure evidence and approval boundaries for the applicable region.
Test a narrow market thesis with explicit firmographic and technographic filters. Review a small sample, identify why each account fits, and keep outreach manual while the ICP changes. A hiring event or technology signal can suggest relevance, but it does not prove private buying intent.
Require provenance, source timing, role relevance, identity confidence, and suppression checks before drafting. Managers own working hours, pacing, authentication, reply routing, and stop conditions. Personalization does not guarantee a reply, and automation does not remove channel obligations.
Map each source, agent runtime, API key, export, CRM destination, log, retention period, and deletion path. Prefer documented APIs where available. Browser automation may be fragile or restricted, so review current provider terms and design a visible pause when an interface changes.
Isolate each client’s brief, credentials, suppression records, evidence, templates, and reports. Document authorization and the person who approves external action. Reports should distinguish researched, accepted, sent, delivered, replied, bounced, and opted-out records instead of presenting activity as outcome.
Install the skill, configure only approved connections, and inspect a small first result before enabling exports or any external action.
npx -y @okki-global/okki-go-taroball