Changelog
See what's new with Whippy.
Added: Call Transfer Handoff Notes & Context Labels
Agents can now attach a note and see who transferred a call before they pick up.
What's included
- Optional transfer notes: agents can add a plain-text note explaining the reason for a transfer before sending the call
- Automatic sender labeling: every transferred call displays a "Transferred from [Agent Name]" badge, even when no note is added
- Support for both warm (attended) and cold (blind) transfers
How it works
When transferring a call, agents can type a short note into the transfer panel, for example, "Customer wants a refund on last month's invoice". The receiving agent sees this note along with a badge showing who sent the call, right on their incoming call card, before they answer.
Why it matters
Agents previously received transferred calls with no context, which meant customers had to repeat their issue and re-introduce themselves to every new agent. With handoff notes and context labels, receiving agents know who's calling and why before they pick up, so customers get answered faster and don't have to explain themselves twice. This is especially useful for teams routing calls between frontline support and specialists in Whippy's VoIP platform.
Setup
No setup required. Handoff notes and context labels are available by default on all warm and cold transfers.
Notes
Transfer notes are plain text only and are visible only to the receiving agent, not the caller.
Added: Notion Workflow Integration
You can now read and write Notion pages, databases, and files inside Whippy workflows. The first release ships 40 actions and 32 webhook triggers, with no custom API calls or manual OAuth setup.
What's included
- Pages and content:
- Search, get, create, and update pages.
- Update database properties with Update Page, and update the page body with Update Page Markdown. They are separate steps, so you map structured fields and narrative content to the right place.
- Append or edit blocks, and move or trash pages.
- Databases and data sources:
- Query rows, create entries, and read or update schemas.
- Work with databases, views, and templates.
- Files:
- Upload and Attach File takes a file from an earlier step, such as an Email Parser attachment, and lands it on a page as a real attachment, not a broken link.
- Comments and users:
- List, create, update, and delete comments, and look up workspace users.
- Triggers (32):
- Fire a workflow on events such as page created, updated, deleted, or moved, plus content changes, new comments, and new database entries.
How it works
Connect your workspace once through OAuth, then drop a Notion step into any workflow, pick an action, and map fields from the previous step in the same builder you use for messaging and agents. You choose exactly which pages and databases the connection can access.
Why it matters
Teams keep their source of truth in Notion: runbooks, weekly updates, customer notes, project trackers. Now you can push a formatted Linear or LLM summary straight into a database row every Friday, move an email attachment onto the right page, or trigger a workflow when a page changes and notify Slack.
Setup
- In Whippy: add a step, then App → Notion → Connect, and authorize through OAuth.
- In Notion: share the pages you need with the connection (page menu → Add connections).
- For triggers: create the webhook subscription in your Notion Developer Portal, then paste the callback URL from your Whippy workflow trigger when you publish. Trigger setup is a one-time configuration on both sides, per workflow.
Added: Calendly Workflow Integration
Whippy added a native Calendly app to its workflow builder, so teams can trigger automations the moment a meeting is booked or canceled and take action on Calendly data without leaving the workflow editor.
What's Included
Three real-time webhook triggers:
- Invitee Created: a prospect books a meeting
- Invitee Canceled: a booking is canceled
- Routing Form Submission Created: someone submits a Calendly routing form
Plus 56 additional steps to read, create, update, and delete Calendly data, including scheduled events, event types, invitees, availability, scheduling links, contacts, routing forms, webhooks, and more.
How It Works
When a trigger fires, the workflow has immediate access to the booking details. From there, it can enrich the contact, notify the team, update the CRM, or take any action available in Whippy Workflows.
Example: A prospect books a demo. The workflow enriches their profile via Apollo, sends that data to OpenAI to generate a short host prep note, and posts everything to Slack. The team sees who booked, when the call is, and context for the conversation before they ever open their calendar.
The same trigger can also update Whippy CRM, send an SMS or email, or chain additional Calendly steps like fetching event details or updating contact records.
Why It Matters
Acting on a Calendly booking used to mean checking an email notification, manually looking up the prospect, pinging the team, and writing prep notes. A process that worked fine until it got busy and steps got skipped.
This integration makes that entire sequence automatic and consistent, regardless of how full the day is.
Setup
- Go to Integrations → Calendly in your Whippy account
- Connect with a Calendly Personal Access Token
- Add a Calendly trigger or step to any workflow
- Publish. Webhook triggers register automatically.
Notes
- Webhook triggers require Calendly Paid Plan
- OAuth 2.1 support is planned for a future release
Improved: Faster Long-Timeframe Agents Reports
Agents reports over extended date ranges now load significantly faster, eliminating slow load times for ranges longer than 3 months.
What's Included
- Reduced load times for standard Agents reports under Reports > Agents
- Improved performance across any date range longer than 3 months, including custom ranges selected via the date picker
- No changes to report structure, data, or navigation. Same workflow, faster results
- Full backward compatibility: shorter timeframes are unaffected
How It Works
Open Reports > Agents and select any date range of 3 months or longer, including custom ranges up to a full year. The report loads promptly without stalling or timing out, regardless of how much AI call data your account has accumulated.
This applies to the built-in Agents reports only.
Why It Matters
Long-timeframe reporting on AI agent performance was previously unreliable for analysis workflows on large datasets. That made it impractical to track trends across quarters or identify seasonality patterns without significant waiting.
This update makes extended-range reporting reliable and on-demand. Teams can now pull a full year of agent performance data in the same time it previously took to load a single month, supporting faster decisions without workarounds.
As call history grows over time, report performance stays consistent rather than degrading.
Setup
No setup required. The improvement is applied automatically. There is nothing to configure or enable.
Notes
- Applies to standard Agents reports under Reports > Agents only
- Existing report filters, date pickers, and data remain unchanged