Hello Pinterest Business Community!
Our team is currently hard at work redesigning our Pinterest Help Center—if you’re not familiar with it, the Pinterest Help Center is the place to quickly get answers to your questions, learn how to use Pinterest and troubleshoot issues. In addition to updating brand colors and restructuring articles and topics, the team wants to hear from the people who use it, people like you!
Whether you’re an avid user or you’ve never used the Pinterest Help Center (but have ideas of what you’d like to see), we’d love your thoughts. Below are some questions to help guide your thinking, but please feel free to share any ideas you may have.
Anything else? We’re all ears! Thank you in advance for your time and for helping to make the Pinterest community better for everyone. ❤️
Hi everyone, we've heard the feedback that you've shared in this post about wanting more transparency from the Pinterest team about improvements, changes and updates we make to Pinterest products and tools.
We're excited to announce that we've just rolled out a new product release note series on the PBC that will be shared monthly. If you have a moment, take a peek at the article and please share any feedback you have about the changes or your thoughts on this new format. Thank you, we appreciate you!
I think transparency about current issues and fixes the engineering team/product are working on would save both creators and the customer support team lots of time and hassle. If there's a known issue it would be great if there was a place that listed this as well as it's expected fix time. 🙂
1. Support often does not answer the actual question. I had one ticket that took 11 emails because the "second level" support person simply refused to read the question. He gave me multiple and repeated "canned" answers that did not address the actual question. This also occurred with first level support on another issue I had. The response was a "canned" answer and it was fairly unrelated to the actual issue I asked about.
2. Randomly closing tickets without a resolution. Then I have to start a new ticket.
3. DMCA "strikes" - This process needs to be revamped. When a blogger gets a strike because they re-pinned a pin that showed up in their feed that turns out to be stolen. When the rightful owner comes along and finds it, they file a DMCA, the "strike" goes against the blogger who simply re-pinned it INSTEAD of the account that created the stolen pin. I know (now) that ever single link has to be checked first (ridiculous) before re-pinning. The platform is supposed to be a place where interesting finds can be saved, but the risk is too great. BUT - There is no process to dispute a strike if you are not the "copyright owner" of the pin. There should be a process in place where in the above scenario, the strike is removed against the innocent blogger and applied to the spam account who created the stolen pin. ALL STRIKES should go against the account who created the stolen pin. Period.
If I think of any more, I'll add, but those are the top 3 issues I've experienced with Support.
And the other problem is submitting a ticket!
I followed your link -- spent considerable time collecting the info and inputting into the form. The form only allows for one file upload so I had to combine my screen shots into one form. Hit the submit button and it gave me an error message that it didn't go through and told me to send to the zen desk. So again I spent time reconstructing the problem uploading the screen shots -- and received a robo response telling me to submit a ticket if the suggestions were not helpful -- clear cache, etc.
So again I submitted through the help form and this time it went through only send me another email telling me clear cache, etc. or email back for human help. I replied back that I need human help. Yet another email back with the robo suggestions and if I still need help to reply back for human help!!!!
Thank you for the feedback, everyone! I've been sharing all of this with our team for consideration. Your input is much, MUCH appreciated. ❤️
Hey @troprockin we're sorry to hear you find this experience frustrating.