How the routing desk works
- 1Enter the booked showsThe dates already confirmed: festival slots, support dates, a hometown show.
- 2Qloo shows where the fans areFanpoint maps the act's fans along each drive and drops any city that breaks a touring limit: too close to a booked show, doubling back, or too far to drive in a day.
- 3Book with proofOpen dates fill with the strongest fan cities left, each with a room, an opener and what those fans like outside music. You get the empty-night cost avoided, a CSV and hold requests. Every number links to its source; the AI only explains.
What Qloo adds: with the same touring limits but Qloo turned off, the demo route fills 0 of 13 open dates instead of 8.
Fanpoint vs a plain AI chatbot · tested on 10 acts, 13 open dates each
measured 2026-10-21, 10 artists, live Qloo + GeminiSame booked shows for every act. Both face the same touring limits: no show too close to a booked one (radius clause), no doubling back, a daily driving cap, at most 6 shows before a day off. “Plain AI” is the same AI model with no tools and no Qloo, answering from general knowledge. Limit breaks are counted by Fanpoint's own checker on real road distances (OSRM). “Typical” is the median act. Full method
Fanpoint + Qloo
5–10 open dates filled (typical: 7)
0 shows that broke touring limits · at most 3–6 shows before a day off
Plain AI chatbot (same model, no tools)
4–13 open dates filled (typical: 5)
Shows too close to a booked show: 0–3 · drives that doubled back: 0–5 · up to 16 shows without a day off (3 of 10 plans broke a touring limit)
Qloo changes which cities come first.
With and without Qloo on the same cities: the demo route fills 8 of 13 open dates with Qloo and 0 without (no fan data, so no schedule). On 34 drives, the top 5 cities by fan strength matched the top 5 by population and venues on only 2.