In my experience, Manus ultimately failed to solve the most serious problem I encountered.
A service like this should protect continuity of work and provide reliable recovery when critical data is missing. Instead, when my business-critical project data and credits were affected, I received no clear technical resolution, no accountable case ownership, and no meaningful recovery outcome.
What was especially concerning was the lack of basic customer-case management. Even my formal support email remained without confirmed review, while the support process repeatedly asked for more evidence and then closed conversations before the underlying issue was resolved.
For me, the practical benefit was therefore undermined by the company’s inability to handle a serious data-loss incident responsibly. A tool that can help create business assets but cannot reliably support customers when those assets are at risk does not solve the core problem I need solved. Review collected by and hosted on G2.com.
This was one of the worst customer support experiences I have ever had. I have never seen a paid service repeatedly close support conversations in the middle of an unresolved case when the questions became difficult. My business-critical startup assets and credits were lost, yet after a week of submitting evidence, no one took clear ownership or provided a technical explanation.
I followed Manus’s official backup process exactly as instructed. The system showed the backup as completed, but the Task Data required for restoration was simply not there.
I then spent about a week dealing with Manus Support and submitted everything they requested:
screenshots
backup file details
OneDrive evidence
restoration status
screen recordings
project information
credit-loss evidence
And still, no one gave me a clear technical answer to the most basic question:
Why did Manus show a successful backup if the required Task Data was never actually available?
The support process made the situation even worse.
Two separate support conversations were closed while the issue was still unresolved. In one case, I was told to perform additional checks and reply, but the conversation was closed before I could continue. After reconnecting and submitting even more evidence, the second case was also closed without resolving the underlying problem.
In the end, I was told that Manus had informed users to back up their data.
That response is absurd in my case because I did back up my data. I followed Manus’s own instructions and relied on Manus’s own “completed” status.
What I lost was not some disposable test file. It was business-critical startup work, project history, development decisions, and credits built up over time.
After a week of fully cooperating, I was left with:
no Task Data
no technical explanation
unresolved lost credits
two prematurely closed support conversations
no meaningful resolution
no clear person or team taking responsibility
I am preserving the full evidence trail, including screenshots, videos, backup files, emails, and support transcripts, and I am now preparing to pursue this through formal channels.
At this point, this looks much more serious than an isolated inconvenience.
If multiple users followed the official backup process, saw “completed,” and still ended up without their Task Data, Manus needs to explain what failed in the backup/export system instead of pushing the issue back onto users. Review collected by and hosted on G2.com.