Documentation | ConversationArc

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:

The canonical public marketing site is https://conversationarc.com. The signed-in product UI currently remains at https://correspond.outliyr.com. This repository does not configure app.conversationarc.com, so customers should not be directed there. 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.

Provider approval is not implied by product setup. External Instagram tenants cannot use production delivery until Meta grants the required app access. 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 code-truth review: July 18, 2026.