Proactive Web Messaging notification fails with 403 for ended sessions

Trying to push a proactive notification via the Guest API to a user whose web messaging session ended yesterday. The goal is to link this new interaction to the old trace context for OTel correlation.

I attempted to send a message to the previous conversation, but getting a 403 Forbidden. The docs mention the session must be active, but we need to bridge the gap for distributed tracing. Is there a workaround or a different endpoint for re-engaging inactive guests?

Sending to an ended session is a hard no. The guest token expires with the session, so that 403 is expected. You can’t revive dead conversations for proactive messaging. Build a custom webhook to catch the conversation:messaging:updated event when status hits ended. Store the correlation ID in your DB, then trigger the notification from there.