We’re trying to send a proactive notification to a customer who had an abandoned web messaging session earlier today. The goal is to pop a message in their browser without forcing them to start a brand new conversation thread.
I’ve got the guestId and conversationId from our CRM logs. I’m using the standard web messaging SDK initialization in our custom agent desktop wrapper. Here’s the setup:
const client = new GenesysCloud.ClientAppSdk.GuestClient({
orgId: 'our-org-id',
guestId: storedGuestId,
conversationId: storedConversationId
});
When I try to call client.conversations.sendMessage(), the SDK throws a 404 saying the conversation isn’t found for this guest context. I suspect the session token expired or the guest object needs re-authentication via the /api/v2/conversations/webmessaging/guests endpoint first.
Does the Guest API support re-attaching to a closed conversation, or do I have to create a new one and link it manually via the previousConversationId field in the payload? The docs are vague on lifecycle recovery for proactive pings. Any pointers on the correct sequence of API calls to re-open that channel?