> ## Documentation Index > Fetch the complete documentation index at: https://help.fanaura.com/llms.txt > Use this file to discover all available pages before exploring further. # AI Tour Builder > Paste your entire tour routing into Aura and watch it build your complete tour in seconds. Supports any format -- Excel, CSV, freeform text, and more. Manually entering 30-50 tour dates into any platform is tedious, error-prone, and a massive waste of time. Fanaura's AI Tour Builder solves this completely. Paste your tour routing -- in any format -- and Aura parses everything automatically. Dates, cities, venues, ticket links, presale codes, on-sale times -- all of it. What used to take 30 minutes of careful data entry now takes about 30 seconds. The AI Tour Builder accepts data in any format -- spreadsheets, agent emails, CSV, freeform text, or any combination. No reformatting required. *** ## The Problem If you've ever had to enter tour dates into a platform, you know the pain: * Your booking agent sends a spreadsheet or a PDF with all the dates * You have to manually enter each date, one by one * Each entry needs: date, city, state, venue, ticket link, on-sale date, presale code... * It's 30+ dates, each with 5-8 fields * One typo means a fan sees the wrong date or wrong venue * It takes forever and it's the least fun part of tour announcement prep Other platforms (Bandsintown, Seated, etc.) have the same manual entry problem. Manual data entry for 30+ tour dates means 25-35 minutes of work and a high risk of typos. *** ## How It Works Navigate to the **AI** section in your Fanaura dashboard. Start a new conversation or use an existing one. Tell Aura you want to build a tour and paste your data. Aura handles any format -- spreadsheet copy-paste, agent emails, CSV, or even minimal shorthand. **From a spreadsheet (tab-separated):** ``` 03/15/2027 Nashville, TN Ryman Auditorium https://tickets.example.com/nash 03/17/2027 Atlanta, GA The Tabernacle https://tickets.example.com/atl 03/19/2027 Austin, TX Stubb's BBQ https://tickets.example.com/atx 03/21/2027 Denver, CO Red Rocks https://tickets.example.com/den ``` **From an agent's email (freeform text):** ``` Hey, here's the routing: Wed March 15 - Nashville, TN - Ryman Auditorium Fri March 17 - Atlanta, GA - The Tabernacle Sun March 19 - Austin, TX - Stubb's BBQ Tue March 21 - Denver, CO - Red Rocks Ticket links and presale codes to follow. ``` **From a detailed routing:** ``` SPRING TOUR 2027 03/15 Nashville TN - Ryman Auditorium (Cap: 2,362) - Tickets: link1 - Presale: RYMAN2027 03/17 Atlanta GA - The Tabernacle (Cap: 2,600) - Tickets: link2 - Presale: ATL2027 03/19 Austin TX - Stubb's BBQ (Cap: 2,100) - Tickets: link3 - Presale: STUBBS2027 03/21 Denver CO - Red Rocks (Cap: 9,525) - Tickets: link4 - Presale: ROCKS2027 ``` **Even minimal formatting:** ``` Mar 15, Ryman, Nashville TN Mar 17, Tabernacle, Atlanta GA Mar 19, Stubbs, Austin TX Mar 21, Red Rocks, Denver CO ``` After you paste your routing, Aura: 1. **Identifies the data structure** -- figures out which parts are dates, venues, cities, links, etc. 2. **Normalizes dates** -- converts any date format into a consistent format 3. **Extracts venue names** -- separates venue names from city/state information 4. **Finds ticket links** -- pulls out any URLs associated with each date 5. **Captures presale codes** -- identifies presale codes if included 6. **Fills in missing data** -- if state abbreviations are missing, Aura infers them from the city name Aura presents the parsed tour data in a clean, formatted table for your review: * Each tour date as a row with all extracted fields * Date, city, state, country, venue, ticket link, presale code * Any ambiguous entries flagged for your review You can: * Confirm everything looks correct * Ask Aura to fix specific entries ("Change the Denver date to March 22") * Add missing information ("Add ticket links for all dates") * Proceed with creation Once you confirm, Aura creates the entire tour: * All events are created in your Fanaura account * Venues are auto-geocoded for heatmap integration (so fans near each venue show up on your fan map) * Each event gets its own smart link for sharing * Tour dates appear on your Artist Hub automatically * RSVP functionality is live immediately *** ## Supported Formats Aura is remarkably flexible about input formats. You do not need to clean up or reformat your data before pasting. | Format | Supported | | ---------------------------------- | -------------------------- | | Excel copy-paste (tab-separated) | Yes | | Comma-separated (CSV) | Yes | | Freeform text | Yes | | Agent email copy-paste | Yes | | PDF text copy-paste | Yes | | Abbreviated dates ("Wed 10 Mar") | Yes | | Full dates ("March 10, 2027") | Yes | | Numeric dates ("03/10/2027") | Yes | | International dates ("10/03/2027") | Yes (Aura asks to confirm) | | Mixed formats in one paste | Yes | *** ## What Gets Created When Aura builds your tour, each event includes: * **Event date and time** -- properly formatted and timezone-aware * **Venue name** -- exactly as provided (or cleaned up from abbreviations) * **City and state** -- normalized for consistent display * **Country** -- inferred if not provided (defaults to US for US cities) * **Ticket link** -- if provided in the routing * **Presale code** -- if provided in the routing * **Presale date** -- if provided in the routing * **On-sale date** -- if provided in the routing * **Geocoordinates** -- auto-generated for venue location mapping * **Smart link** -- automatically created at `fan.fanaura.com/[artistSlug]/[eventSlug]` *** ## Date Format Handling Aura is smart about dates, but here's how it handles edge cases: * **Two-digit years** -- "03/15/27" is interpreted as 2027 * **Abbreviated months** -- "Mar", "March", "03" all work * **Day-of-week prefixes** -- "Wed March 15" works, the day of week is used for validation * **Ambiguous dates** -- if "03/04/2027" could be March 4 or April 3, Aura asks you to clarify * **Relative dates** -- "next Friday" or "this Saturday" work if context is clear * **Date ranges** -- "March 15-April 20" with individual dates listed below When pasting international dates (DD/MM/YYYY vs MM/DD/YYYY), Aura will ask you to confirm the format if dates are ambiguous. It never guesses wrong silently. *** ## Time Saved Here's the real math: | Approach | 30 Tour Dates | | ------------------------------ | ------------- | | Manual entry (other platforms) | 25-35 minutes | | Manual entry (Fanaura form) | 20-30 minutes | | AI Tour Builder | \~30 seconds | That's not an exaggeration. Paste, review, confirm, done. For a typical 50-date arena tour, you're saving over an hour of tedious data entry -- and eliminating typos and data entry errors in the process. *** ## Why Booking Agents Love This If you work with a booking agent (or you are one), this feature is a game-changer: Paste the routing exactly as the agent sends it. The agent doesn't need to fill out a special template. Tour announcement pages can be live minutes after routing is confirmed. AI parsing eliminates manual data entry mistakes that lead to fans showing up at the wrong venue. This is a genuine competitive advantage over tools like Seated, Bandsintown, and manual Linktree setups. No other platform lets you build a complete tour this fast. *** ## Tips and Tricks **Paste everything at once.** Don't feed Aura dates one at a time. Paste the entire routing in one message for best results. **Include as much data as possible.** The more information you paste (ticket links, presale codes, on-sale dates), the more complete your tour will be without follow-up edits. **Review carefully before confirming.** Aura is very accurate, but always double-check dates and venue names before creating the tour. **Ask for corrections.** If Aura misreads a venue name or date, just tell it: "The Nashville venue should be Ryman Auditorium, not Ryman Theater." Aura will fix it. **Add dates later.** Already created a tour but new dates were added? Just paste the new dates and Aura will add them to the existing tour. **Use for festival routing too.** Festival appearances with stages, set times, and load-in details can all be parsed. *** ## Example Conversation Here's what a typical Tour Builder interaction looks like: **You:** > Build a tour from this routing my agent sent: > > Mar 15 Nashville TN - Ryman Auditorium > Mar 17 Atlanta GA - The Tabernacle > Mar 19 Austin TX - Stubb's BBQ > Mar 21 Denver CO - Red Rocks Amphitheatre > Mar 23 Los Angeles CA - The Greek Theatre > Mar 25 San Francisco CA - The Fillmore **Aura:** > I've parsed your tour routing. Here's what I found: > > | Date | City | State | Venue | > | -------------- | ------------- | ----- | ---------------------- | > | March 15, 2027 | Nashville | TN | Ryman Auditorium | > | March 17, 2027 | Atlanta | GA | The Tabernacle | > | March 19, 2027 | Austin | TX | Stubb's BBQ | > | March 21, 2027 | Denver | CO | Red Rocks Amphitheatre | > | March 23, 2027 | Los Angeles | CA | The Greek Theatre | > | March 25, 2027 | San Francisco | CA | The Fillmore | > > 6 dates found. I didn't see ticket links or presale codes -- would you like to add those, or should I create the tour with what we have? **You:** > Create it! I'll add ticket links later. **Aura:** > Done! Your tour has been created with 6 events. Each event has a smart link for sharing, and all venues have been geocoded for your fan map. You can view and edit the tour in your Tours section. That's it. Six tour dates, created in under a minute.