Tickmi

The Data assistant for your attendee and ticket lists

The Data assistant sits right above the list in the Attendees tab and the Tickets tab. Type what you need in plain language and it filters, counts, runs stats, exports Excel and points out data that needs checking. Every change is shown first, so you review it before applying.

· 6 min read · Checked against the Tickmi software

On this page
  1. What the Data assistant is
  2. Data check suggestions when you open a tab
  3. Ask and have the assistant do the work
  4. Filter and count
  5. Stats
  6. Clean up data
  7. Bulk actions
  8. Export Excel
  9. Review before applying, undo when needed
  10. AI credits and attendee data
  11. Tips for getting the most out of it

What the Data assistant is

Attendee lists often come from several sources: Excel imports, registration pages, ticket purchases, manual entry. So the data tends to mix ALL-CAPS names, phone numbers in different formats, emails with mistyped domains, people with no email, or someone who registered twice. The Data assistant helps you find and fix these before you send tickets, and speeds up everyday jobs like counting, running stats and exporting Excel for a group of people.

The assistant is available in two places and works the same way in both:

  • Attendees & tickets → Attendees: works with attendee details (full name, email, phone number, note, approval status). See also manage attendees.
  • Attendees & tickets → Tickets: works with individual tickets (check-in, email delivery status, tickets that failed to build, cancelled tickets).

The input box has a ✨ icon and the hint "Ask the assistant: …". Type your request and click Send.

The assistant is only visible to the organization's Owner and Admin. Accounts used only for check-in do not see it, because the assistant shows attendees' names and emails. See member permissions.

Data check suggestions when you open a tab

As soon as you open the tab, a Suggestions: line appears under the input box with buttons that show exact counts. Issues that affect whether attendees receive their tickets are listed first.

In the Attendees tab:

  • N people have no email to receive tickets: people on a ticket type that is sent by email but who have no email yet. Enter the email right in the list (the Enter correct email box) and apply.
  • N emails can't receive mail: mail sent to these addresses has bounced before. Ask the attendee for the correct email and enter it. See also fix bounced emails.
  • N duplicates: people with the same email or the same phone number. Each row says who they duplicate and whether that person has checked in. The assistant only lists them; to delete, select the person in the list and delete as usual.
  • N emails to check: emails with a mistyped domain (gmial.com, gamil.com and so on) with a suggested correct address; emails in the wrong format are flagged for you to fix by hand.
  • N phone numbers to check: normalized to the 0xxxxxxxxx form (removing +84, dots and spaces, and restoring a leading 0 that Excel dropped). Numbers it cannot recognize are only flagged as "Phone number looks wrong" for you to review.
  • N people pending for over 3 days: reminds you to approve or delete them in the Attendees list.
  • N names to tidy: extra spaces are removed; names in ALL CAPS or all lowercase are rewritten as Title Case. Names with deliberately mixed capitalization are left alone.

