Yeh, I looked at them. And we did a discussion in the discussion section about this.
A few things:
There is a bit of a mindset challenge. They think like a lawyer and try to sue everyone for crazy things. If you don't like your parking ticket, let's fight it... Exacerbating the same combative mindset that exists today.
The AI model I'm thinking through is the front end of the process -- collecting and interviewing the customer. From what I understand, they are using automation for the backend.
The business model makes it inaccessible. You have to pay a subscription to use the service.
All that said have you used the service? How do you like it?
That makes alot of sense, almost more geared towards more almost interview and advisory less "task" oriented like DoNotPay.
I have used them for various things to mainly try the service, it is pretty crazy everything that it can be used for and it's pretty straight forward to use. That being said, I can see alot of users having issues with the amount of data DoNotPay collects to fulfill it's services.
I am experimenting with the API to do deep subscription cancelling automatically.
I plan to use it, too, to understand the user experience. For example, if I want to request a payment or refund from a contractor who didn't show up, I want to learn about that experience.
Please share your observations about the subscription cancellation service, and I share my experience on the contractor case.
If you are interested in exploring the idea further with me, let's content too.
Hunter Yeagley
Yeh, I looked at them. And we did a discussion in the discussion section about this.
A few things:
All that said have you used the service? How do you like it?
Senior Product Manager @ Ramsey Solutions
That makes alot of sense, almost more geared towards more almost interview and advisory less "task" oriented like DoNotPay.
I have used them for various things to mainly try the service, it is pretty crazy everything that it can be used for and it's pretty straight forward to use. That being said, I can see alot of users having issues with the amount of data DoNotPay collects to fulfill it's services.
I am experimenting with the API to do deep subscription cancelling automatically.
That is a very good point on data collection.
I plan to use it, too, to understand the user experience. For example, if I want to request a payment or refund from a contractor who didn't show up, I want to learn about that experience.
Please share your observations about the subscription cancellation service, and I share my experience on the contractor case.
If you are interested in exploring the idea further with me, let's content too.