Changelog

Added: Location-Specific VoIP Notification Preferences

Granular notification control per channel.

How It Works

We added channel-specific notification preferences that let users manage alerts on a per-channel basis. Notification settings now live on the relationship between a user and a channel, instead of being applied globally.

Previously, notification preferences were shared across all channels. Users could not mute one office without muting all of them. With this update, each channel (office, branch, or location) can be configured independently.

If no preference is set for a channel, the system defaults to the standard global settings.

Why It Matters

For multi-channel teams, notification overload reduces focus and productivity. This change gives users precise control over when and where they receive VoIP alerts, without affecting other active channels.

Teams can now stay responsive where it matters most and quiet where it doesn’t.

Key Benefits

• Reduced noise: Recruiters and managers only receive notifications from the channels they actively manage.
• Better user experience: Notification settings are no longer “all or nothing”.
• Scalable by design: As organizations add more channels, notification streams stay relevant and manageable.

Publisher Attribution for Knowledge Base Versions

Each knowledge base version now records who published it.

How It Works

Whippy now captures and displays the user who publishes each knowledge base version. When a version is pushed live, the system automatically records the publisher and associates that user with the published version. This happens at the time of publishing and requires no changes to existing workflows or permissions.

For versions published before this update, publisher details may not appear because that data was not previously tracked.

Why It Matters

Teams often collaborate on knowledge base content, with one user drafting and another approving or publishing. Previously, there was no reliable way to see who actually published a version. This update improves visibility and accountability by clearly showing who pushed each version live, which helps with audits, content reviews, and internal ownership.

This change supports better content governance across shared knowledge bases and aligns with Whippy’s focus on clear, trackable communication management.

Added: Unified User Avatars with Presence & Status

User avatars were unified across Whippy to clearly show who is available, on a call, or away without opening user profiles.

How It Works

Whippy now displays a single, consistent user avatar everywhere the team collaborates.

• Avatars show a profile photo when available or user initials when not.
• A live presence indicator appears directly on avatars in conversations, assignments, activity logs, and tables.
• Hovering over an avatar shows the user’s current status when enabled, including Available, On a Call, or Away, along with any custom emoji or status message.

Presence color legend:

• Green indicates the user is available and online.
• Orange indicates the user is currently on a call.
• Grey indicates the user is away or offline.

This update applies automatically and does not require setup or configuration.

Why It Matters

Clear presence indicators reduce guesswork during collaboration.

• Teams can route conversations and assign work faster.
• Busy inboxes are easier to manage with immediate visibility into availability.
• The interface stays consistent and easier to scan as teams grow.

This change improves day-to-day collaboration across Whippy while keeping the interface simple and predictable.

Added: Rollback Functionality for Knowledge Bases

You can now roll back an entire knowledge base to any previously published version without changing what’s live right away.

How It Works

You can select any published version of a knowledge base and roll back to it. When you choose a version, the system creates a new draft based on that version.

From there, you can:

• Review the restored content
• Make edits if needed
• Publish when you are ready

Rollback does not immediately replace the live knowledge base. The live version stays active until you publish the draft.

Why It Matters

Knowledge bases change often, and mistakes happen. This update added a safer way to manage content updates and keep customer-facing information accurate.

Rollback helps you:

• Undo incorrect or unwanted edits
• Restore a stable version after a problematic update
• Control what goes live with a draft-first workflow
• Reduce risk when updating support content, FAQs, or internal documentation

If you use Whippy’s knowledge base to support AI conversations, customer support, or automated messaging workflows, rollback gives you a more reliable way to maintain version control and content quality.