How to file a class action claim without getting redirected

Why redirects happen

Settlement filing usually happens on administrator-run websites. Many apps stop at discovery and simply send the user there to finish the process. That keeps the app lighter, but it leaves the hardest part of the experience untouched.

Why the redirect is such a problem

The redirect sounds small until you are the person filing. It usually means a new page, a new layout, more retyping, and a higher chance that the user simply stops before finishing.

That is why the real product problem is not just finding claims. It is getting people through the form cleanly once they decide to act.

What a better filing path looks like

• - the user stays in one product flow
• - the official settlement form still opens
• - less retyping is needed
• - fewer context switches happen right before submission

That is the difference between a discovery tool and a true filing product.

What Oyster is trying to do differently

Oyster's product direction is simple: the official settlement form opens inside the app. That keeps the filing path tighter and more believable than the usual "tap here, now go somewhere else" flow.

That does not eliminate every kind of filing friction. Some claims still need notice IDs, proof, or other credentials. But reducing the redirect is still one of the clearest improvements an app can make.

Why this matters for trust

When a product says it helps you file but immediately sends you away, the promise and the experience do not match. That gap matters. In settlement products especially, people already have reasons to be skeptical.