Call transcription: where the conversation is sent
The Transcription section of the AI4CALL assistant defines where the conversation is sent when the call ends. You can set up delivery by email or delivery to a webhook. Email is for the person who needs to read the conversation. A webhook is for getting the data inside an application.
These are two separate options, each with its own configuration tab. The transcription is the text of the conversation that took place during the call. The webhook is the address of the external service the portal delivers that data to, so another application can work with it.
Email delivery: SMTP service and recipients
Open Configure in the Email delivery tab. The Enable conversation delivery toggle switches on delivery at the end of the call: as soon as you turn it on, the SMTP service and the recipients field appear.
Choose the SMTP instance to use, then enter one or more email addresses, separated by commas. In the example, the message goes to support and to the manager. The addresses shown are for demonstration only: in your own setup, enter the mailboxes that really need to receive the conversation.
- Enable conversation delivery: switches on delivery at the end of the call.
- SMTP service: the instance used to send the message.
- Recipients: one or more email addresses, separated by commas.
- Configure SMTP: opens the choice of which instance to manage.
Configure SMTP: choosing and checking the instance
The Configure SMTP button opens the choice of which instance to manage. If you have several services, select the one used for this delivery and make sure its configuration is complete before you switch delivery on.
A correct recipient list is not enough if the email service cannot send.
Transcription settings, email delivery
Webhook delivery: bringing the conversation into your applications
For an integration, open Webhook delivery. Switch delivery on and enter the address of the receiving service. The screen shows a POST request with data in JSON format: the payload includes caller, called, callid and conversation.
The receiving system can use the call identifier to attach the transcription to the right record: the customer record in your management software, for example. The address must point to an endpoint able to receive this structure.
The shape of the data is shown here in the window. Agree on it with whoever builds the integration, before you switch delivery on.
Webhook authentication: Bearer Token, API Key, Basic Auth and OAuth
If the receiving service requires credentials, create the authentication and link it to the webhook. The portal manages reusable authentications such as Bearer Token, API Key, Basic Auth and OAuth: choose the one the receiving service asks for. Do not put credentials in the assistant prompt.
Email or webhook: how to choose
Email is for the person who needs to read the conversation: it arrives in the mailboxes you list, separated by commas, through the SMTP instance you selected. A webhook is for getting the data inside an application: a POST request in JSON with caller, called, callid and conversation, sent to an endpoint able to receive it, with the authentication the receiving service requires.
Final checks before saving the configuration
Check the recipients and the email instance, or the endpoint and its authentication. Save the webhook configuration where required, then save the assistant. After a test call, also check that the conversation actually reached the receiving system.
- Check the email recipients and the SMTP instance, or the webhook endpoint and its authentication.
- Save the webhook configuration where required.
- Save the assistant.
- Make a test call and check that the conversation reaches the receiving system.
The final check is about actual delivery, not only the settings visible in the portal.
Frequently asked questions about Transcription
What is the Transcription section of the AI4CALL assistant for?
It defines where the conversation is sent when the call ends. The two options are email delivery, for the person who needs to read the conversation, and delivery to a webhook, for getting the data inside an application.
What data is sent to the webhook?
The portal sends a POST request with data in JSON format. The payload includes caller, called, callid and conversation. The receiving system can use the call identifier to attach the transcription to the right record.
How do you handle credentials required by the receiving service?
Create the authentication and link it to the webhook. The portal manages reusable authentications such as Bearer Token, API Key, Basic Auth and OAuth. Choose the one the receiving service asks for, and do not put credentials in the assistant prompt.
Want your transcriptions inside your own systems?
We will show you how to set up email delivery and the webhook integration on your AI4CALL assistant, starting from the workflows you already use.