Every BandBrain band gets a dedicated email address: <yourband>@bandbrain.ai. Find it on the Channels page or the Channels quadrant on the home page.
What to send to it
Anything you want BandBrain to know:
- Day sheets from Master Tour
- Venue advance packets
- Promoter contracts (PDFs)
- Press contact lists
- Email threads with the booking agent (CC the BandBrain address)
- Travel confirmations
- Hotel reservations
What happens with each inbound email
- Message saved to the conversations log — searchable via the agent's
search_messagestool and visible on the Inbox page - Attachments ingested — PDFs, images, sheets, docs become resources in your knowledge base
- Links followed — Drive / Dropbox URLs in the body get auto-ingested if BandBrain can access them
- Body text parsed for structured facts via day_facts extraction — load-in times, doors, hotel confirmations all become structured data
- Sender added to contacts (if not already there) — auto-extracts name + organization + role from email signature
Email is ingestion-only
BandBrain never auto-replies to an inbound email. The agent doesn't run; no agent-composed response goes out. Email is a one-way pipe into the brain.
The reason: email threads are often multi-party (booking agent, manager, label, venue). Auto-replying would inject the bot into business conversations unpredictably. Inbound = absorb; outbound = only via explicit broadcast.
Master Tour day sheets
A common pattern: your booking agent emails the daysheet PDF to your BandBrain address every morning. Within ~1 minute:
- PDF is ingested as a resource
- day_facts extraction pulls venue/hotel/schedule/contacts into the structured store
- Sender domain is checked — if it's
@eventric.comor@mastertour.com, the resource gets taggedmetadata.source = "mastertour"so the agent knows it's canonical data
After that, any band member texting "what's tonight's hotel?" gets the right answer instantly.
CC'ing the BandBrain inbox
A nice pattern: CC <yourband>@bandbrain.ai on threads with promoters / venues / label. BandBrain absorbs the back-and-forth and the agent can search past conversations later: "what did the Wiltern's PM say about parking last time?"