Use cases by operating context
A map is not a coverage claim. It is a planning surface for deciding which rules, sources, review owners, and outreach channels apply before a real person enters a workflow.
Define a narrow ICP, document sources, and separate US and Canadian obligations rather than treating the region as one rule set. Check consent, suppression, state or provincial requirements, sender identity, and channel terms. A public business profile does not automatically authorize every use or message.
Record purpose, source, role relevance, lawful-basis assessment where applicable, and a clear objection path. Review PECR and UK GDPR obligations with qualified counsel for the actual channel and recipient type. Generated relevance is not a substitute for necessity, transparency, or human judgment.
A single European playbook can hide national differences. Configure geography, language, source restrictions, retention, deletion, and who answers access or objection requests. Avoid sensitive inference and broad scraping. Keep research, drafting, export, and sending as independently authorized states.
Check applicable anti-spam and privacy requirements, inferred or express consent rules, sender identification, unsubscribe handling, and source provenance. A LinkedIn action and an email follow-up may carry different constraints. Preserve evidence of review rather than assuming a workflow is compliant by design.
Start with a small authorized sample. Verify current laws, contracts, platform terms, source provenance, identity confidence, suppression, and the person who can approve external action.
npx -y @okki-global/okki-go-taroball