> For the complete documentation index, see [llms.txt](https://docs.fullwhere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fullwhere.com/documentation/documentation-en/missed-calls/call-log.md).

# Call log

Find calls forwarded to Fullwhere, check the status of WhatsApp invitations, and access your customer conversations.

The **call log** lets you track calls transferred to Fullwhere, location by location. For each call, you can see the caller, whether they agreed to continue on WhatsApp, the invitation status, and access to the conversation when available.

Use it to find a specific call, understand why an invitation was not received, or open the conversation to handle the customer's request.

## Access the call log

In **Missed calls**, click **Call log** in the top-right corner of your screen.

The table shows calls for the selected scope and time period. The **Date** column shows the date and time of each call; the most recent calls appear first in the view shown below.

{% hint style="info" %}
The log lists calls that reach **Fullwhere** through call forwarding. Calls answered directly by your establishment, without being forwarded to Fullwhere, do not appear in this log.

To set up or check the process, see the [missed calls setup guide](https://docs.fullwhere.com/documentation/documentation-en/missed-calls/configuration.md).
{% endhint %}

## Find a call using filters

The filters are located above the table. Combine them to narrow your search.

| Filter             | How to use                                                                                                                     |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------ |
| **Date**           | Select the date range in which to search for calls.                                                                            |
| **Location**       | Limit the search to the desired location.                                                                                      |
| **Caller**         | Search for a customer by name or phone number.                                                                                 |
| **Consent**        | Find calls based on whether the caller agreed to continue on WhatsApp.                                                         |
| **Invitation**     | Filter by invitation status: received, sending, blocked, etc.                                                                  |
| **Response**       | Choose **With response**, **Without response** or **No conversation**. The latter option corresponds to rows displaying **—**. |
| **Failure reason** | Search for calls affected by a specific cause of blocking or failure.                                                          |

## Read call details

| Column           | Information shown                                                                          |
| ---------------- | ------------------------------------------------------------------------------------------ |
| **Date**         | Call date and time.                                                                        |
| **Location**     | Establishment associated with the call.                                                    |
| **Caller**       | Customer name when a profile is associated, phone number, or the label **Private number**. |
| **Consent**      | Result of collecting consent to continue on WhatsApp.                                      |
| **Invitation**   | Status of the WhatsApp invitation send and delivery.                                       |
| **Conversation** | Response attributed to the invitation and link to the conversation, when available.        |

In **Caller**, click the customer's name to open their record in a new tab. When a number is displayed with a copy icon, click the icon to copy it.

### Understanding caller consent

The **Consent** column applies only to the consent requested during the voice flow.

| Consent          | Meaning                                                                    |
| ---------------- | -------------------------------------------------------------------------- |
| **Granted**      | The caller agreed to continue on WhatsApp.                                 |
| **Not required** | The consent request is disabled in the location settings.                  |
| **Not obtained** | The flow did not collect the required consent. The invitation is not sent. |
| **Pending**      | The consent collection result is not yet available.                        |

Consent **Granted** does not guarantee that the invitation will be received: a reached limit, a delay between invitations, or a sending issue may still prevent delivery. Also check the **Invitation**.

You can change how consent is collected in the [location settings](https://docs.fullwhere.com/documentation/documentation-en/missed-calls/configuration.md).

### Understanding invitation status

| Invitation      | Meaning                                                                                                                 |
| --------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Pending**     | No sending result is available yet. When consent is also pending, the hover text says **Consent pending**.              |
| **Not sent**    | The required consent was not obtained. The hover text says **Consent not obtained**.                                    |
| **Sending**     | WhatsApp accepted the send, but delivery has not yet been confirmed.                                                    |
| **Received**    | WhatsApp confirmed delivery of the invitation. This status does not mean the customer has read it or replied.           |
| **Blocked**     | A setting prevents the send: the delay between invitations has not elapsed, or a limit has been reached.                |
| **Failed**      | The number is missing or invalid, the send failed, or WhatsApp reported a delivery failure.                             |
| **Unconfirmed** | Delivery of the invitation was not confirmed after **24 hours**. This does not establish that the customer received it. |

{% hint style="info" %}
**Hover over the badge in the Invitation column to see the available reason.**

A call with consent **Granted** and an invitation marked **Blocked** is not necessarily an error: the location's sending rules may have prevented another invitation.
{% endhint %}

### Identifying the reason for a block or failure

The reason appears when you hover over the status **Invitation**. The filter **Failure reason** helps you find the affected calls.

| Displayed reason                                    | What you can check                                                                                                                                            |
| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Wait period between invitations has not elapsed** | The same number was already contacted within the specified period. Check the setting **Wait period between invitations to the same number** for the location. |
| **Invitation limit reached**                        | Check the invitation limit and when it will next reset in the location’s settings.                                                                            |
| **Missing or invalid number**                       | Check whether the caller appears with a usable number. A caller with a hidden number does not provide the number needed to send the invitation.               |
| **Failed to send**                                  | Check the WhatsApp account connection and whether its invitation template is available.                                                                       |
| **Failed to deliver**                               | WhatsApp reported a failure after accepting the send request. Initial acceptance therefore does not guarantee that the message was received.                  |
| **Delivery not confirmed after 24 hours**           | Delivery confirmation did not arrive within this period. When the conversation is available, check it to review the exchanges with the customer.              |

To adjust the limits and the wait period between invitations, see [Settings](https://docs.fullwhere.com/documentation/documentation-en/missed-calls/configuration.md). To check the expected name, category, languages, and content of the template, follow the guide [WhatsApp template for missed calls](https://docs.fullwhere.com/documentation/documentation-en/missed-calls/whatsapp-template-for-missed-calls.md).

If the failure persists, contact the Fullwhere team and provide the location, the date and time of the call, and the displayed reason.

## Open the conversation and follow up on the response

The **Conversation** column brings together information about the response and access to the exchange in the Inbox.

| Display          | Meaning and action                                                                                                                                                            |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Replied in …** | A response has been attributed to the invitation. The duration indicates the time between sending the invitation and receiving this response. Click to open the conversation. |
| **No response**  | A conversation is linked to the call, but no response has been attributed to this invitation. Click to view the exchange.                                                     |
| **—**            | No conversation is linked to this call; no link is available on this row.                                                                                                     |

**To handle a request:** find the call, click **Replied in …** or **No response**, then continue the exchange in the Inbox.

{% hint style="info" %}
**The three columns should be read separately.**

* **Consent** indicates whether the caller agreed to continue on WhatsApp.
* **Invitation** indicates the status of sending or delivery.
* **Conversation** indicates whether a response is attributed to the invitation and provides access to the conversation.

An invitation that failed to deliver may still have a link to its conversation. Conversely, a call listed in the log does not necessarily have a conversation.
{% endhint %}

### Why does it say “No response” when the customer wrote back?

The log displays responses **attributed to the invitation**, according to the location’s **Response attribution** setting.

For example, with an attribution period of **48 hours**, a message received three days later appears in the Inbox, but isn’t automatically counted as a response to that invitation. However, a reply sent directly to the invitation message may still be attributed to it after this period.

Open the conversation to read the full exchange, then see the [setup guide](https://docs.fullwhere.com/documentation/documentation-en/missed-calls/configuration.md) to understand or adjust this period.

## View statistics

Click **Statistics**, at the top right of the log, to open the missed-call analytics view.

The log helps you review **each call** and find a conversation; statistics let you track the feature’s overall results.

## If a call doesn’t appear in the log

1. Check the filters **Date**, **Location** and any other active filters.
2. Check that the call was forwarded to the location’s **Fullwhere number** .
3. Check that the location’s configuration is active or in its test flow.

A disabled configuration no longer handles new forwarded calls. If needed, resume the [setup and testing guide](https://docs.fullwhere.com/documentation/documentation-en/missed-calls/configuration.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fullwhere.com/documentation/documentation-en/missed-calls/call-log.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
