ConversationArc customer documentation
ConversationArc is the customer-facing product name. This documentation is the source of truth for the current design-partner release and assumes no private operator access or instructions.
Start here:
- Capabilities and release boundaries
- Workspace and first-workflow setup
- Troubleshooting and support
- REST API and MCP reference
The canonical public marketing site is https://conversationarc.com, and the signed-in product UI is https://app.conversationarc.com. The legacy https://correspond.outliyr.com host remains a supported alias. A workspace invitation is required while public signup remains disabled.
What a new customer can complete
With a valid invitation and a provider connection that the ConversationArc Meta app is allowed to serve, an owner can:
- create an account and workspace, enable two-factor authentication, and invite teammates;
- create a resource or hosted waitlist;
- connect an Instagram professional account through OAuth;
- create a paused workflow, preview its copy, validate it, and activate it;
- inspect delivery activity, usage, audit history, and privacy-safe diagnostics;
- create a tenant-scoped API/MCP key for an agent; and
- export or delete customer data through the documented privacy controls.
Meta has approved instagram_business_basic, instagram_business_manage_comments, and instagram_business_manage_messages for this app. That approval is not universal workspace-delivery proof: each invited workspace still needs an eligible professional account, its own OAuth connection, and live connection and delivery evidence before relying on production delivery. YouTube and Telegram have narrower adapter foundations described in the capability matrix; neither should be sold as an Instagram-equivalent comment-to-DM flow.
Documentation contract
- Product capabilities are stated separately from provider access.
- Every REST example uses a personal tenant-scoped key, never the platform operator token.
- Destructive actions name their exact-confirmation field.
- Secrets, raw customer data, and provider tokens never belong in support reports.
- If the UI and this documentation disagree, pause the workflow and report the discrepancy with an opaque correlation ID.
Last review of the host and Instagram approval sections: September 12, 2026.