Skip to main content
Post‑call settings define what Fluents.ai does after the call ends. From here you can:
  • Run an AI analysis on the call transcript.
  • Write the raw analysis result to a connected tool (for example, a CRM).
  • Optionally send SMS and/or email follow‑ups, with conditions based on:
    • Whether the call went to voicemail or not.
    • What the post‑call analysis contains.

​
Analyze Call

The Analyze Call section tells Fluents.ai how to summarize or interpret the call once it’s finished.
  • You write an analysis prompt describing what you want:
    • Summaries (key points discussed)
    • Extracted data (names, emails, reasons for calling)
    • Follow‑up suggestions or classifications
  • The agent runs this prompt against the call transcript and metadata.
The output of this analysis:
  • Is stored as a single raw text result attached to the call in Call History.
  • Can be referenced in templates as \“ (for example, in an email body).
  • Is exactly what your analysis prompt generates; Fluents.ai does not reformat it.
Tip: Keep your analysis prompt clear and structured so the result is easy to read or parse in your own systems.

​
Write results to

Write results to lets you send the raw post‑call result to a connected tool such as:
  • HubSpot
  • Salesforce
  • GoHighLevel
  • Lead Docket
  • Monday.com
After each call:
  • Fluents.ai sends the raw analysis text (the output of your Analyze Call prompt) to the selected integration.
  • Your integration or connected app decides how to store or use that text (for example, saving it as a note, activity, or custom field).
Fluents.ai does not automatically map individual fields into the CRM; it sends the analysis result, and you handle the mapping on the destination side.

​
Send SMS

You can configure an optional SMS follow‑up to be sent after a call. There are two parts:
  1. Configure SMS content and provider.
  2. Set conditions that decide when SMS should send.

​
Configure SMS

When you configure SMS, you choose:
  • SMS Provider – Which SMS provider connection to use.
  • From Number – The phone number the SMS will be sent from.
  • To Number – Usually the caller’s number or a variable that resolves to it.
  • SMS Message – The text you want to send.
You can use variables inside the SMS message, for example:
  • \“ – personalization from Call Context or campaign
  • Other context variables you have defined
Example message:
Thank you for calling {first_name}! We will get back to you soon. If you have any questions, just reply to this message.
You can always choose Don’t Send an SMS if you want SMS disabled for this agent.

​
SMS conditions (when SMS should send)

Under Conditions, you decide when an SMS is sent.
All configured conditions must be satisfied for the SMS to go out. You can base conditions on:

​
Call conditions

Here you use whether the call went to voicemail or not voicemail:
  • Send SMS only if the call went to voicemail.
  • Send SMS only if the call was answered by a person.
Examples:
  • “Send SMS if the call went to voicemail” – helpful when someone couldn’t pick up.
  • “Send SMS only if the call was answered” – useful for confirmations after a real conversation.

​
Post‑call analysis conditions

You can also base conditions on the text of the post‑call analysis, using:
  • Contains text – For example, send SMS if the analysis text contains “interested” or “call back later”.
  • Matching field value – If your analysis format includes labeled fields and values, you can test for a specific value.
This lets you do things like:
  • Send a follow‑up SMS only when the analysis suggests the caller is interested.
  • Avoid sending SMS when the person clearly said they are not interested.

​
Send Email

Email follow‑ups work similarly to SMS: you configure content and conditions. You can use:
  • No follow‑up
  • SMS only
  • Email only
  • Or both SMS and Email for the same agent.

​
Configure Email

When you configure email, you choose:
  • Email Provider – The email provider connection to use.
  • From Email – The sender address, for example from@your_company.com.
  • To Email – Destination address(es); usually a team inbox or a variable‑based value.
  • Subject Line – For example, “Inbound call summary”.
  • Email Body – The content of the email.
Within the body you can use variables such as:
  • \“ – caller’s number
  • \“ – number that was called
  • \“ – the raw post‑call analysis text
  • Other call or context variables (for example, \“)
A simple structure might look like: From: {from_number}
To: {to_number} Summary:
{post_call_results} You can choose Don’t Send an Email if you want email disabled for this agent.

​
Email conditions (when Email should send)

Email conditions work the same way as SMS:
  • Call‑based – Voicemail vs. not voicemail.
  • Post‑call analysis‑based – Contains certain text or matches a field value.
Examples:
  • Send an internal summary email only when the call was answered (not voicemail).
  • Send an email to a team queue when the analysis suggests an escalation or urgent follow‑up.

​
Putting it all together

A typical post‑call flow looks like this:
  1. Call ends.
  2. Analyze Call runs using your analysis prompt.
    • The result is stored with the call and exposed as \“.
  3. Write results to (optional) sends the raw analysis result to a CRM or other tool.
  4. SMS / Email (optional) are evaluated:
    • First, check the call condition (voicemail vs. not voicemail).
    • Then, check any post‑call analysis conditions.
    • If all conditions are satisfied, the configured SMS and/or email are sent.

​
Where to go next