Summarize and deliver call results¶

Post-processing creates the final call summary and can deliver it by email or webhook after the call. Choose the relevant profile before changing its summary or delivery settings.

1. Define the summary¶

Open Post Processing → Summary Prompt in the selected profile. Describe the information your team needs:

Summarize the caller's request with name, confirmed callback number,
reason, outcome and any promised next step. Mark missing information clearly.
Use stored facts where relevant: {conversation_fact_summary}
Use caller context only where relevant: {pre_call_context}
Do not invent an action or promise that is absent from the conversation.

To use an individual caller-lookup value in the summary prompt, insert a field path such as {pre_call_context.customer.name}. See the pre-processing guide for field paths and list access.

You can write a separate summary prompt for each profile. Leave it empty to use the default configuration. If needed, append saved facts, the conversation history or a list of tools used. The tool list includes names and status, but not full requests or responses.

2. Configure summary email¶

Enable delivery, set To and optional CC recipients, and configure subject and body templates. Begin with a neutral subject such as Callback request and a body containing {summary}.

Enable Skip when the caller did not say anything if silent calls should not produce an email. This affects email delivery, not storage of the final summary. Configure the webhook's separate setting independently.

Choose Always to send every eligible call summary. Use Conditional to send only selected results, such as callback requests. To avoid duplicate messages, check whether an Email Tool already sends the same notification during the call.

Use individual facts in email templates¶

You can insert saved conversation facts into the email subject and body. For the fact keys name and company, use the placeholders {fact_name} and {fact_company}.

Example subject:

Callback request from {fact_name}

Example message body:

{summary}

Company: {fact_company}

The values come from saved conversation facts. If a fact is missing, Nuvoca inserts Nicht angegeben (not provided) in its place.

3. Configure a summary webhook¶

Enable the webhook and enter target URL, timeout, content type, supported authentication, headers, query values and body. The editor supports JSON, form or text bodies. Use the target system's expected structure and inspect the rendered request before sending.

Send Test sends a real request to the address you entered. Use a test destination and check that it receives the expected data. Then make a test call and check delivery after hanging up.

Send JSON objects and lists¶

In a JSON body, you can send saved conversation facts as an object and the tool list as an array. Insert these placeholders without quotation marks to preserve their structure. Use {duration_seconds} without quotation marks to send a number as well.

Template for the application/json content type:

{
  "summary": "{summary}",
  "facts": {conversation_fact_summary},
  "tools": {tool_invocations},
  "duration_seconds": {duration_seconds}
}

The template is converted to JSON when sent. For example:

{
  "summary": "Alex requests a callback.",
  "facts": {"name": "Alex", "customer_id": "K-1042"},
  "tools": [],
  "duration_seconds": 42
}

The receiving system can process individual values from the facts object. With quotation marks, as in "{conversation_fact_summary}", the facts are sent as text. Check the preview to confirm that the data matches the format your destination expects.

Email and webhook variables¶

Variable	Content
`{summary}`	Final generated summary
`{conversation_history}`	Available conversation history
`{conversation_fact_summary}`	Stored conversation facts
`{tool_invocation_summary}`	List of tools used, as text
`{tool_invocations}`	List of tools used, as structured data
`{from_number}`, `{to_number}`	Available caller and called numbers
`{started_at}`, `{ended_at}`, `{duration_seconds}`	Available call timing

Choose variables from the list in the relevant editor.

Verify the complete outcome¶

After the test call, check the summary in Call History and confirm receipt at the destination. Also test a silent call, a missing detail and a delivery failure.