Skip to main content

​
What gets logged in the app

Call detail and per-call logging available in the Callaro app. 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).

​
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. 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. 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.