Pearl
Post-Call
All you need to know about Post-Call in NLPearl
What is a Post-Call?
In NLPearl, a post-call is a structured summary generated after each phone conversation handled by Pearl. It centralizes all key information captured before, during, and after the call to ensure full traceability, improve quality, and support human follow‑up when needed.What Does the Post-Call Include?
A post-call provides multiple key sections to review and analyze the outcome of a conversation:Call ID
A unique identifier for each call, displayed at the top right of the page. It allows you to quickly reference or search for a specific call across the system.
Call Details
This section summarizes the essential metadata captured during the call, including participant details, call status, timing, and performance metrics.| Ref | Section | Description |
|---|---|---|
| ① | Header Information | Displays the phone numbers for both the caller and the receiver. Also includes the name of the Pearl used and the status of the call (e.g. “Call Successful”). |
| ② | Call Metrics | Shows the duration of the call (in mm:ss) and the final call status (e.g. Completed, Busy, Missed). |
| ③ | Timestamp | Located on the right-hand side, this shows the exact date and time the call took place. |
Call Status
The technical status of the call (whether the user answered or not). Possible values include:
| Status | Description |
|---|---|
In Progress | The call is currently ongoing or being connected. |
Completed | The call was successfully connected and ended normally. |
Busy | The receiver was already on another call or rejected the call. |
Failed | The call could not be established due to an error or network issue. |
No Answer | The call rang but no one picked up before the timeout. |
Call Status refers to the telephony-level result of the call connection, such as whether the call was picked up, missed, busy, or failed to connect.
Conversation Status
Indicates the outcome of the conversation from a business or process perspective. Possible values include:
| Status | Description |
|---|---|
Voice Mail Left | A voicemail was successfully left. (Outbound only) |
Need Retry | The contact attempt failed and should be retried. (Outbound only) |
Unreachable | The user could not be reached. (Outbound only) |
Call Successful | The conversation achieved its expected outcome. |
Not Successful | The conversation failed to meet its objective. |
Completed | The conversation was conducted and finalized, regardless of outcome. |
Important distinctions about Conversation Status:
-
Voice Mail Left,Need Retry, andUnreachableare only shown for outbound activities; these statuses are not applicable for inbound calls. -
The difference between
Successful,Not Successful, andCompletedepends on whether a Success Definition was configured when creating the Pearl:- If a Success Definition was configured:
Successful→ the Success Definition criteria were met during the conversation.Not Successful→ the conversation did not meet the Success Definition criteria.
- If no Success Definition was configured:
Complete→ the conversation was completed without any Success Definition evaluation.
- If a Success Definition was configured:
For more information on Success Definitions, see How to Create a Pearl – Step 4: Flow Configuration.
Tags
The list of tags defined during the last step of the Pearl creation process. These tags represent key topics or categories you chose when setting up the Pearl configuration.
For more information on setting up tags, see How to Create a Pearl – Step 4: Flow Configuration.
Events
A log of the actions triggered by Pearl during the call. Each event includes a timestamp and details about the action. Possible event types include:
| Event Type | Description |
|---|---|
Call Transferred | The call was transferred to another destination. |
SMS Sent | A text message was sent to the customer. |
API | An API was triggered during the conversation. |
Email Sent | An email was sent during the call. |
Appointment Booked | An appointment was booked in the calendar. |
The Event Log provides a chronological view of all actions triggered by Pearl during the call. Each entry includes the action type (such as API call, SMS sent, or email), the execution status, and contextual data. This section allows users to review the flow of automated operations, verify that each action was successfully executed, and understand the resulting outputs in detail.
Sentiment Analysis
An automatic classification of the customer’s tone and emotional state throughout the conversation. Possible sentiment values include:
| Sentiment Value | Description |
|---|---|
Positive | The conversation was clearly positive in tone and emotion. |
Slightly Positive | The overall tone was mostly positive, with minor neutral moments. |
Neutral | The sentiment was balanced or emotionless. |
Slightly Negative | The tone leaned slightly negative, but not strongly so. |
Negative | The conversation had a clearly negative emotional tone. |
Summary
A concise, human‑readable recap of the conversation, generated by Pearl. This includes:- What the customer requested
- What was confirmed or declined
- The overall outcome of the interaction
Transcript
A full text version of the conversation between the customer and Pearl. Always available. Useful for:- Reviewing the interaction
- Auditing purposes
- Training and improvement
Call Information
This section displays structured variables captured before or during the call, corresponding to the dynamic data collected through the Pearl configuration.Examples:
- Delivery type
- Selected options (e.g. “Dessert: Cheesecake”)
- Customer preferences
You can learn more about creating variables in the Pearl here.
Recording
The recording is accessible directly from this page, allowing you to listen to the entire conversation again for audit, training, or operational purposes.
If you wish to disable call recording, you can manage this setting from the activity configuration (whether inbound or outbound).
Why the Post-Call Matters
Traceability
Every call leaves a documented trace for accountability.
Faster Follow‑Up
Helps support and operations teams follow up efficiently with customers.
Quality & Analytics
Enables continuous improvement through quality review, sentiment tracking, and conversation analysis.
Auditing & Compliance
Provides an auditable record of AI-driven conversations to meet regulatory or internal policy needs.
By consolidating all these elements, the Post-Call Activities page provides a complete overview of each AI-handled conversation, ensuring transparency, traceability, and actionable insights for your team.