A Better Way to Snooze

Muhsin K

Muhsin K

Published on

2 minute read

Snoozing conversations used to rely on a fixed set of options like tomorrow, next week, or selecting a time from a date picker. That worked, but it often meant extra clicks for something agents do frequently.

You can now type snooze times in plain language.

0:00
/0:35

Things like next tuesday at 2pm, in 3 hours, or end of the month are understood directly. The parser handles both relative and specific dates, so agents can quickly type what they mean instead of navigating a calendar.

For example:

  • If you’re waiting for a customer response later in the day, you can type snooze for 2 hours.
  • If you want to follow up next week, simply write Next Monday morning.

It’s a small change, but it makes snoozing faster and more natural during busy support shifts.

Other Updates

Security & Integrations

  • Each outgoing webhook now gets its own secret and includes three signed headers (X-Chatwoot-Signature, X-Chatwoot-Timestamp, X-Chatwoot-Delivery) so receivers can verify authenticity, reject stale requests, and deduplicate retries. Existing webhooks are backfilled automatically.
  • Stabilized webhook delivery for transient upstream failures.
  • Agent bots can now toggle typing indicators.
  • IMAP authentication failures now return proper authorization errors
  • Captain assistant traces in Langfuse now include channel type metadata..

Conversations & Workflow

  • Private notes no longer trigger new message notifications. If someone is explicitly @mentioned, they'll still get notified.
  • Added priority + created at sorting for conversations.
  • Assignment policy name now appears in auto-assignment activity messages.
  • Bot handoff now correctly sets waiting time.
  • Disabled the reply editor for API channel conversations outside the 24-hour response window.
  • Conversation continuity setting is now available for Telegram, TikTok, Instagram, Line, WhatsApp, and Facebook.

Channels

  • When an agent replies from Slack and their email doesn't match a Chatwoot account, the message now shows the Slack user's display name and profile image instead of "Bot."
  • Messenger native-app echoes are marked correctly as external echo messages.
  • Added a Captain-powered CSAT template analyzer for WhatsApp that predicts whether Meta might reclassify a Utility template as Marketing, explains the risks, and suggests safer rewording before submission. Manual and button-triggered.

Performance

  • Replaced vue-virtual-scroller with virtua for chat list rendering—smoother scrolling, especially on long lists.
  • Filter endpoints now use the search API internally for faster results.
  • Rate-limited Meta endpoint calls to 30 per minute per user to prevent throttling.

Settings & UX

  • SMTP validation now returns specific error messages for authentication failures, connection issues, SSL/TLS errors, and unreachable servers instead of a generic failure message.
  • Categories can now be reordered via drag and drop.

Thanks to everyone reporting issues and sharing feedback.