Should We Use Vocal Stories To Highlight Platform Issues?

Introduction

This is a result of some recent issues that have not been platform-wide on Vocal, but have severely affected some creators who are Vocal Plus members, and therefore pay for a service.

So What’s Happened

Vocal got hit by another Denial of Service attack and finally set up a Status page (which I had been publicly advocating for years, and they published this story about it. That was something that affected all creators and Vocal itself, so something was done about it.

And this is where I advocated this last year:

As I write this, I am on the fourth day of being unable to post on Vocal due to a system error. I have raised a ticket, put a website error message on Discord and emailed Vocal about my problem. At this point I have received no response.

Recently, Jay Kantor lost everything (thankfully restored now) and Mark Gagnon has been having issues. Judey Kalchik highlighted this on Discord, but there seemed to be no response.

This is the email I sent

I Am Unable To submit any Vocal Stories

Mike Singleton

to Vocal

This has been the situation for two days.

I have raised a ticket and put a question on Discord.

When I save, I get this

Also, my page 301 of my stats is not being picked up by the system.

Sometimes the story appears in drafts, but when I try and access I get this

I am paying for my subscription and if this is not fixed I will go public with it and cancel my subscription.

Given all the support I have given Vocal over the years I find this behaviour very unprofessional

Mike Singleton

Conclusion

I am not happy with this situation and am sorry I have to resort to this backup account.

The only way Vocal might see this is if it gets on the leader board, but as this is a backup account, I know that is unlikely.

This is an update with the Zendesk replies to three of my enquiries on this

And the lack of response on Discord

Thank you for reading.