We were getting this error in the submission of one of our outbound Marketing forms.
Activity id: e1ede147-efb6-457d-bc19-826c6176a2e4, Request id: jH7xRiEzGFTdZQTbE2fkh9_Z_WtjumCqJERuYZbGSL0_0, Exception: Entity ‘Contact’ With Id = 896b960d-c5d7-4c4d-95c7-a9e226afbf8e Does Not Exist
The form had only the Lead form matching defined and Only leads for Update contacts / leads.
So here because of some earlier multiple/different form submissions, a contact got created and stored in the browser’s cookie, which CRM was referring to, and trying to set a Parent Contact for the lead record even though we were having Only leads set for update contact/leads option.
Enter Account SID and Authentication token click on Next
Next, we need to add the WhatsApp Name and Phone number
Navigate to Messaging >> Try it out >> Send a WhatsApp message to activate the WhatsApp Sandbox.
Follow the steps there to configure the Sandbox account. (scan the QR code send the Message, and test the Business and User-Initiated message/conversation).
Click on Sandbox setting tab to get more information
Copy the number.
Add the number and click on Next
Copy the URL
Paste that URL in the When a message comes in and save.
We can see our WhatsApp account created, open the record.
We can see our number being shown as Active
With the account active time to now it is time to set up the channel/workstream / queue.
Navigate to Customer Support >> Channels >> Messaging (Manage)
Click on Add Channel and add the details
Enter channel details
We are creating a new workstream
Add the WhatsApp number added
Select the language
Specify the Behaviour (automated messages and approved templates)
Specify the user features (attachments)
Review and Finish and Create the channel.
Open the workstream and specify routing rule/fallback queue/work distribution/associate bots etc details
We will create a ruleset to route the message to the queue
We have the below route-to-queue rule created to route to the default queue which has all the omnichannel agents added to it. (In an actual scenario, we would add the conditions and create a specific Advanced Queue).
We are leaving the rest of the settings/configuration as default.
Now is the time to test.
Let us log in to the Customer Service Workspace as an agent and from the registered sandbox participant number added send a message.