Crisp
COMMS
Velocity0.0
Customer messaging and live chat platform
Crisp ships RTM API events for verification and unread acknowledgement; the visible feed is docs-only and sparse.
customer messagingrtm apiidentity verificationintegrator surfacelow cadence
◆Current state
Three new RTM API events shipped in a single batch on February 11: identity:verify:request, session:updated (with the verification list), and message:acknowledge:unread:send. Each lets integrators react in real time to verification or unread state without polling. The fourth entry is a truncated August 2025 version of the identity-verification event.
◆Where it's heading
What's visible is Crisp quietly extending its real-time API surface for integrators rather than shipping user-facing features. Whether the customer-messaging product itself is moving — AI assistance, channel additions, automations — isn't visible from this docs feed.
◆Prediction
Expect more incremental RTM events as integrators request hooks. To read product direction we'd need to re-point the source to the release blog or product-news feed; this docs surface won't show user-visible changes.
◆Recent moves
- 4mo ago
RTM event added: identity:verify:request
New RTM event identity:verify:request fires when verification is requested for a conversation. Useful for plugin authors who need to surface verification prompts in third-party integrations without polling.
View source ↗ - 4mo ago
RTM event extended: session:updated with verification history
session:updated now carries the past-and-current verification list when a conversation is marked verified. Closes the verification-history gap for integrators handling compliance flows.
View source ↗ - 4mo ago
RTM event added: message:acknowledge:unread:send
New RTM event message:acknowledge:unread:send for when a conversation is marked unread. Useful for integrations that mirror conversation state into ticketing or analytics systems.
View source ↗