Trying to get the Web Messaging SDK to fire a active notification for a user who chatted with us last week. The docs are vague on how to link a new SDK session to a historical guest ID without forcing a full re-auth flow.
I’m using the genesys-cloud-messaging-widget v2.4.0. I have the guestId from the previous conversation logs, but when I initialize the widget, the active trigger never fires. It just sits there waiting for the user to type first.
Here’s the init config:
const config = {
organizationUuid: 'my-org-uuid',
guestId: 'prev-session-guest-123',
active: {
enabled: true,
trigger: 'onReady'
}
};
MessagingWidget.init(config);
The console shows the widget connects fine, but no active message appears. I’ve checked the routing settings and the active campaign is active. Is there a specific API call I need to make to ‘warm up’ the guest session before the SDK will respect the active trigger? Or am I missing a param in the init call? The standard sendProactiveMessage endpoint requires an active session ID, which I don’t have yet.