01
AI reads the company
Every agent
AI crawls the site and writes the offer, the audience, the voice, and the brand. Website chat, card flows, and LinkedIn start from that.
Integrating Collected Customer Data from SMOC.AI
Integrating Collected Customer Data from SMOC.AI 
Simple guide showing how to connect SMOC customer and outcome data to your CRM, data warehouse, or custom systems.
Get your integration token
All SMOC data integrations authenticate with a private API key generated in Console — the same pattern as Zapier and MCP.
For the REST API:
- Go to Settings → Integrations → API in SMOC Console.
- Optionally name the key and set an expiry, then generate it and copy it immediately — it's shown only once, so store it somewhere secure.
- Issued keys are listed on that page. Revoke unused keys there.
For MCP:
- Go to Settings → Integrations → MCP in SMOC Console.
- Optionally name the key and set an expiry, then generate it and copy it immediately — it's shown only once, so store it somewhere secure.
- Issued keys are listed on that page. Revoke unused keys there.
Your key is tied to your company. Every request made with it is automatically scoped to your data — you only see contacts, companies, and analytics that belong to you.
Integration options
SMOC supports several ways to move data out of the platform:
- Zapier — no-code automation to 2,000+ apps with the New Contact trigger. Generate a key under Settings → Integrations → Zapier. See the Zapier eGuide.
- REST API — programmatic access for listing company contacts. Generate a key under Settings → Integrations → API. See the REST API eGuide and the REST v2 API reference.
- MCP — company-scoped access for AI clients such as Claude, Cursor, and VS Code. Keys are read-only by default; check Allow limited writes to update contacts, lists, and tags, and to send a text inbox reply. Generate a key under Settings → Integrations → MCP. See the MCP eGuide.
- Integration partners — contact SMOC for managed handoffs through partner connectors.
- Manual export — download CSV from the contacts section in Console when you need a one-off extract.
Using the REST API
Send your integration key on each request to SMOC public REST endpoints. Typical use cases include:
- Retrieving contacts and interaction history for CRM or data-warehouse sync.
- Routing outcomes into internal pipelines on a schedule.
- Connecting messaging workflows and outcome data to your stack.
All responses stay company-scoped — you never see another tenant's data.
For endpoint details and examples, follow the steps in this guide and the related eGuides at smoc.ai/eguides. For a product overview of all integration paths, see smoc.ai/integrations.
See also
- REST v2 API reference — every
POST /api/v2/{toolName}call - Connecting SMOC with the REST API
- Public Contacts API
- MCP for Claude, Cursor, and VS Code
Where AI runs
AI does the work. You review it.
Website chat, card flows, and LinkedIn share one system. AI does each job below. The line under the title says where that job runs.
02
AI plans your growth
Dashboard · Lead Strategy
Set your lead goal. AI simulates thousands of channel mixes, ranks them by efficiency, and shows the most cost-effective plan. Your data and constraints shape the math.
03
AI drafts the agent
Every agent · theme on web · list on LinkedIn
AI writes the flow. Theme runs on website chat and cards. Translation runs on every agent. AI finds the prospect list on LinkedIn.
04
AI runs the conversation
Path on every flow · web and LinkedIn split
Reinforcement learning on the flow path runs on every agent. Recommendations run on web. Right timing and reply reading run on LinkedIn.
05
AI gets better
Every agent
AI proposes a variant, uses your review on the next draft, and starts from an example that already works. You apply the change.
Related guides
Continue learning with these related guides
Stay close to the shift in AI sales
Get product updates and perspective on proactive AI agents, multichannel orchestration, and conversion—without the noise.
Weekly signal on proactive AI sales