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

# FAQ

> Why a case wasn't called, why a user can't see their bot, and other situations that span several screens

This page covers the situations that **can't be explained by looking at a single screen**: they depend on
how the campaign, the rest rules, the labels and the permissions interact.

If your question is about one specific screen —how a field works, what a button does— **each page has its
own frequently asked questions at the end**. Look there first.

> [!NOTE]
>
> Each situation starts with the most likely cause. If you went through all of them and the behaviour still
> doesn't add up, don't keep trying things: write to **Customer Success** with the case, bot or
> campaign identifier at hand.

***

## A case was in the file and the bot never called it

The most likely causes, in order:

> [accordion] The case is resting
>
> If the case was managed before and ended with a label that triggers a rest period, it stays out of
> campaigns until that rest period expires — **even if it comes in a new campaign's file**.
>
> You can confirm this in the campaign detail: the **Discarded for rest** counter tells you how many
> fell for that reason, and the download icon gives you the list with the **rest reason** —the label that
> caused it— and the **activation date**, that is, when it becomes available again.
>
> To see or change how long each rest period lasts: [Rest rules](https://docs.inceptia.ai/en/operacion/reglas-descanso.md).

> [accordion] The case was filtered out during file validation
>
> When you create the campaign, the system checks the file before loading anything. Cases that don't pass
> are marked as **Filtered** and are not managed.
>
> The campaign detail shows how many there were. If the number surprises you, check that the file follows
> the structure configured for that bot in Campaign Input.

> [accordion] The phone was filtered out, not the case
>
> A case can come in and still not be called if **none of its phone numbers is manageable**. The campaign
> detail separates filtered phones from the ones left to manage.

> [accordion] The campaign hasn't reached that case yet
>
> Cases are managed within the configured time window and according to the campaign's priority. If the
> campaign started recently, or its time window is narrow, it may not have reached it yet.
>
> Check the progress in [Campaigns](https://docs.inceptia.ai/en/operacion/campanas.md).

***

## A user can't see a bot that was assigned to them

> [accordion] They have the access but not the assignment
>
> This is the most common cause, and they are two different things: the **access** enables the module,
> the **assignment** defines which bots they work on. A user with the Bots access and no bot assigned
> gets into the module and sees nothing.
>
> Check **Assigned bots** in the user's detail, in [Users](https://docs.inceptia.ai/en/operacion/usuarios.md).

> [accordion] The change is very recent
>
> Accesses can take a few minutes to show up. If you just assigned it, wait and ask the user to sign in
> again.

> [accordion] You checked both and they still can't see it
>
> If the access and the assignment are correctly set and several minutes have passed, **this is not a
> configuration problem**: write to **Customer Success** with the user's email and the bot's name.

***

## The same contact received more than one call

> [accordion] The campaign has retries configured
>
> **Retries** defines how many times an unanswered phone number is tried again. It's set when you create
> the campaign and defaults to 1, that is, a single call per phone number.
>
> It's worth reviewing before a large campaign: see [Create a campaign](https://docs.inceptia.ai/en/operacion/crear-campana.md).

> [accordion] The rest period applied to the phone only, not to the case
>
> A rest rule can rest **only the phone number that answered**, leaving the case's other numbers
> available. If the contact has more than one number on file, they may get calls on the others.
>
> It's configured per label in [Rest rules](https://docs.inceptia.ai/en/operacion/reglas-descanso.md).

> [accordion] They are different debts of the same contact
>
> If the bot has **Ignore debt code** turned off in its global settings, the rest period is recorded
> taking into account the debt the call was about: the same contact can be called again for a different
> debt.
>
> It's in the global settings of [Rest rules](https://docs.inceptia.ai/en/operacion/reglas-descanso.md).

***

## The campaign is running and isn't calling anyone

> [accordion] It's outside the configured time window
>
> A running campaign only works within its time window. Outside that range it stays active but doesn't
> call.

> [accordion] No cases were left to manage
>
> The file may have loaded without leaving any case available, because they all fell out through filters
> or rest periods. The campaign detail shows this under **To manage**.
>
> If the notice appeared when you created it, validation had already warned you: see
> [Create a campaign](https://docs.inceptia.ai/en/operacion/crear-campana.md).

> [accordion] Another campaign has higher priority
>
> Priority defines which campaign goes first when several are active on the same bot.

***

## A report's numbers don't match what I see on screen

> [accordion] You're comparing different periods or states
>
> The on-screen metrics are calculated over the whole campaign. A report exported with a date range, or
> with the campaign still running, will give a different result.

> [accordion] What counts as success is defined by the label
>
> The success rate is calculated over the labels marked as a positive outcome. If a result you consider
> successful isn't configured that way, it doesn't count.
>
> The same goes for contactability: it depends on whether the label counts as contact, and on whether
> that contact was with the account holder or not.

> [accordion] In exports, the Client column carries the bot's alias
>
> Reports label the client with the bot's **alias**, not its technical name. If the alias was changed,
> new reports show the new value.

***

## When to escalate to Customer Success

Before escalating, check whether your **Customer Admin** can solve it: accesses, assigned bots and user
onboarding and offboarding are handled inside your organization, without going through Inceptia.

These other situations **can't be solved from the platform**. Write to **Customer Success** with the
detail in brackets at hand:

* A user with the correct access and assignment who still can't see their bot (user's email and bot name).
* Cases that should have come in and don't show up as filtered or discarded either (case and campaign identifier).
* A campaign that is running, within its time window and with cases to manage, and records no calls (campaign identifier).
* Differences between a report and the screen that aren't explained by period or by label configuration.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.