BattleKart to ROLLER Agentic Booking Creation
Coming soon. When a guest books on battlekart.com, an AI agent will create the matching booking in ROLLER, so every booking and all venue capacity live in one place. This pack is pending BattleKart API access and is not yet available to purchase.
IntelliPaaS keeps every battlekart.com booking in ROLLER without anyone rekeying it. When a guest books a session on battlekart.com, an AI agent picks up the new booking and creates the matching booking in ROLLER.
The agent reads the session, the date and time and the party details, then writes them into ROLLER as a new booking. Your team sees battlekart.com bookings alongside every other channel, so venue capacity is managed from one place.
Because the agent works from the booking the guest just made, bookings land in ROLLER in moments. The flow runs for every new battlekart.com booking, so nothing is missed and nobody copies details between two systems.
Watch the agent run, end to end
Why deploy this use case
Battlekart.com bookings appear in ROLLER alongside every other channel.
An AI agent creates each ROLLER booking, with no manual entry from your team.
Venue capacity is tracked in ROLLER across every channel.
The agent works from the battlekart.com booking, so it needs no custom BattleKart booking API.
Bookings land in ROLLER shortly after the guest books.
Nobody rekeys bookings between battlekart.com and ROLLER.
More BattleKart automations
Questions teams ask
How quickly can we get this running?
Most teams are live the same day. Connect ROLLER, point the agent at your battlekart.com bookings, and it runs against your own data with nothing to deploy.
Do we need to write any code?
No. The agent and the ROLLER booking creation are configured for you, so your team can own it without waiting on engineering.
Does this need a BattleKart booking API?
No. The agent works from the battlekart.com booking itself, so it does not depend on a BattleKart booking feed.
What about changes or cancellations?
For now the pack creates the booking in ROLLER. Later changes or cancellations are not synced automatically and should be updated in both systems.