Skip to main content
After every voice call, Nedzo can automatically analyze the conversation. Configure these features from the Settings tab under Conversation Analysis.

Summary generation

Generate a concise summary of every call. When enabled, each call gets an automatic summary that includes:
  • Key discussion points
  • Outcomes and decisions
  • Action items
  • Any notable details
Summaries appear on the call detail page in your dashboard. You can customize the summary prompt to focus on what matters to your business. Pick the shape of the summary under Conversation Analysis: Custom prompt example: “Summarize the call focusing on: the contact’s main pain point, any pricing discussed, and the agreed next steps.”

Outcome

Every conversation gets one Outcome, on every channel: voice calls, web calls, chat, SMS, email and the other messaging channels. The list is fixed and the same for every workspace, so an outcome means the same thing on every agent, in Conversation Logs, and in workflow conditions. Nedzo sets No answer, Failed, Appointment booked, Booking failed and Transferred from what happened in the conversation. The AI reads the conversation to pick one of the others. When it can’t decide, the outcome is Other. Only Do not disturb turns on Do Not Disturb (DND) for the contact. A plain Not interested does not.
Do not call is now called Do not disturb. Positive and Completed are gone, and older conversations that had them now show Other.Outcome was previously called Disposition, and each agent had its own editable disposition prompt. That prompt is gone: the outcome list is owned by Nedzo and can’t be customized.

Contact details

When a conversation ends, Nedzo fills the contact’s first name, last name, email, phone, and company from what the contact said. This runs on voice, chat, web, and email conversations. You don’t need an extraction field for these five.
  • A field is filled only when it is empty.
  • A value already on file is replaced only when the contact corrects it.
  • Nedzo never guesses. A value is saved only when the contact said it in the conversation.
  • A phone or email that another contact in your workspace already has is skipped.
  • Test calls and the chat simulator don’t fill contact details.

Data extraction

Extract structured data from conversations and save it to your custom fields. This is useful for pulling out specific information that your team needs.

Adding extraction fields

  1. Click Add under Data Extraction
  2. Configure the field:
  1. The agent extracts this data from every conversation
Nedzo sets the field’s name and type from the custom field you pick.
First name, last name, email, phone, and company are not in the Save to contact field list. Nedzo fills them for you (see Contact details). An older extraction field that saved to one of them now shows Filled automatically.

Use cases

  • Budget: the contact’s stated budget
  • Decision timeline: when they plan to make a decision
  • Has authority: whether they’re the decision maker
  • Pain points: main challenges mentioned
  • Competitor: any competitor names mentioned
Extracted data appears on the call detail page and can be used for filtering and reporting.

Conversation Logs

Conversation Logs lists one row per conversation, with its outcome and summary. Use the Outcome filter to show only conversations with a given outcome. For chat and email conversations, the Replies column counts the AI replies sent in that conversation. Replies from your team, sends that failed, and imported WhatsApp history don’t count. Open a row to read the full thread. Long threads load in full, not only the newest messages.

Agent tool calls

Open a row to see the tools the agent ran in that conversation, such as booking a meeting or sending a message. Each one shows as a chip where it happened:
  • Chat, web chat, SMS, email, WhatsApp, Instagram and Messenger: under the agent reply that ran it, in the order it ran.
  • Voice calls: inside the transcript, after the spoken turn that led to it.
Click a chip to see what the agent sent and what came back. Use it to check why the agent did something, or why an action failed. If the agent ran the same tool twice, you see two chips. Tool calls show only in Conversation Logs. Unibox does not show them, so your team’s inbox stays about the conversation itself. Chips are not messages, so they don’t change the Replies count. Calls placed from the dialer have no agent, so they show no tool calls. On a workspace with more than one Instagram account, Instagram rows name the account the conversation came through.