Why carrier claims stay manual
Carrier claims are pure admin: log in, copy the tracking number, copy the order value, upload the photo, submit. Most carrier portals have no API, so this work has stayed manual even on teams that automated everything else, and the customer waits while it sits on someone's list.
- Every portal has its own login and forms
- Each claim means copying data between tabs
- The customer waits until someone finds the time
How Yuma files the claim for you
With Web Actions, Yuma drives a real Chrome browser as part of resolving the ticket. You record yourself filing one claim, or upload a written procedure as a PDF. Yuma turns it into steps and learns which values change on every run.
When a damaged parcel ticket arrives, it opens the portal, signs in, pulls the order value and tracking number, attaches the customer's photo from the conversation, submits and writes the claim reference back to the ticket. No code, no selectors and no help needed from the carrier.
A crushed box and a claim nobody had to file
A customer emails a photo of a crushed box. Yuma replies with your damaged item policy, files the carrier claim in the portal with the photo attached, and adds the claim reference to the ticket. Your team never opens the portal, and the customer knows the claim is already in.
Benefits
01Speed
Hours of admin back
Claims are filed as part of resolving the ticket, so nobody copies data between tabs.
02Coverage
No integration project
If your team can do it in a browser, Yuma can too, with no API and no vendor help.
03Control
Tested before it goes live
A test run stops right before submit, and anything that blocks a run is reported to your team.
04Visibility
Full audit trail
Every run is logged step by step with a screenshot, linked to the ticket that triggered it.
Yuma
Step by step
- 01
Record the task
File one claim while recording your screen, or upload a written procedure as a PDF. - 02
Review the steps
Check the steps Yuma worked out and the values it will fill in on each run. - 03
Test it
A test run goes all the way to the submit button and stops, so nothing is sent. - 04
Publish
Once the test passes, the action becomes available to your playbooks. - 05
Run and review
Yuma files claims as tickets arrive and logs every run with screenshots.
