Maggie Battaglia

Thibaud Giovannetti 

I'm not sure if this will work for you, as well, but I was able to get this to work. 

One of our developers found that when generating the private key, we had to paste the full private_key and not the private_key_id. The private_key that was generated was a very long string of letters, numbers, and special characters, starting and ending with: "-----BEGIN PRIVATE KEY-----  and -----END PRIVATE KEY-----\n". 

Once I pasted the full string into the Private Key field, I was able to submit without receiving the error. 

Hope this helps!

I am running into a similar issue - after adding in the Project ID, Private Key, and Client Email, I receive a ‘Something went wrong, give it a moment and try again’ error. After inspecting the page, I see a push_credentials error with the status code of: 503 Service Unavailable. 

Wondering if there's a simple explanation for this error and a solution for how to fix this. Thanks!

We have 4 brands that we support with different customer types. Two of the 4 brands have customers we'd like to offer faster response times to and would like to customize, by brand, when new Messaging tickets are broadcasted to agents, especially since SLAs are not currently supported for Messaging. 

We have a view set up for all Messaging tickets, grouped by brand, but notifying agents via broadcast for a specific brand would greatly improve our prioritization and agent workflows.