In the Tickets tab:

  • N tickets sent to bounced emails: tickets that were sent but whose email could not receive mail. Fix the email in the Attendees tab (the emails can't receive mail chip), then resend the ticket.
  • N tickets failed to email, N tickets not sent, registration closed, N tickets not sent: click to see the list, then click Resend N tickets. Studio asks Email tickets to N people? before sending.
  • N tickets failed to build: click Rebuild N tickets to regenerate the QR code and the ticket file.

These suggestions are checked by Tickmi directly against your data using fixed rules, and do not use AI credits.

Ask and have the assistant do the work

You can type naturally, as if messaging a colleague. The assistant understands five kinds of requests:

Filter and count

Examples: "how many people use outlook", "who registered last week but has not checked in", "list people pending approval", "which tickets failed to email". The assistant applies a filter to the list below and reports the number of matches, for example 2 people match. Filters understand email domain, phone prefix, full name, ticket type, source, approval status, check-in, attendance confirmation and date range. You can still adjust the filter by hand afterwards.

Stats

Examples: "stats by ticket type and source", "stats by email provider", "check-ins by hour". The result is a small table with the columns Group, the number of people (or tickets) and Checked in. Check-ins by hour show you the peak times so you can staff the gate better next time. See also the check-in stats screen.

Clean up data

Examples: "clean up my data", "normalize phone numbers", "find duplicates". The result is the same as clicking the suggestion buttons above.

Bulk actions

  • Attendees tab: add to or overwrite the note for a group of matching people, for example "add a VIP note to self-registered people not yet checked in".
  • Tickets tab: rebuild tickets, check in or undo check-in, restore cancelled tickets.

Approving attendees, sending or resending tickets, cancelling tickets and deleting are not done through assistant commands. You select the people or tickets in the list and use the regular buttons, so every action that issues tickets, sends email or deletes is one you click yourself. Rebuilding tickets still uses ticket issuance quota, just like the regular button; if you run short, Studio opens the buy-more box right there. See buy more ticket issuance quota.

Export Excel

Example: "export excel tickets not checked in". The assistant applies the filter and downloads an Excel file with exactly that part of the list.

If the assistant cannot do something yet (for example changing a ticket type), it tells you plainly that it can't do this yet.

Review before applying, undo when needed

The assistant never changes data on its own. Every change appears in a separate panel:

  1. Each row shows the attendee's name and the old → new value (the old value struck through, the new value in green), or the number of tickets and the ticket type for ticket actions. Rows that are informational only (such as duplicates and people pending approval) carry a note on how to handle them and cannot be selected.
  2. Untick the rows you do not want to change. Use Select all to select or clear everything quickly.
  3. Click the main button at the bottom of the panel, for example Apply 3 changes, Rebuild 2 tickets, Check in 1 ticket or Restore 3 tickets. Click Dismiss if you do not want to do it.

After changing names, phone numbers, emails or notes, the line Updated N fields. appears with an Undo button that puts every value back as it was.

Fixing an email through the assistant does not resend the ticket email. If that person needs the ticket again at the new email, select their ticket in the Tickets tab to resend it, or use Fix email with the resend option.

AI credits and attendee data

Common requests (counting by email, pending approval, not checked in, stats by ticket type, data clean-up, duplicates, tickets that failed to email and so on) and the data check suggestion buttons are handled directly by Tickmi and do not use AI credits. Only for more complex requests, for example an action with conditions or a date reference such as "today" or "this week", does the assistant ask the AI to understand the request, and each such request uses 1 AI credit from your organization. When your organization runs out of AI credits, the assistant shows a Buy more link (the remaining AI credits are shown right under the input box); the clean-up suggestions and regular filters still work.

The AI only reads the sentence you type and the ticket type names to choose what to do. Names, emails and phone numbers in your sentence are masked before it is sent. Finding people, counting and fixing data are all done by Tickmi; the AI never reads the attendee list. See also use Tickmi in AI assistants.

Tips for getting the most out of it

  • After every Excel import, click the suggestion buttons (especially people have no email to receive tickets and emails can't receive mail) to clean the data before you approve and send tickets: correct emails mean tickets reach the right people, and consistent phone numbers make look-ups at the check-in desk faster.
  • Before the event day, ask "which tickets failed to email" so you can sort out people who have not received their tickets early.
  • After the event, "check-ins by hour" and "export excel tickets not checked in" help you build reports and follow up with no-shows. See also the summary report and QR code check-in.

Frequently asked questions

Does the Data assistant change my list on its own?

No. The assistant only suggests and shows a list of old → new changes. Data changes only when you click the apply button. Approving, sending tickets, cancelling tickets and deleting are not done through the assistant but with the regular buttons in the list.

Does using the assistant cost AI credits?

The data clean-up suggestions and common requests such as counting by email, not checked in, stats by ticket type and finding duplicates do not use AI credits. Only more complex requests use 1 AI credit each.

What if I applied something by mistake?

For changes to names, phone numbers, emails and notes, click Undo on the notice line right away to restore them. If you checked in the wrong tickets, ask the assistant to undo check-in for exactly those tickets.

Why don't check-in staff see the assistant?

The assistant displays and edits attendee information, so it is only for the organization owner and admins. Check-in-only accounts can still scan tickets and view the list as before.

How does the assistant find duplicates, and does it delete anything?

It groups people with the same email or phone number, keeps the one who has checked in, then the one who already has a ticket, then the one added earliest, and lists the rest along with who they duplicate. It never deletes anything itself; if needed, you select the person in the list and delete them.

Can't find your answer?

The Tickmi team is here to help on hotline 0349 632 920, or try Tickmi for free and follow along.

Contact Tickmi

Request a callbackChat on ZaloMessage on FacebookHotline 0349 632 920

Tickmi uses essential cookies to run this website and Google Analytics to measure page views and clicks so we can improve the product (only if you agree). Privacy policy