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

# What gets logged

# What gets logged in the app

![Call detail and per-call logging available in the Callaro app.](https://mintcdn.com/callaro-docs/Rn-efrjnSIS1s0ID/images/crm-integrations/what-gets-logged.png?fit=max\&auto=format\&n=Rn-efrjnSIS1s0ID\&q=85\&s=219a391f5d4c7d952c174a35c4c170da)

**What the static image should show:** A real **Call logs** list row and/or the **Call detail** screen for a session (do not use a single hero of an unrelated page).

The product does not expose a separate “CRM logging” page for HubSpot or Salesforce; downstream delivery is a **webhook** / **API** concern (see [Integrations in the web app](https://help.callaro.ai/crm-and-integrations/integrations-in-the-web-app.md)).

## What you can review per call in the product

1. **Outcome and call metadata** — In **Call detail**, the primary workspace shows call/session fields your tenant has access to (status, times, numbers, direction, and related data returned by the API).
2. **Transcript** — When the session has a transcript, it appears in the call-detail workspace (same two-pane call detail).
3. **Recording** — When recording or playback is available for the session, the UI surfaces it in the same workflow (gated by plan and backend data).
4. **Tools / analysis** — Additional rails/tabs in **Call detail** (for example **Tools**, **Webhooks**, cost/latency/debug for permitted roles) show operational data returned for that session.
5. **Webhooks and deliveries** — On the **Webhooks** tab, the app shows:
   * A message when there is no webhook data; copy explains that **pre-call** and **post-call** logs appear when webhooks are configured
   * **Post-call webhook** error blocks (URL, failure time, type) and delivery rows when metrics include them
   * A separate section for **inbound** webhook log entries when inbound webhook logs are non-empty
6. **Finding webhook-related sessions in the list** — On **Call logs**, debug presets (when filter attributes are present) can include items such as **Called webhooks** and **Webhook failures**.

![MEDIA: GIF — In Call detail, switch to the Webhooks tab and expand one section (delivery or error) if data exists; if empty, show the empty state copy.](https://mintcdn.com/callaro-docs/Rn-efrjnSIS1s0ID/images/crm-and-integrations/slot-01.gif?s=074845bd7e8fe57f52f332de8da24d43)

**What the GIF should show:** **Webhooks** tab in focus; expand a delivery or the empty state. Keep the loop under about eight seconds.

![MEDIA: VIDEO — “Review one completed call: transcript, then Webhooks” with chapters.](https://mintcdn.com/callaro-docs/1fJs_sKJdgiwY8nj/media/crm-and-integrations/slot-01.mp4?fit=max\&auto=format\&n=1fJs_sKJdgiwY8nj\&q=85\&s=d5096de771f4ff0d0fa39fecb1400a57)

**What the video should show:** Open **Call logs** → open a completed call → show **transcript/recording** if available → end on **Webhooks** with a clear explanation of what to look for (success vs empty vs error).

## What this article does *not* claim

* It does not describe automatic **HubSpot** or **Salesforce** field updates, because the **web app** does not render those CRMs as first-class UIs. Map external systems from **webhook payload** and **API** behavior documented for developers.
* It does not replace the **API reference**; use the developer site for request/response contracts.

## Related

* [Call detail: start here](https://help.callaro.ai/call-logs-and-reporting/call-detail-start-here.md)
* [Integrations in the web app](https://help.callaro.ai/crm-and-integrations/integrations-in-the-web-app.md)
* [Developer documentation](https://developers.callaro.ai)


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