Logs
Complete visibility into your voice agent operations
Synthflow provides a unified logging system that gives you complete visibility into all your agent operations. Open the Logs page in your Synthflow dashboard to access four log types in one centralized place:
Call logs give you full visibility into every call your agents handle. Beyond the dashboard, you can export call logs to CSV for reporting or consume the same data programmatically through the post-call webhook, which also documents the full list of statuses and end-call reasons.
Click on any call log to view detailed information in the call details drawer, organized into four tabs:
The Overview page shows the call’s status, timing, and agent-related information:
Unknown Contact)The Duration shown in the call log reflects the total call duration, which includes all phases of the call such as PBX delay, ringing time, and conversation time. The Recording, however, only captures the conversation portion of the call. This means the recording duration will often be shorter than the total duration displayed in the log.
For example, a call with a logged duration of 18 seconds may include a PBX delay (e.g., ~4 seconds), ringing (e.g., ~7 seconds), and actual conversation (e.g., ~7 seconds). In this case, the recording would only be 7 seconds long since it starts when the conversation begins.
Chat logs give you full visibility into every chat conversation your agents handle. Conversations are recorded when end users interact with a chat agent over API, widget, WhatsApp, or SMS, and when you test an agent with chat from the agent editor. You can also consume the same data programmatically through the post-conversation webhook.
Click on any chat log to view detailed information in the chat details drawer, organized into three tabs:
The Overview page shows the chat’s status, timing, and agent-related information:
In Progress, Completed)completed, inactivity_timeout)
API logs track every outbound API request your agents make during calls and chats, including custom actions and other integrations. Each entry links back to the Call logs entry that triggered it.
Click on any API log to inspect the request and response, organized into two tabs:
The Details block shows the agent and call context behind the request:
Webhook logs track every webhook delivery to and from your workspace, including inbound webhooks, post-call webhooks, and custom integrations. Each entry links back to the Call logs entry that triggered it. Click on any webhook log to inspect the request and response, organized into two tabs:
The Details block shows the agent, call context, and webhook category:
External, Inbound, Custom Action)Call, API, and webhook logs are also available programmatically. See the API reference for the full set of endpoints and parameters. Chat logs are not yet available via the API.
From the Logs page, use the Agents filter to scope every log type (calls, chats, API, webhook) to a specific agent.
The Duration field includes PBX delay, ringing, and conversation time, while the recording only captures the conversation portion. A logged duration of 18 seconds can correspond to a 7-second recording if there were 4 seconds of PBX delay and 7 seconds of ringing.
Retention depends on your plan. Export logs regularly using the Export button (call logs) or the API reference if you need historical records beyond your plan’s retention window.