Genesys Cloud CX (formerly PureCloud)

Discussion Thread View
Expand all | Collapse all

Parse customer details to WebMessaging

  • 1.  Parse customer details to WebMessaging

    Posted 6 days ago
    As there is no 'pre-registration' form inside web messaging vs web chat.  The next best thing would be an intent asking for 3 slots, first name, last name and email.
    Is there some way to parse those details collected in a botflow to the queue?
    The end goal of course being so the customer in the webmessaging interaction ie Jane Doe, will automatically be linked to an external contact so the agent can check customer history accross channels.

    Daniel Buxton
    Acquire BPO

  • 2.  RE: Parse customer details to WebMessaging

    Posted 4 days ago

    If you have some mechanism to collect first name, last name, and email then you can use the "Search External Contact" block to see if an external contact exists for that web visitor.  If one or more external contacts are found then you'll have to figure out which one to select and use that External Contact ID.  If one does not exist then you'd have to use a Genesys Cloud Data Action ( to call POST /api/v2/externalcontacts/contacts to create an external contact and get the returned Eternal Contact ID.

    Once you have an External Contact ID that matches your web visitor then you'll need to use another Genesys Cloud Data Action to call PUT /api/v2/externalcontacts/conversations/{conversationId} to link that external contact to the messaging conversation.  There should be a variable available called messaging.conversationId (or something like that) to identify the conversation and you'll have the external contact id from above.

    I hope that helps.

    Jim Crespino
    Senior Director, Developer Evangelism