Changelog

See what's new with Whippy.

Added: Fax Channel Onboarding

Whippy dashboard showing ‘Create New Channel’ setup (Step 2 of 5), with channel type options including Phone, Email, WhatsApp, Messenger, Instagram, and Fax selected, plus a Next button to continue.

Whippy now supports fax as a dedicated communication channel: send and receive faxes directly from your Inbox, alongside SMS, voice, and email.

What's Included

  • A new Fax Channel option available in the Whippy Dashboard
  • Two onboarding paths: Custom and Whippy Managed
  • Ability to select a local phone number during setup
  • Fax sending and receiving from the Whippy Inbox immediately after onboarding
  • Support for PDF and TIFF documents, including signed forms and case files

How It Works

Fax channel onboarding follows the same familiar setup flow used by other Whippy channels. During setup, you choose one of two configuration paths:

  • Custom: Connect your existing Telnyx account using your API key and public key. Best for teams that already manage their own Telnyx integration.
  • Whippy Managed: Whippy handles the full configuration, including purchasing a dedicated phone number and setting up the fax service. No Telnyx account or technical setup required.

Once onboarded, the fax channel is live. You can select a number in your preferred area code and start sending and receiving faxes within the same session.

Why It Matters

Fax remains a required communication method in industries like healthcare, legal, and logistics, where signed documents, case files, and compliance forms are still transmitted by fax daily.

Previously, teams in these industries had to manage fax outside of their main communication stack. Now, fax lives alongside SMS, voice, and email inside Whippy, keeping all outreach and document exchange in one place.

This is especially relevant for teams that need a dedicated local fax number, like a pharmacy receiving signed prescription forms, without adding another tool or vendor to their workflow.

Setup

  1. Go to your Whippy Dashboard
  2. Navigate to Channel Settings and select Add Channel
  3. Choose Fax from the available channel types
  4. Select your onboarding path: Custom or Whippy Managed
  5. If using Whippy Managed, choose your preferred area code and confirm your number
  6. Save and start sending faxes from your Inbox

Notes

  • The Custom path requires an active Telnyx account with a valid API key and public key on hand before starting setup.
  • Faxes are sent and received as PDF or TIFF files through the Whippy Inbox.
  • Both onboarding paths are available to all eligible Whippy accounts. Contact Whippy support if you need help choosing the right path for your team.

Changed: Clearer Transcript Tool Call Display UI

Whippy call analysis screen showing an AI agent transcript where a candidate confirms requiring U.S. work sponsorship, followed by an automated rejection message and an audio playback bar.

We improved the transcript interface to make tool calls easier to read and understand.

What’s included

  • Structured display of tool calls in chat and call transcripts
  • Clear separation of tool name, input, and output sections
  • Collapsible views for expanding or hiding details
  • Syntax-highlighted JSON for better readability
  • Cleaner layout for scanning AI interactions

How it works

Tool calls now appear as structured blocks inside transcripts. Each block shows the tool name, followed by clearly separated input and output sections. Users can expand or collapse these sections as needed. JSON responses are formatted and syntax-highlighted to improve visibility and reduce parsing effort.

Why it matters

This update reduces time spent reading raw JSON and improves clarity when reviewing AI actions. Teams can quickly understand what the AI executed, what data was passed, and what results were returned. This supports faster debugging, better auditing, and improved workflow visibility across messaging and voice interactions.

Notes

  • This update applies to both chat and call transcripts
  • No changes are required to existing workflows or integrations
  • The improvement is available automatically within the platform

Added: Audio & Video Support in Knowledge Bases

Modal window titled “Create Page” in Whippy showing a form to add a knowledge item, with fields for name and item type, and a dropdown expanded with options including Text Content, Document Upload, Audio Upload (selected), Video Upload, Single Webpage, and Website.

You can now upload audio and video files to your Knowledge Base and use them in AI-powered responses.

What’s included

  • Upload support for audio files (up to 100MB)
  • Upload support for video files (up to 200MB)
  • Searchable content available in AI responses and workflows

How it works

Upload audio or video files to your Knowledge Base and publish it.

After publishing, the system generates a transcription and indexes the content so it can be used in searches, automations, and AI responses.

Why it matters

Important knowledge often lives in recordings like demos, trainings, and calls.

This update makes that content searchable and usable, helping your team:

  • Access information faster
  • Improve response accuracy
  • Reduce manual documentation

Notes

  • Audio files: maximum 100MB
  • Video files: maximum 200MB
  • Transcription starts after the Knowledge Base is published

Changed: Dynamic Form Submission Email Routing

Whippy form builder interface showing submission settings, including submit button text, thank-you message fields, and email notification toggle, with draggable form elements like input, email, and phone number on the left panel.

Form submission notifications now support dynamic recipients using contact custom data, allowing emails to be routed based on contact ownership or synced fields.

What’s included

You can now configure notification recipients using static and dynamic values. This update:

  • Adds support for dynamic email recipients using contact custom data
  • Allows combining static email addresses and dynamic placeholders
  • Removes the need for external automation or custom integrations

How it works

When a form is submitted, Whippy reads the contact record and resolves any dynamic fields into email addresses.

You can define recipients as:

  • A standard email address
  • A dynamic field (for example, recruiter or owner email stored in contact data)

Notifications are then sent to all valid recipients, combining both static and dynamic values.

Why it matters

Notifications are now sent based on who is actually responsible for the contact, not just a fixed list.

  • Improves accuracy of form submission alerts
  • Reduces manual routing and dependency on third-party tools
  • Supports scalable email notification automation workflows

This is especially useful for teams using CRM or ATS data to manage ownership and assignments.

Notes

  • Dynamic fields must contain a valid email address
  • If no value is found, that recipient is skipped
  • Static and dynamic recipients can be used together