Step one: the portal team dropped the Web Messaging SDK widget onto the account page, and we’re trying to shove the CRM customer ID into the session before it hits our Studio flow. The startChat() call goes through without throwing, but the ID vanishes by the time the contact reaches the SNIPPET action.
They’re passing the attribute like this:
await client.startChat({
customAttributes: { crmCustomerId: "CUST_99887" }
});
We’ve got the Studio attribute map pointing at customAttributes.crmCustomerId, so the wiring should be good. The flow drops into a SNIPPET action immediately to fetch account status via REST Proxy, but the ASSIGN block is returning null because the attribute isn’t populated. Adding the ID to the routingData object didn’t stick either. The SDK version is 4.2.1.
Is the customAttributes object supposed to be nested deeper? Or maybe the key needs to be snake_case? The docs mention guestAttributes in one place and customAttributes in another, and it’s confusing. Also checked the network tab. The chat:start message comes back with a blank payload. Something obvious is getting lost here.