Who provides first-line support to end clients?

You do. Your team handles usage questions, basic configuration, and onboarding. Our team handles deep infrastructure, channel connectivity, and AI worker issues through a direct partner channel.

How is the program billed?

Partner billing is a separate contract from standard plans — it accounts for the managed WhatsApp API access, the branded console, and partner-specific support. Full numbers are shared during the application conversation.

How long does the initial setup take?

Roughly 3 to 5 business days to deploy the branded console on your domain once the agreement is signed and your brand assets are ready.

How is client data isolated between workspaces?

Each workspace is its own scope. Conversations, catalogs, branches, AI Config, and Orders never cross accounts. Your admin surface sees aggregate usage; clients only see their own workspace.

What is NOT customizable in the program?

The underlying AI worker and Meta API integrations stay on our infrastructure and aren't swapped per partner. Workflow semantics (e.g. the 15-minute manual pause, the paid appointment validation pattern) are consistent so support, onboarding, and docs stay coherent.

Ship Interlinked under your brand,

What the partner tier includes

Everything you need to deliver Interlinked as if it were your own product — with honest scoping on what stays on our side.

Branded client console Your logo, colors, and custom domain on the panel your clients use daily. The Onboarding Wizard, CRM, Orders, and Calendar surfaces all inherit the branding.
Workspace scoping and data isolation Each client gets their own workspace. Conversations, catalogs, channels, and AI Config live inside that scope and never leak across accounts.
Per-workspace billing visibility Usage and message limits are tracked per workspace, so you can translate them into client-facing pricing however you bill.
Managed infrastructure WhatsApp Official API access, Meta app management, and the AI worker all stay on our side. You focus on customer relationships and rollout.

A short, selective program — not a self-serve signup.

How the rollout works

01

Apply to the program

Tell us about your clients, your sales motion, and the workflows you expect to run. We approve partners who can deliver the program responsibly.
02

Configure the branded environment

Once approved, we deploy a branded console on your domain. You decide the naming, visuals, and which of the nine Interlinked workflows you offer.
03

Onboard and operate

Use the Onboarding Wizard to bring clients live. Your team owns client relationships and first-line support; our team owns infrastructure and deep technical issues.

Who this is for

Built for three kinds of operators

Agencies Run Interlinked for multiple clients under your own brand. Scope workspaces, isolate data, and keep delivery consistent across accounts.
Platform partners Embed Interlinked inside a vertical SaaS. Keep your product surface; hand off the messaging, workflow, and AI layer to the partner program.
Multi-brand operators Run one workspace per brand, share an operational playbook. Per-brand branding and billing visibility without duplicating infrastructure.

What partners ask us

Who provides first-line support to end clients?: You do. Your team handles usage questions, basic configuration, and onboarding. Our team handles deep infrastructure, channel connectivity, and AI worker issues through a direct partner channel.
How is the program billed?: Partner billing is a separate contract from standard plans — it accounts for the managed WhatsApp API access, the branded console, and partner-specific support. Full numbers are shared during the application conversation.
How long does the initial setup take?: Roughly 3 to 5 business days to deploy the branded console on your domain once the agreement is signed and your brand assets are ready.
How is client data isolated between workspaces?: Each workspace is its own scope. Conversations, catalogs, branches, AI Config, and Orders never cross accounts. Your admin surface sees aggregate usage; clients only see their own workspace.
What is NOT customizable in the program?: The underlying AI worker and Meta API integrations stay on our infrastructure and aren't swapped per partner. Workflow semantics (e.g. the 15-minute manual pause, the paid appointment validation pattern) are consistent so support, onboarding, and docs stay coherent.