Quick question about triggering proactive web messaging notifications for past guests. While my gRPC service reliably ingests /api/v2/conversations/messaging webhooks, pushing a follow-up via the Guest API fails. A simple POST to /api/v2/conversations/messaging/messages carrying {"toId": "guest_123"} immediately yields 403 Forbidden.
- Extract
guestIdfrom inbound payload. - Authenticate endpoint call with service token.
- Observe
403 Forbidden.
Which Web Messaging SDK function handles re-engagement for expired sessions?