From aa5fa6e7b1850a088d6e256b9a811e42287db82b Mon Sep 17 00:00:00 2001 From: Quantstruct Bot Date: Fri, 18 Apr 2025 11:46:16 -0700 Subject: [PATCH] Add changelog for 2025-04-18 --- fern/changelog/2025-04-17.mdx | 8 ++++++++ fern/changelog/2025-04-18.mdx | 1 + 2 files changed, 9 insertions(+) create mode 100644 fern/changelog/2025-04-17.mdx create mode 100644 fern/changelog/2025-04-18.mdx diff --git a/fern/changelog/2025-04-17.mdx b/fern/changelog/2025-04-17.mdx new file mode 100644 index 000000000..e5e99b493 --- /dev/null +++ b/fern/changelog/2025-04-17.mdx @@ -0,0 +1,8 @@ +**1. **Custom Hooks When a Call is Ringing**: You can now define custom hooks on your phone numbers to automatically perform actions when a call is ringing. This enables you to play messages or transfer calls without additional server-side code by using the new `hooks` property in `Call.phoneNumber.hooks["phoneNumberHookCallRinging"]`. + +**2. **Say and Transfer Actions in Hooks**: The new [phone number hook call ringing](https://api.vapi.ai/api#:~:text=PhoneNumberHookCallRinging) allows you to specify actions that trigger when a call is ringing (`on: 'call.ringing'`). like [redirecting calls](https://api.vapi.ai/api#:~:text=TransferPhoneNumberHookAction) or [playing a message](https://api.vapi.ai/api#:~:text=SayPhoneNumberHookAction). Include these actions in the `do` array of your hook. + +**3. **Enhanced Call Tracking with endedReason**: When implementing call analytics, you can now track calls that ended due to hook actions through new `endedReason` values: +- `'call.ringing.hook-executed-say'`: Call ended after playing a message via hook +- `'call.ringing.hook-executed-transfer'`: Call ended after being transferred via hook +These values let you distinguish between different automated call handling outcomes in your reporting. \ No newline at end of file diff --git a/fern/changelog/2025-04-18.mdx b/fern/changelog/2025-04-18.mdx new file mode 100644 index 000000000..08b5dbd48 --- /dev/null +++ b/fern/changelog/2025-04-18.mdx @@ -0,0 +1 @@ +1. **Idle Message Count Reset in `Assistant.messagePlan`**: You can now enable `Assistant.messagePlan.idleMessageResetCountOnUserSpeechEnabled` (default: false) to allow the idle message count to reset whenever the user speaks. This means the assistant can repeatedly remind an idle user throughout the conversation.