Your event

Invitations

A personal link that RSVPs straight into tickets, past the event page.

Your eventShareInvitations

What you can do here

An invitation lets someone claim tickets without going through your event page. The tickets can be free, paid, or a mix.

go.tito.io/acme/summer-fetes-summer-fete/admin/invitations

Anyone holding the personal link can respond whether or not it was ever emailed.

On an event people get into only by invitation, Invitations is near the top of the sidebar, under Overview. Once somebody books another way, or pays for an invitation, it moves into Share.

Invitees can confirm one place without a second name and email form when their free invitation already has those details and asks no questions before RSVP. If you offer one free ticket type and allow guests to be added later, invitees can add guests after confirming their own place.

Once somebody accepts, they get the RSVP confirmation email, whether their invitation is free or paid. It lists who’s going and links back to their RSVP. You can change its words in Customize.

The link in that email opens their RSVP page. It asks Are you going? with their answer picked, and lists who’s going. Each person has Show code for the code to show at the door. When the ticket type has its QR code off, each person’s reference is shown instead. If you let people add guests later, the page says how many more they can bring.

If you let people cancel their own RSVP, they can choose No, I can’t make it, and each guest has Remove. Both ask them to confirm first.

Someone who cancels their RSVP can accept again from the same page, as long as the invitation’s deadline hasn’t passed and there are places left. Their invitation goes back to Accepted.

Actions offers two things you can do to whoever the list is showing: message them, or export a spreadsheet of them.

When you add someone, their invitation is marked Draft. After you send their invitation email, individually or in a batch, it is marked Sent. A failed first send leaves it in Draft.

Existing invitations use their send history. After someone responds, you’ll see Claimed or Declined.

Someone who signed up on Tito Pro and still needs your approval shows Waiting on you, and their link offers nothing to claim yet. See Approve or turn down an invitation.

Filter the list first and the filter comes with messages and exports. A search term comes across only on an export. Filter by Imported by or by duplicates and Message these people isn't offered. See Email everyone who is coming.

A message to your invitees is in the list on Messages, with the rest of your messages. Open it and select its Recipients figure to see every email it became. Sent means the sending service accepted the email, not that it reached the inbox. See Messages.

Invitation details list each attempt with its date, status, and subject, linked to that recipient’s saved email. The saved copy keeps its original wording after you edit the template. Older emails appear when their saved invitation link identifies the recipient. Older bulk sends appear as individual emails. Messages addressed to invitees also appear in their invitation history.

Open the invitation and choose Send email, or Resend email once it has been out. You can see the recipient and the email, choose who it's from, and edit the subject and preview text. To write the email yourself, choose Start from an empty email.

Choose Add an optional note to open the note dialog. The note is written in the same box as a message, with formatting, and Insert adds their name or the event’s own details. Save note updates the email in place. The note is included when you send this email and applies to this send only.

Lists

A list groups invitations.

They share one name, one set of ticket types and one deadline. Manage lists, from Invitations, shows the lists you have and makes new ones.

Open a list for its own page, showing how many have claimed, what it hands out and what it asks. Two buttons send to everyone who hasn't been sent theirs, or remind everyone who hasn't answered. They appear once somebody is on the list. Edit changes its name, its deadline and its ticket types, and What they’re asked covers the questions. The ⋮ menu holds importing, exporting, duplicating and archiving.

Duplicate makes a second list with the same settings: how many tickets an invitation is worth, whether the invitee can edit their own details, the claim deadline, the ticket types and the questions. Nobody on the list is copied. You land on the new list's Edit page with its name ready to change.

You can set which ticket types a list offers from either end.

From the list's own page, under Edit. From a ticket type, under Where it’s shown on its own page, which is the one to use when you want one ticket on several lists. See Choose where a ticket is sold.

Moving an invitation to a different list changes which settings and deadline apply to it from then on.

Importing a spreadsheet

Import in the Invitations header takes a CSV or an Excel file, one person per row, up to 5 MB. Download a starter file gives you the columns already laid out.

