Product guide
How Coldvio works
Understand the workspace, the customer voice layer, reviewed execution, and where CLI and MCP fit before you automate a workflow.
The operating model
Coldvio brings customer context, relationship data, campaigns, drafts, and trend signals into one workspace. Your voice profile guides generation; CRM and campaign state provide context; approval boundaries keep external actions reviewable.
A reliable Coldvio workflow
- Read the current state and relevant source material.
- Prepare a proposal or draft in the customer's voice.
- Review exact recipients, identifiers, claims, and final text.
- Confirm one bounded operation when a change or credit spend is intended.
- Read the resulting state and report what changed.
Dashboard, CLI, MCP, and API
Use the dashboard for visual exploration and account settings. Use the CLI for explicit terminal workflows and scripts. Use MCP when Claude, Codex, Copilot, or another agent should discover Coldvio tools conversationally. Build directly on the Agent API only when you own the client and its customer approval experience.
What an agent cannot do
- No generic execute endpoint.
- No direct send or publish tool.
- Drafting never means sending.
- Foreign workspace identifiers never grant access.
- Consequential operations require a short-lived, one-use server intent bound to the exact payload.