Problem
The queue analytics dashboard flagged abandoned webchat sessions last Tuesday. We’re pushing a proactive follow-up notification to those specific visitors. The admin UI tracks the engagement IDs perfectly. The Guest API keeps rejecting the payload though.
Code
const guestClient = new GuestClient({ orgId: 'acme-pacific', accountId: 'acct-7721' });
await guestClient.conversations.create({
type: 'webchat',
metadata: { previousEngagementId: 'eng-x9k2m', source: 'proactive_recall' }
});
Error
403 Forbidden: Engagement ID does not match current session context.
Question
The documentation mentions rehydrating stale sessions. The token refresh endpoint doesn’t accept archived IDs. We’ve tried passing the participant ID in the Authorization header. Nothing sticks. Need the exact header format for session rehydration.