Topic

Conversation Intelligence

2 posts about Conversation Intelligence. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Posts

Twilio
Augment Voice Calls with Twilio Conversation Intelligence Using Node.js
Twilio Conversation Intelligence, Conversation Orchestrator, and Conversation Memory together analyze voice calls for a Node.js voice agent built with Conversation Relay. After a call, Twilio sends a webhook to /intelligence-results containing a call summary, sentiment analysis, and script adherence for categories like introduction with the required phrase “Thanks for calling Owl Air! I’m Hoot.” The developer creates a Memory Store and Conversation Configuration, then an Intelligence rule selecting Sentiment, Summary, and Script-Adherence operators triggered at conversation end. A Node.js handler extracts the data and persists it to a SQLite database using tables for intelligence_results, operators, and operator_script_adherence_categories. Testing involves calling the Twilio number and verifying the summary, sentiment, and script adherence records in the database.

Twilio
How to Augment Voice Calls with Twilio Intelligence
This tutorial shows PHP developers how to augment a Twilio voice AI agent with Conversation Intelligence, Conversation Orchestrator, and Conversation Memory. The goal is to retrieve a short summary of each customer call, analyze the caller’s sentiment, and check whether the agent followed set guidelines. The information is persisted to a SQLite database for later use. The tutorial builds on a previous voice agent tutorial and requires a Twilio account, a voice-capable phone number, and ngrok to expose the local server. It walks through setting up Conversation Orchestrator, Conversation Intelligence, and the application database, then testing the flow with example questions. The post also mentions the Conversations API (V2) for retrieving call summaries and sentiment analysis.

The best engineering reads, once a week.

Topic

2 posts about Conversation Intelligence. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Twilio
Augment Voice Calls with Twilio Conversation Intelligence Using Node.js
Twilio Conversation Intelligence, Conversation Orchestrator, and Conversation Memory together analyze voice calls for a Node.js voice agent built with Conversation Relay. After a call, Twilio sends a webhook to /intelligence-results containing a call summary, sentiment analysis, and script adherence for categories like introduction with the required phrase “Thanks for calling Owl Air! I’m Hoot.” The developer creates a Memory Store and Conversation Configuration, then an Intelligence rule selecting Sentiment, Summary, and Script-Adherence operators triggered at conversation end. A Node.js handler extracts the data and persists it to a SQLite database using tables for intelligence_results, operators, and operator_script_adherence_categories. Testing involves calling the Twilio number and verifying the summary, sentiment, and script adherence records in the database.

Twilio
How to Augment Voice Calls with Twilio Intelligence
This tutorial shows PHP developers how to augment a Twilio voice AI agent with Conversation Intelligence, Conversation Orchestrator, and Conversation Memory. The goal is to retrieve a short summary of each customer call, analyze the caller’s sentiment, and check whether the agent followed set guidelines. The information is persisted to a SQLite database for later use. The tutorial builds on a previous voice agent tutorial and requires a Twilio account, a voice-capable phone number, and ngrok to expose the local server. It walks through setting up Conversation Orchestrator, Conversation Intelligence, and the application database, then testing the flow with example questions. The post also mentions the Conversations API (V2) for retrieving call summaries and sentiment analysis.

The best engineering reads, once a week.