Changelog
See what's new with Whippy.
Added: Funnel Charts Can Follow the Same Contacts
Funnel charts in custom reports can now follow the same contacts from stage to stage, showing step-to-step percentages and an overall conversion rate when enabled.
What's included
- Follow the same contacts toggle: A new toggle in the funnel chart builder links each stage to the one before it, so every step reflects contacts who actually came from the previous stage. Off by default.
- Unique contact counting: When enabled, each stage counts unique contacts, even if a contact went through a sequence or generated a result more than once.
- Step-to-step percentages and conversion rate: With the toggle on, each stage shows what percentage of the previous stage reached it, and the legend displays a first-to-last stage conversion rate.
How it works
Turn on "Follow the same contacts" in the funnel chart builder to connect each stage to the one before it. Once enabled, each stage counts only unique contacts carried over from the previous stage, so the funnel never grows between stages, and percentages calculate automatically.
Why it matters
By default, funnel stages show unrelated counts with no connection to each other, which still works for some use cases. But when the toggle is on, conversion rate between stages become visible without manual calculation, and the funnel reflects how contacts actually move through a sequence or process.
Notes
- Off by default. Existing saved funnel charts are unchanged unless the toggle is switched on.
- Percentages and conversion rate only appear when this toggle is on, since disconnected stages would produce misleading percentages.
- Applies to funnel charts in custom reports only, not campaign goal funnels.
Fixed: Sender Name/Email Resolve in Previews
Test and preview emails now resolve Sender Name and Sender Email variables using the selected contact.
What's included
Sender Name and Sender Email fields now resolve contact variables in test and preview emails
Preview behavior for these fields now matches how body, subject, and CC/BCC already worked
Applies to previews across sequences, campaigns, and Send Email actions
How it works
When you send a test or preview email, Whippy now pulls the selected contact's data into the Sender Name and Sender Email fields, the same way it already does for the message body, subject, and CC/BCC. If your sender fields are mapped to custom data (for example, a recruiter's name and email address), the preview shows the resolved values for whichever contact you selected.
Why it matters
Previously, preview emails filled in the message content correctly but left Sender Name and Sender Email unresolved, showing raw variables instead of actual values. This made it look like personalization wasn't working, even though live sends were already resolving these fields correctly. Preview now reflects exactly what contacts receive, so teams can verify sender personalization before a campaign or sequence goes live.
Notes
This is a display fix for previews only. Live sends were not affected and already resolved Sender Name and Sender Email correctly.
Added: Custom Colors for Grouped Metrics
Custom metrics now support per-group color selection, so teams can keep colors consistent across dashboards and reports.
Previously, custom metrics used a fixed default palette. A group could show up as blue on one chart and green on another, making it harder to read dashboards at a glance or match reports to a brand's colors.
What's included
- Color picker per group: Each group in a metric's series can now be assigned its own color directly from the metric configuration.
- Support for donut, stacked, and distribution charts: Color selection works on donut charts, stacked bar charts, stacked column charts, and distribution charts.
- Colors saved with the metric: Once a color is set, it's stored with the metric and applied automatically everywhere that metric is used, across dashboards and reports.
- Reset to default: Any group color can be reset back to the default palette at any time, individually or all at once.
How it works
Open a metric's configuration and select Group By to enable grouping. From there, click Edit to access group colors. Each group can be set using the color palette or one of the suggested colors. Changes save at the metric level, so the same group keeps the same color on every chart where that metric appears.
Why it matters
- Consistent dashboards: The same color represents the same group everywhere, so teams don't have to relearn what each color means on every chart.
- On-brand reporting: Reports can be color-matched to a company's brand before they're shared with clients or stakeholders.
Setup
No setup is required. Custom colors are available now in the metric configuration for any grouped metric.
Notes
- Existing metrics are unaffected: Metrics keep the default palette until custom colors are set.
- Grouping is required: Color selection only applies to charts that have a Group By configured.
- Single-event charts only: Custom colors currently work on charts built from a single event. Multi-event charts are not yet supported.
Added: Duplicate Workflows
Whippy added the ability to duplicate any existing workflow directly from the workflow list, so teams can build new automations from a working template instead of starting from scratch.
What's included
- A duplicate action available directly from the workflow list
- Full copy of the original workflow's configuration, including steps, actions, and conditions
- The duplicated workflow appears in the list as a separate, editable workflow
How it works
From the workflows list, select the workflow you want to copy and choose duplicate. Whippy creates an exact copy of that workflow, including all existing steps, actions, and conditions. The new workflow is added to the list immediately, and you can rename it and update only the details that need to change for its new use case.
Why it matters
Building a complex workflow from zero takes time, especially when a similar one already exists. Duplication removes that repetition. Teams can reuse a proven workflow structure as a starting point and adjust only what's different, instead of rebuilding every step, action, and condition by hand.
Common use cases include:
- Duplicating a complex workflow and adjusting a few details for a new use case
- Reusing the same workflow structure across different campaigns or audiences
- Creating variations of an existing workflow without rebuilding it from the ground up
Notes
Duplicated workflows are independent of the original. Changes made to one do not affect the other.