Removes work · Pilot-ready
Schedule-change queue work
Clear airline schedule changes from the queue: classify, protect, notify, reissue.
For tmcs, airline crew travel desks, staff travel.
- 1Reads each schedule-change message and classifies it: minor time change, misconnect or cancellation.
- 2Finds protection under the fare rules and the airline schedule-change policy.
- 3Notifies the traveler or the crew desk with the options, in your wording.
- 4Reissues the ticket once accepted and records the acceptance.
- 5Escalates the cases the policy reserves for people, with the facts gathered.
Five steps, one branch to a person.
- 1
Change received
- 2
Classify impact
- 3
Find protection
- 4
Notify and accept
- 5
Reissue and log
Branch to a person: Involuntary refunds. Reroutes outside the airline policy. Crew changes that touch legal rest or duty limits.
What it reads, who signs off, what we count.
- GDS queues and schedule-change messages
- Fare rules and airline policies
- Traveler and crew profiles
- Roster and legal-rest constraints for crew
- Involuntary refunds.
- Reroutes outside the airline policy.
- Crew changes that touch legal rest or duty limits.
- Queue items cleared per day
- Time from change to traveler notice
- Reissue errors and resulting debit memos
Time to shadow mode
4 weeks
From the day the 50 files arrive to the agent running beside your team.
Production, processing workflows
$2 to $6 per document
Reconciliation, schedule changes and claims. Priced per file handled, with a monthly minimum of $3,000. No platform fee. Full pricing
The API behind this workflow
For crew travel, schedule changes can enter through the Crew Travel API. For TMC queues the agent works in the GDS directly.
How schedule-change queue work goes live
- 1
Week 1
Pick the workflow and the owner
One workflow your team already runs, with its documents, systems and written rules, one owner on your side, and one number that decides whether it worked.
- 2
Weeks 1 to 2
The 50-file test
Fifty closed files with known outcomes, graded blind by two of your people. We write the agent without looking at them, run it, and report false positives and false negatives against the human baseline.
- 3
Weeks 3 to 8
Shadow mode
About 100 new files run beside your team with no answers given. Your team compares weekly. The test set stays closed while we tune, so the agent is never fitted to it.
- 4
Weeks 9 to 10
Run alone on the cases it has earned
The agent finishes the routine cases alone. Every batch is stamped with the policy version and can be undone. Exceptions go to a person with the facts gathered.
- 5
After go-live
Eight-week error watch
Every finished case is checked for eight weeks, then a sample. Every correction joins the test set. The error rate is reported to the owner weekly.
The other five.
Hotel folio reconciliation
Chase, read and itemize every crew hotel folio, check it against the contract, and raise the dispute.
See the workflowCrew hotel invoice audit
Match every invoiced room night to a crew booking and the contract, and recover what was overbilled.
See the workflowUnused ticket and credit recovery
Track every unused ticket, credit and voucher, and apply it before it expires.
See the workflowAgency debit memos
For airlines: find violations and issue the memo. For agencies: build the dispute and win it.
See the workflowPassenger compensation claims
Decide EU261, UK261, APPR and US refund claims under your written policy, and pay within limits.
See the workflowSend us 50 closed files.
Fifty closed schedule-change queue work cases under NDA. Within two weeks you get the agent’s error rate against your own team and, for recovery workflows, the dollars it would have found. No charge.
- NDA first
- Two weeks
- The report is yours