Changelog

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.

Added: Editable Interview Questions (Email-Based)

Recruiters can now edit interview questions directly from the interview summary email, and the question coverage section now follows the exact order of the call for easier review.

How It Works

• 1) Editable Interview Questions (from the Interview Summary Email)
  Recruiters can now add, remove, and refine interview questions directly inside the interview summary email.
  Previously, interview questions were auto-generated from the job description and agent instructions, and recruiters could review the results but had limited ability to iterate.
  Now:
  - Recruiters can edit questions from the email using Edit Questions
  - Updates are saved at the job level, so future interviews for that job use the latest version
  - Changes are shared across recruiters, making it easy to collaborate
  - Each question shows who added it, so teams can track changes clearly
  This helps teams improve interview quality over time without rebuilding workflows.
• 2) Question Coverage Now Matches the Call Order
  The question coverage section in the interview summary email is now displayed in the exact order questions were asked and answered during the interview call.
  Previously, questions could appear out of sequence, which made interviews harder to review.
  Now, recruiters can read the interview summary from start to finish exactly as the conversation happened.

Why It Matters

These updates improve control, collaboration, and clarity during interview review.

• Recruiters can continuously improve interview questions without restarting the job setup
• Teams can collaborate across the same job with visibility into what changed + who changed it
• Interview summaries are easier to scan, understand, and compare
• Review is faster and reduces confusion when evaluating candidates