The agent can edit your tour data in plain English. Common patterns:
Schedule / time updates
- "Update van call to 9am tomorrow"
- "Doors are pushed to 8pm tonight"
- "Soundcheck moved to 4:30 for the Wiltern show"
Hotel / venue changes
- "Tonight's hotel is the Marriott Downtown, not the Hilton"
- "Updated the address for the Wiltern — 3790 Wilshire, not 3796"
Guest list
- "Add John Smith plus one to tonight's list"
- "Take Matt off the Friday list"
- "Add Sarah Jones plus three (all access) to Seattle"
- "Who's on the Wiltern list?"
Contacts
- "Save Jamie at the Wiltern as production manager, phone 213-555-0100"
- "Update Sarah's email to sarah.j@livenation.com"
How writes propagate
When the agent writes a change:
- The change lands in BandBrain's
day_factstable (the structured source of truth for the agent) - If the original source is a Google Sheet, the agent ALSO writes the change back to the right cell in the sheet, so humans opening the sheet see the new value
- The agent confirms back to you with the relevant numbers (e.g. "Added John Smith +1 tonight. Tonight's list — 4 people total: ...")
For Dropbox sources, BandBrain writes only to day_facts — Dropbox files don't get auto-updated (see Connecting Dropbox for why).
Confirmation pattern
For guest list adds, the agent ALWAYS reads back the full updated list so you can verify. This is by design — a bare "X spots" was too easy to misread. Now you see exactly who's on the list after every change.
Permissions
Edits respect the same category permissions as reads. If you don't have finance permission, you can't update financial fields. If you're a non-admin, you can't trigger broadcasts. Refusals are polite and explain which permission is missing.
Undo
There's no formal undo, but each write captures the previous value in the audit log. If you ask "undo my last update", the agent can usually look up what changed and revert it.