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

# Callback Notification node

> Record a confirmed callback request and notify a configured business recipient after the call.

Use the **Callback Notification** node to send one business follow-up after a
caller has confirmed callback details. It is a disconnected integration: it
runs after the workflow call completes and does not keep the caller on the
line. It does not imply that a human handoff was attempted.

## Callback fields

The conversational workflow must collect these exact values before its callback
terminal edge:

| Field                        | Type    | Requirement                                             |
| ---------------------------- | ------- | ------------------------------------------------------- |
| `callback_name`              | string  | Non-empty caller name, such as `Example Caller`         |
| `callback_phone`             | string  | Non-empty callback number, such as `+34 000 000 000`    |
| `callback_time_window`       | string  | Non-empty preferred time, such as `tomorrow morning`    |
| `callback_reason`            | string  | Non-empty concise reason, such as `Discuss the service` |
| `callback_requested`         | boolean | `true` only when the caller requests a callback         |
| `callback_details_confirmed` | boolean | `true` only after explicit caller confirmation          |

Read back the name, number, preferred time, and reason. Ask the caller to
explicitly confirm that the read-back is correct. Only then set
`callback_details_confirmed` to `true`, speak a formal acknowledgement, and end
the call. If details are missing or not confirmed, the request is sent to the
business as a needs-review alert when a safe recipient is available.

If the caller hangs up or the call times out during collection, Klatt extracts
the latest available details before post-call processing. An explicit callback
request can still produce a needs-review alert; a withdrawn request produces
no email. If extraction fails, missing details are not invented and the
notification may be unavailable.

## Choose the recipient

Enter **Business callback email** when generating a workflow, or edit the
recipient on its Callback Notification node. This is the only email setting
you need. Klatt sends notifications using its managed sender; no Resend account,
API key, sender address, or reply-to setup is required from your organization.

Leave the recipient blank during generation to disable callback notifications.
If Klatt's email service is unavailable, contact Klatt support and retry after
it is restored. Your generation draft is preserved.

## Configure the node

Copilot can create this setup: enter the optional business callback email while
creating a workflow. Copilot adds the dedicated callback collection step and
the disconnected node. You can also configure it manually:

1. Add **Callback Notification** as a disconnected integration node.
2. Open the node configuration and enter the business recipient email address
   that should receive the alert.
3. Leave it enabled for the workflow that offers a supported callback path.
4. Collect and confirm the six callback fields on the conversational callback
   path before the terminal edge.
5. Test both the unavailable-handoff callback path and a resolved path.

The recipient field is validated as an email address during workflow
validation and publish. It may be a business inbox that is not the workflow
owner's Klatt login address; the node remains part of the tenant-owned
workflow definition.

Resolved calls do not trigger a callback email. The workflow owner account is
not used as an implicit recipient. The configured `recipient_email` is the
sole business recipient. The caller is never emailed and is not asked for an
email address by this integration.

## What the caller hears

After a confirmed read-back, the agent acknowledges that the details were
recorded for the team. This acknowledgement does not claim that the issue was
resolved, that a handoff was attempted, that an email was sent, or that delivery
was completed.

## Delivery and privacy

Delivery failures appear in the workflow-run annotations for operator review.
An accepted notification means the mail provider accepted the request; it does
not prove inbox delivery. Collect only the minimum callback details needed for
the business to return the call. See [Context and variables](/core-concepts/context-and-variables)
for data-handling guidance.

Klatt’s managed email service must be configured before enabled notifications can be created.

Do not add transcripts, recordings, public artifact links, or unrelated caller
details to the callback request.