AI Assistant

Ask the Sway assistant about an event, train it on what Sway cannot measure, import a mailbox, and share it with the people working the door.

Swapy answers questions about one event, in two registers. It reads what Sway already measures — the line-up, the ticket types, the orders, the guestlist, the team, and the history of the promoter, the venue and the artists booked. And it repeats what your team has taught it: the phone number of the photographer, the load-in time, which door the van goes to.

The two never blend. A number Sway measured and a sentence a colleague typed are different kinds of claim, and the assistant says which one it is using.


Open the assistant

Three ways in, all showing the same conversation:

  1. The Swapy quick tool, on the right of every admin screen.
  2. Full screen, from the header of that panel, which floats the conversation over the page.
  3. Open in a dedicated tab, from the panel header. It opens a screen with nothing else on it, at /backstage/event/<id>/assistant.

On a phone the assistant is the bottom sheet the other quick tools use.

If you cannot see it on an event, your account holds no permission on that event — see Permissions.

On Backstage the same button opens a different assistant. There is no event to answer about there, so Swapy answers about your account instead: what to create, what to claim, and in what order. See How Your Pages Work.

Ask a question

With no conversation started, the panel shows six Suggested questions. They are built from this event: an artist who has no set time yet, a name somebody trained, a question your team asked and nobody answered. They change as the event does.

Type anything else into Ask anything about your data…. The assistant reads the question, looks up what it needs, and answers in a sentence or two. It is deliberately brief: a factual question gets a factual answer, not a paragraph of preamble.

New conversation clears the thread. The conversation is shared across the three surfaces above, so closing the panel and opening the tab does not lose it.

An answer sometimes ends with a button to the screen that owns the subject. That only happens when the next step is genuinely somewhere else, not on every reply.

Copy a message with the button that appears beside it when you point at it - yours or Swapy's. It turns into a tick once the text is on your clipboard. On a phone the button is always there, since there is nothing to hover.

Reasoning appears above an answer when the assistant worked something out before replying. Unfold it to read what it decided to look up and why it chose one figure over another - useful when an answer surprises you. It is folded by default and per message, because on most replies it tells you nothing you did not already know.


What the assistant can see

SourceWhat it carries
This eventTitle, dates, timezone, venue, promoter, genres, line-up, ticket types, paid orders, guestlist, team, description
The promoterTheir past events, how far in advance they usually announce, how those events sold
The venueWhat has been held there before
The artistsThe other Sway events an artist on your line-up has played
Past editionsEarlier events with the same name, compared edition over edition
Trained factsEverything your team confirmed in Train, below
Each block obeys the permission that protects the screen it comes from. Somebody with guestlist access only gets the guestlist: asking for the revenue returns nothing, not a number. Opening the assistant to your whole team widens who can ask, never what any one of them can see.

The cross-event blocks are cautious on purpose. With fewer than three past events, the assistant says the history is too thin to draw a median from rather than pretending two events make a trend.


Ask how Sway works

The assistant also reads the documentation you are on right now. Ask it where a screen is, what a setting does, or which steps a feature takes, and it answers from the written page and links it:

  • "How do I create a discount code?"
  • "Where do I connect Stripe so I can get paid?"
  • "How do I add a scanner at the door?"

This works on every assistant, not only an event's — an artist page, a venue, a promoter, a crew. It reads the edition in your own language, and it follows the documentation as it is updated: edit a page, and the next answer quotes the new text.

It also reads the Terms, the Privacy Policy and the contest rules, straight from the published files. Ask what the terms say about refunds or what happens to personal data, and it quotes the clause with the version it came from and links the page. It quotes rather than summarises, and it never turns a clause into advice about your situation — for that, write to [email protected].

The documentation says how Sway works. It never says anything about your event: no phone number, no load-in time, no name. Those come from the two sources above, and the assistant keeps them apart.

Train it on what Sway cannot read

Switch the panel to Train. The tab is only there for people who hold the training permission.

  1. Type what you know into the box: "Alex is the photographer, reachable on +32 470 00 00 00. Load-in is at 16:00."
  2. Click Extract the facts.
  3. The rows that come back land under Waiting for you, one per fact.
  4. Confirm each one that is right. Reject the rest.

Nothing is quoted to anybody until you confirm it. A wrong fact here is a volunteer calling the wrong number at 02:00, so the assistant never applies its own extraction.

Confirming a fact that already exists replaces the old one. In the knowledge base lists everything active, which is exactly what the assistant will repeat.

Refresh Sway data rebuilds the event snapshot the assistant reads. Useful right after you have changed the line-up or added a ticket type.

The assistant never guesses from what you typed. Write "the stage manager is Marie", not "Marie will handle it" — the second sentence names nobody the assistant can look up later.

Import a mailbox

Import a mailbox takes an .eml or .mbox export — the thread with the tour manager, the rider, the hotel confirmation — and turns it into pending facts, judged the same way as anything you type.

  • One file at a time, up to 10 MB.
  • The uploaded file is never stored. It is read once and dropped; only the facts you confirm are kept.
  • A signature repeated across twelve replies produces one row, not twelve.

Asked, never answered

Every question the assistant could not answer is logged under Asked, never answered, in the words of whoever asked it, with a count of how often it came up. Click one and it becomes the first line of the training box.

That list is the best answer to "what should I train next" — better than an empty textarea, and it comes from your own team.


House rules

House rules are standing instructions added to every answer: "After 22:00 call the production lead, never the promoter." Up to 2000 characters.

They change how the assistant answers. They do not change what it knows, and they never override what Sway measured or the rule in What it will never tell you, below.


Share this assistant

The people working the door rarely have a reason to open the admin. Share this assistant gives them a link that opens the conversation on its own.

  1. Enter a Link name: 3 to 48 characters, lowercase letters, digits and dashes.
  2. Turn on Link is live.
  3. Click Save, then Copy link.
The link is not a password. Whoever opens it still has to sign in to Sway and still has to hold a permission on this event; the name only decides which event the page is about. Anyone else is told to ask you for access. The page is kept out of search engines and out of the sitemap.

What it will never tell you

The assistant never says how many tickets are left. Not the remaining stock, not the capacity minus the sales, not an estimate, not a hint, on any surface, to anybody, however the question is phrased. That number is removed from the data the assistant reads before it ever gets there. Read it on the dashboard instead.

When a question has no answer in what it holds, the reply starts with Not in the knowledge base. rather than a plausible guess, and the question joins the list above. An assistant that invents a phone number is worse than one that says it does not know.


Who can do what

ToYou need
Open the assistant and ask questionsAny permission on the event, or membership of the crew that manages it
See a given figure in an answerThe permission that protects that screen: Orders, Line-up, Guestlist and so on
Open Train, confirm facts, import a mailbox, share the linkTrain the event assistant, under Event AI in the event's team permissions

Where the rest lives

Event Dashboard

Ticket stock, recent orders and the figures the assistant will not quote.

Insights

The charts behind the sales, traffic and check-in answers.

Team and Permissions

Who can open the assistant, and who can train it.