> ## Documentation Index
> Fetch the complete documentation index at: https://docs.convocore.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# When To Use Convocore

> Understand when Convocore is a strong fit, and when a fully custom stack may make more sense.

Convocore is best for teams that want to ship AI agents quickly without building the entire infrastructure stack from scratch.

## Convocore is a strong fit when you want to

* Launch across multiple channels from one platform
* Build with prompts, knowledge base, tools, and flows instead of maintaining backend plumbing
* Use voice, web chat, WhatsApp, and other channels without stitching together separate vendors
* Track conversations, analytics, leads, and handoff in one place
* Offer AI agents to clients through a whitelabel workflow
* Use a REST API for automation while still keeping the dashboard and runtime managed

## Why teams choose Convocore

<CardGroup cols={2}>
  <Card title="Infrastructure already handled" icon="server">
    You do not need to build your own conversation storage, realtime runtime, channel connectors, or dashboard framework first.
  </Card>

  <Card title="Interactive UI engine" icon="layer-group">
    Agents can render more than plain text, including cards, buttons, forms, files, images, and embeds.
  </Card>

  <Card title="Tools and integrations" icon="wrench">
    Connect external systems, calendars, sheets, and workflows without building every tool path from scratch.
  </Card>

  <Card title="Agency-ready delivery" icon="building">
    Brand the platform, manage clients, and support multi-tenant delivery through whitelabel features.
  </Card>
</CardGroup>

## What Convocore saves you from building yourself

Without a platform like Convocore, you usually need to assemble and maintain:

* Conversation and lead storage
* Streaming chat and voice runtime infrastructure
* Channel integrations
* Agent configuration UI
* Analytics and transcript tooling
* Human handoff workflows
* API and permissions layers
* Client-facing dashboard infrastructure

## When Convocore may not be the right fit

Convocore is less ideal if your project requires:

* A completely custom front-end where platform widgets and dashboard patterns are too limiting
* Full control over every part of the runtime, hosting, orchestration, and RAG stack
* A highly specialized product where the managed platform model is more restrictive than helpful

In those cases, a more custom architecture may be a better choice.

## Practical rule of thumb

* Choose **Convocore** if you want to move faster, standardize delivery, and focus on agent quality.
* Choose a **fully custom stack** if front-end freedom and infrastructure ownership matter more than speed of delivery.

## Helpful follow-ups

<CardGroup cols={2}>
  <Card title="How Convocore Works" icon="brain" href="/help-center/how-convocore-works">
    See the full create, test, deploy, and manage workflow.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/v3/intro">
    Explore the API if you want deeper automation or custom integrations.
  </Card>
</CardGroup>