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

# Support

> Contact support with the information needed to investigate access, calls, messages and integrations.

export const Availability = ({lang = 'es', plan, addon, permission, route, status}) => {
  const L = lang === 'en' ? {
    plan: 'Plan',
    addon: 'Add-on',
    permission: 'Permission',
    route: 'Where',
    status: 'Status',
    addonNote: 'enabled on request',
    allPlans: 'All plans',
    beta: 'Beta',
    nuevo: 'New',
    soon: 'Coming soon'
  } : {
    plan: 'Plan',
    addon: 'Add-on',
    permission: 'Permiso',
    route: 'Dónde',
    status: 'Estado',
    addonNote: 'se activa a pedido',
    allPlans: 'Todos los planes',
    beta: 'Beta',
    nuevo: 'Nuevo',
    soon: 'Próximamente'
  };
  const items = [];
  if (plan) items.push([L.plan, plan]);
  if (addon) items.push([L.addon, `${addon} · ${L.addonNote}`]);
  if (permission) items.push([L.permission, permission]);
  if (route) items.push([L.route, route]);
  if (status) items.push([L.status, L[status] || status]);
  return <div style={{
    display: 'flex',
    flexWrap: 'wrap',
    gap: '6px 22px',
    padding: '12px 16px',
    margin: '4px 0 24px',
    border: '1px solid rgba(2, 82, 255, 0.28)',
    borderLeft: '3px solid #0252ff',
    borderRadius: '8px',
    background: 'rgba(2, 82, 255, 0.05)',
    fontSize: '13.5px',
    lineHeight: '1.5'
  }}>
      {items.map(([k, v]) => <div key={k} style={{
    display: 'flex',
    gap: '6px',
    alignItems: 'baseline'
  }}>
          <span style={{
    fontSize: '10.5px',
    fontWeight: 600,
    letterSpacing: '0.07em',
    textTransform: 'uppercase',
    opacity: 0.65
  }}>{k}</span>
          <span style={{
    fontWeight: 500
  }}>{v}</span>
        </div>)}
    </div>;
};

<Availability lang="en" route="Support" />

Email [support@contactship.ai](mailto:support@contactship.ai) for help or questions about enabling a module. Describe the expected result and what happened.

## What to include

| Problem               | Useful details                                         |
| --------------------- | ------------------------------------------------------ |
| Access or permissions | Organization, affected section and blocked action      |
| Call                  | Call ID, date, time, time zone and status              |
| Message or campaign   | Channel, conversation or campaign and visible error    |
| Integration or API    | Method, path, response status and attempt time         |
| Billing               | Organization and affected payment or invoice reference |

Do not send passwords, API keys, tokens or full payment card details. Use identifiers and redact secrets.

## Before contacting support

1. Check the active organization.
2. Check that your role permits the action and the module is enabled.
3. Record the exact error and reproduction steps.
4. Before repeating a message, call or payment, check its status: a screen error does not prove the operation failed.

## Request module access

Explain what you need to accomplish and which organization will use it. Contact center, routing, agenda, tasks and history can require specific activation. Asking about availability does not activate a module automatically.

## Support request template

```text theme={null}
Organization:
Affected section or identifier:
Date, time and time zone:
What I tried:
Expected result:
Actual result and exact error:
Steps to reproduce:
```

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Where should I report an app error?">
    Email support with your organization and reproduction steps. Include the identifier if a call or conversation is affected.
  </Accordion>

  <Accordion title="Do I need to send my API key for integration support?">
    No. Share the method, path, time and response without secrets. Identifiers help locate the request.
  </Accordion>

  <Accordion title="Why is a documented section missing from my organization?">
    Availability may depend on activation, plan or permissions. Review [Roles and permissions](/en/organization/roles-and-permissions) and ask about the module.
  </Accordion>
</AccordionGroup>

## See also

* [Roles and permissions](/en/organization/roles-and-permissions)
* [API keys](/en/organization/api-keys)
* [Plans and limits](/en/billing/plans)