Know what a trip costs before it’s booked.
Your team already asks for flights in Slack. Rally answers there — priced against the cap you set, revalidated before it books, and written to a ledger you can open any day of the month.
Illustrative thread. Sample fares and cap.
One place travel gets asked for
No portal logins, no request forms, no EA acting as a search engine. The channel your team already uses is the booking tool.
Caps enforced before the spend
Rally only shows options inside the trip cap, and revalidates the fare at the moment of booking. Approval stops being a bottleneck.
A ledger, not a card statement
Every booking writes itself down: traveller, destination, department, dollar — the same minute it happens.
Where the money went, by department.
Open it mid-quarter and the number is already right. Nothing to reconcile, because the booking and the record are the same event.
Spend by department
Northbeam · this quarterSample data shown.
Four messages, start to booked.
Rally reads the request, does the searching, and waits for an explicit yes before it spends anything.
- 01
Ask in the channel
One mention, in plain English. No form, no portal, no ticket.
- 02
Rally reads the intent
Origin, dates, traveller count, purpose, budget. Ambiguous details get a question, not a guess.
- 03
Options under the cap
Numbered flights, hotels and ground inside the $800 cap you set. The traveller replies with a number.
- 04
Confirm, then it books
The fare is revalidated at booking time, so the confirmed price is the paid price. Code lands in the thread.
It won’t claim a booking it hasn’t made. Until a provider confirms, Rally says it is working on it.
It won’t invent the details. Dates, budgets and destinations come from what the traveller said.
Every request is verified. Slack events are signature-checked and workspace tokens encrypted at rest.
Fifteen minutes, in your own workspace.
We install Rally, set a trip cap, and run a real request from mention to confirmation code while you watch.