You can paste rows instead of choosing a file. Copy them in Google Sheets or Excel and paste them into Or paste rows from a spreadsheet. Bring the heading row with them if they have one. Without headings, each column is read by what is in it, and the check page shows which column became what so you can change it.

Your file needs a column of names or a column of email addresses. An identifier column is optional. An identifier is anything stable and your own, such as a membership number. Reusing one updates that person instead of inviting them twice.

Rows without an identifier always invite somebody new.

Every import of the same file invites those people again. The check page warns you about any email address that is already on an invitation at this event.

A Form of address column sets how German emails greet each person. It reads Frau and Herr, or feminine, masculine and neutral. When an invitation is updated, an empty cell keeps its form of address.

A CC column copies people in on each invitation, such as a guest's assistant. It also reads Kopie an. Put several addresses in one cell, separated by commas or semicolons. A row that copies people in needs its own email. Importing a file with a CC column replaces the copies on every row it updates, so an empty cell removes them. A file without one leaves them as they are.

If the event has more than one list, the import asks which list the rows are joining. With a single list it uses that one.

Nothing is written until you have seen what the rows will do. Check the rows reads them and shows you each one.

A row that cannot be imported as it stands opens in place, with boxes for its own details and the reason underneath. Correct it and press Check again, which imports nothing. You can also untick a row and import everything else.

Rows that need fixing are always shown, however far down the file they are. The screen shows the first twenty of everything else and counts the rest.

The button says how many invitations it will create or change, and it stays off while a row you have ticked still needs fixing.

Once somebody on your team has imported a file, Filter has an Imported by section with their name in it. Pick a name to see only the people they imported. Somebody invited another way isn't under a name, and neither is anyone imported before Imported by was added. Importing a person again keeps them under whoever imported them first.

People invited twice

When the same email address is on two or more invitations at this event, each of them has a Duplicate mark beside the name.

Filter has a Duplicates section once anyone is marked. Choose Duplicates only to narrow the list to them. The invitation's own page says how many times its address appears, and See them in the list opens those invitations.

Company, job title or phone under each name

Show sets what appears under each name on the list, for you only. Choose Company and job title or Phone number to see them in place of the email address. Anyone who hasn't given one still shows their email address.

They come from the spreadsheet you imported and from what people filled in when they accepted. Show appears once at least one person on the list has one of them.

Giving someone another place

Raising the ticket count on an invitation that has already been accepted opens another place on it. Open the invitation, select Edit, change Tickets and save it.

Add a guest then appears on the RSVP page that person already has, and they name the guest themselves.

Saving stops to ask, because that email goes to somebody. The page names the person and the address, and See this email shows what will arrive. Save and email them does both, and Save without emailing adds the place and says nothing.

The question only appears when the number goes up and that person has accepted. A save that changes a name or a deadline goes straight through.

The email carries the link to their RSVP.

What an invitation costs

Every ticket type on an invitation shows what the person will be asked for, on the row where you switch it on. Leaving the price box empty charges the amount named under the ticket's name.

Set a price on a list under Edit and everyone invited onto that list pays it. Set one on a single invitation, either as you create it or under Edit, and it applies to that person only. Type 0 to give the ticket away.

A price can't be more than the ticket's own price. Emptying a box goes back to inheriting: clear a person's price and the list's applies again, clear the list's and the ticket's own price applies.

A price you type here applies whatever the quantity, so a ticket with volume prices keeps its bands only while the box is empty.

An invitation's page shows Cost under What they can claim. Where the invitation offers a choice of tickets, it shows the range.

If your event sells in more than one currency, Priced in appears on the Ticket types offered line. Pick one and the prices under it reprice in it. The invitation keeps that currency for good: prices you type are read in it, the person's own page charges in it, and only tickets with a price in that currency appear. A list price is an amount of your event's own currency, so it applies to invitations in that currency only.

Invitations to priced tickets

An invitation to a ticket with a price needs a payment method connected before anyone can claim it. Until one is, the Invitations list and each invitation on it show a warning, and anyone opening their link is told the invitation isn't ready yet.

An invitation can go out before your payment setup is finished, and be claimed once it is. Claiming a priced invitation puts the invitee on the same payment page a buyer sees. Connecting either card payments or PayPal is enough for the invitation to work.

