Skip to content
Hypamoon

For teams that run on Billetto

Billetto no-shows: who came and who did not

Billetto shows how many tickets were scanned and when, and its post-event automations send the same email to each ticket buyer of the event. Who held a ticket but stayed away is something you work out from the guest list yourself.

How it goes today

  1. Export the ticket list after the event, including scan times.
  2. Sort out which tickets have no scan.
  3. Write two emails and send each one to the right group.
  4. Do the same again after the next event.

How it can go

The day after: who came, who did not, and a fitting email for each.

The morning after each event, two lists from the Billetto scans: ticket holders who came and ticket holders without a scan, per ticket type. Those who came get your thank-you email with the survey, the others get a short note that you missed them, both in your own words. You get the numbers per event in a short summary.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your Billetto key in the portal, never in the chat.

Your request

With Hypamoon, the morning after each of our Billetto events, split the ticket holders into those whose ticket was scanned and those whose ticket was not. Email the first group our thank-you note with the survey link, and the second group a short note that we missed them. Send me the numbers per ticket type.

You create the API key pair yourself in Billetto, under Integrations, Developers, API key pairs. Give it a name you will recognise, so you can revoke it there later. It stays yours.