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

# What Sympana Connector Cannot Do

> Understand the limits of Sympana Connector so you do not blame the wrong system.

<div className="max-w-5xl mx-auto pt-4 pb-8">
  <div className="rounded-3xl border border-zinc-800 bg-gradient-to-br from-blue-500/10 via-zinc-950 to-zinc-950 p-8">
    <p className="text-xs uppercase tracking-[0.2em] text-zinc-500">Limits</p>
    <h1 className="mt-3 text-4xl font-semibold tracking-tight text-white">What Sympana Connector will not fix for you.</h1>

    <p className="mt-4 max-w-3xl text-zinc-300 text-lg leading-8">
      Sympana Connector removes a lot of setup pain, but it does not erase provider limits, missing workflow steps, bad prompts, or unsupported behavior.
    </p>
  </div>
</div>

<Columns cols={2}>
  <Card title="Provider limits still apply">
    Free trial Retell or Vapi accounts can still fail to place real calls, and unsupported carrier or regional behavior still stays unsupported.
  </Card>

  <Card title="Bad workflow structure still breaks things">
    If actions are in the wrong order, the lead has no phone number, or the connection is misconfigured, the automation can still fail.
  </Card>

  <Card title="Prompt quality still matters">
    The product helps your workflow run, but results still depend on prompt design, call logic, offer quality, and lead quality.
  </Card>

  <Card title="This is not an internal backend window">
    User-facing workflows should focus on supported triggers, actions, functions, and returned workflow data only.
  </Card>
</Columns>

<Check>If you are unsure whether the problem is your provider, GoHighLevel workflow, or Sympana Connector setup, go through Troubleshooting first and then [join the Sympana Discord server](https://discord.gg/QXk7ddhmZQ) to get the fastest support from someone on the Sympana team.</Check>