What an invitation asks for

The event's own defaults for every invitation live under Settings then Invitations: what to ask the invitee and their guests, whether guests can be added later, and whether someone can cancel their own RSVP.

What you ask invitees covers the invitee's name and email. Guests holds the questions about the other people, and switching guests off takes all of them away. Canceling and refunds holds the cancel switch, with the refund rules inside it.

Preview the form shows the claim form these settings produce, and it changes as you answer, before you save. When the form differs between tickets, pick one under Show the form for. Your own design isn't in it, so to see how the form looks, open Customize.

Refunds allowed until reads in the event's own timezone.

  • Questions is everything an RSVP asks beyond a name and an email. Invitations ask a ticket's questions the same way the ticket does. Each row says how the ticket asks it and on which tickets, and says at the right when invitations ask it differently. Select Change to set it for the invitee and for each guest: optional, must answer, shown but can't be changed, seen only by organizers, or not asked.
  • Questions a ticket type asks come first. The claim form asks them first too, so a question of your own can be shown only after a particular answer to one of them. They're added and removed on the ticket type. When your event asks its questions after the order is confirmed, which is how a new event starts, they're asked once the RSVP is confirmed instead, the same as at checkout, and don't show here. Otherwise you change here how they're asked. “Same as the ticket” asks it the way the ticket does, and where one ticket type asks it, Change links to that ticket type.
  • Setting a question the ticket type requires to Not asked shows a warning, and then the claim form doesn't ask it.
  • The questions you're asking come next. Choose from your questions opens the rest of your library, with a box to find one by name. Set how a question is asked and select Done, and it joins the list. It's saved when you save the page.
  • A list and a single invitation have the same list of questions, which overrides the one above it. Change a row and this list or this invitation differs from then on. Set it back to “Same as the event” (on a list) or “Same as the list” (on an invitation) and it follows again.
  • Setting a row to Not asked stops this list asking for something the event still asks everyone else.
  • You can fill an answer in for someone before they claim, under Questions and answers on the invitation. It covers the invitee and a guest for each further ticket, and the answers arrive on that person's form already filled in. For a question set to Read-only or Organizers only, this is the only place its answer can come from.

RSVPs

Each accepted invitation is an RSVP. The event's overview counts them under RSVPs, apart from paid orders, and marks each one in the list of recent orders. The Activity page and the orders report leave free RSVPs out of what was sold.

A free RSVP's order shows Places and the date it was accepted. It has no money section, and its Actions start with Open the invitation. A paid RSVP keeps the money and its receipt.

Good to know

  • The check screen says what each row will do, and nothing imports until you confirm. An invitation whose invitee has already responded is left as it is, whatever the file says.
  • An export starts from what's on screen, with the same filter, and offers every invitation on the event instead. Every column starts selected, including organizer-only ones.
  • Save this as a preset keeps a set of columns for next time, and everyone on your account gets it.
  • CSV heads each column with the field name, for another system to read. Excel writes the headings out in full, to read yourself.
  • When someone cancels a paid RSVP while refunds are allowed, they get back what they paid for their tickets and for any extras they added later. Each amount goes back to the payment it was made with. Canceling one ticket of several refunds that ticket, and the extras on an order go back with its last ticket. An extra you recorded as paid offline stays with you, and the order stays paid.
  • If somebody picks a ticket and closes the page without paying, their place is held for about thirty-five minutes. After that the place becomes available again and their link offers the invitation again.

API

The API can read or change RSVP settings for an invitation list or one invitation. Unchanged settings keep their current overrides. Clearing an override restores the setting inherited from the event or list. You can also set which attendee details invitation recipients provide and whether each detail is optional, required, read-only, private, or hidden. Question overrides apply to a list or one invitation. Choosing the default restores the inherited question rule. You can also set a different price for each ticket type on a list or for one invitation. Clear an override to use the inherited price, or set zero to make the ticket free. See Connect through the API.

Still stuck?

You can let someone at Tito sign in to your account for a set time, and see every visit they made.

Let Tito support in →