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

# Contacts, calls and reports

> Adapter contact states and withdrawals, calls in history, the call overview, reports, and what is visible only in the logs.

# Contacts, calls and reports

## Contacts and withdrawals

The **Campaign contacts** block on the campaign card: search by number, by contract group, and a third field, **Search by adapter contact ID** (exact match). Clicking a row expands it: at the top are **Adapter contact ID** and **External ID (foreign\_id)**, below are the contact variables. The link from the call overview opens the card with the search field already filled in and the row expanded.

![Campaign contacts: search by ID and an expanded row](https://mintcdn.com/hubtalk/imXtUGq2OJsLMMCI/images/v4_adapter_campaign_contacts_en.png?fit=max\&auto=format\&n=imXtUGq2OJsLMMCI\&q=85\&s=04b83eb16c1ce1996b4f038a3331e724)

1. The **Search by adapter contact ID** field: digits only, exact match.
2. Contact state and hold reason: "Waiting · Outside working hours · Retry no earlier than: …".
3. Expanded row: adapter contact ID and external ID (`foreign_id`).
4. Contact variables: fields from the script map and `rl_today`.

| State | What it means |
| - | - |
| Waiting | Waiting to be dialed. The hold reason is in the row: "Outside working hours", "Frequency cap reached", "Retry no earlier than: …". |
| Dialing | Being dialed or in conversation. A `delete` at this moment sets a withdrawal mark: the conversation plays out, and there will be no new attempts. |
| Awaiting evaluation | The retry rules are waiting for the result of the conversation analysis. |
| Done / Exhausted | Success or attempts exhausted. **Exhausted** with zero attempts means the window closed before the contact was dialed. |
| Suppressed | **Withdrawn at the client's request** — `delete` or `delete_phone_number`; **Compatibility adapter request not accepted** — rollback of a failed request; other reasons — the **Do not call** list, frequency policy, deduplication. |

> [!NOTE]
>
> **One contact — several IDs.** If the client sends the same number to the same campaign again, the row goes in as the next batch and gets a new ID. Such a contact has several adapter IDs: the call overview shows the smallest one, and search finds the contact by any of them.

## History and call overview

![History filtered by adapter contact ID](https://mintcdn.com/hubtalk/imXtUGq2OJsLMMCI/images/v4_adapter_history_filtered_en.png?fit=max\&auto=format\&n=imXtUGq2OJsLMMCI\&q=85\&s=ebe86878edd5a1ff8a0f7418e8638434)

A call of an adapter contact in History filtered by the contact ID.

1. **More filters** with a counter of applied filters.
2. The **Adapter contact ID: …** chip; clicking it opens the filter panel on this field, the cross removes the filter.
3. The **Compatibility adapter** badge under the agent name for calls of an adapter campaign.

![The More filters panel with the ID field](https://mintcdn.com/hubtalk/imXtUGq2OJsLMMCI/images/v4_adapter_history_more_filters_en.png?fit=max\&auto=format\&n=imXtUGq2OJsLMMCI\&q=85\&s=74704115d3e9e2838cc07d272671252f)

1. The **Adapter contact ID** field is last: digits only, exact match; applied with the **Show calls** button. The same filter carries over to the report export panel.

The call panel has the tabs **Transcript**, **Overview**, **Data**. For the general layout, see [Call details](https://docs.hubtalk.ai/v4/platform/campaign-history/call-details).

* **Overview** → the **Compatibility adapter** section: the account with its system, the registry script, the contact ID and the **Open the contact in the campaign** link — it switches the organization and opens the campaign card with the contact row expanded.
* **Data** → **Variables passed to the agent**: the final set of call variables, including `rl_today`, fields from the map and platform variables (`today`, `call_date`, `from_number`…). Here too are **Webhook deliveries** with attempts and a retry button.
* **Transcript** → function events before and after the call, the `call_decision` decision, observer incidents.

![Call panel, the Overview tab, the Compatibility adapter section](https://mintcdn.com/hubtalk/imXtUGq2OJsLMMCI/images/v4_adapter_call_overview_en.png?fit=max\&auto=format\&n=imXtUGq2OJsLMMCI\&q=85\&s=5accf53fff0c4b2d5b57797b001c7f2d)

1. Call panel tabs: Transcript, Overview, Data.
2. The **Compatibility adapter** section: account, registry script, contact ID.
3. **Open the contact in the campaign**: switches the organization and opens the card with the contact row expanded.
4. The badge in the list row for calls of an adapter campaign.

## Reports and the daily export

* The call report builder has the columns **Adapter contact ID** and **Registry script**. The **Adapter contact ID** filter from history carries over to the export panel and is restored by the **Change and export** button. See [Reports](https://docs.hubtalk.ai/v4/platform/campaign-history/reports.md).
* The client's [`details`](https://docs.hubtalk.ai/v4/compat-adapter/details) operation returns the daily export using the template from the account: only calls of this account's adapter campaigns, with the day by the organization's time zone. Without a template, the client gets "The export template configuration is missing or invalid".

## What is visible only in the logs

Each client request leaves one summary line in the application log, and the reasons for refusals and rollbacks appear as separate warnings. None of this is in the cabinet. If an investigation comes down to such a reason, ask the platform engineers to check the log by the client's login and the request time. What they will see there:

| Log message | Meaning |
| - | - |
| Request summary: operation, outcome, number of rows, duration | Whether the request happened at all and how it ended: success, sign-in refusal, limit, data error, internal error. |
| `login refused … reason=…` | The reason for the sign-in refusal: wrong password, unknown login, account disabled, limit. |
| `end 21:30 cut to 21:00` | The campaign end was cut to the window; the client got the `notice` key in the response. |
| `row 2 skipped, fields amount_due` | The row was dropped by `flag_ignore_errors: skip`; the fields without values are named. |
| `request … rolled back: …` | Request rollback with the reason: campaign creation refused (for example, an ambiguous binding), a launch blocker (for example, a signature variable without a value), a batch refusal. |


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