Background Speech Denoising, Cartesia Transcriber, Workflow Enhancements, and Call Error Handling
- Background Speech Denoising Plan: You can now enhance call quality by configuring advanced background speech denoising options using the new
assistant.backgroundSpeechDenoisingPlan.smartDenoisingPlan
(default:false
), which replaces the previousbackgroundDenoisingEnabled
setting.
Use the SmartDenoisingPlan
to filter out background speech and noise using Krisp technology.
Fine-tune noise reduction with the new FourierDenoisingPlan
for more control over audio clarity.
Smart and Fourier denoising can be combined for optimal results. Order of precedence: Smart denoising, then Fourier denoising.
-
Workflow Server Property: Workflows now support a
server
property, allowing you to specify a server URL to receive webhook callbacks for workflow events directly. -
New Workflow Models: You can now integrate Google’s LLMs or custom models into your workflows by specifying
Google
orCustom LLM
in your workflow model settings. Select your model under Model Settings

-
Enhanced Error Reporting for Cartesia Services: A new
endedReason
valuepipeline-error-cartesia-502-server-error
has been added to help you identify and handle specific errors related to Cartesia server issues. -
Enhanced Error Handling and Status Enums: We’ve added new error enums and status codes to help you better handle and debug call-related issues:
-
VAPI Fault Errors: Detect specific VAPI-related errors during call start using
call.start.error-vapifault-get-org
andcall.start.error-vapifault-get-subscription
-
Subscription Status Errors: Identify subscription-related issues with new enums:
call.start.error-subscription-frozen
(replacesunknown-error
)call.start.error-subscription-insufficient-credits
-
Call Completion Statuses: Track how calls are completed with new enums:
call.in-progress.twilio-completed-call
call.in-progress.sip-completed-call
-
In-Call Error Detection: Handle specific errors during active calls using enums like
call.in-progress.error-vapifault-chat-pipeline-failed-to-start
-