How to run event registration and check-in by text

It's 6:40 and doors open at 7. There's one folding table, two volunteers, a clipboard with a pen on a string, and 140 people walking up the steps at once. The line reaches the parking lot. Half the names on the sheet are printed, half are a scrawl, and one email ends in ".con". If you're working out how to run event check-in by text, the aim is simple: let every arrival check themselves in on their own phone, at the same time, and have the list of who came waiting for you when the doors close.

With Textiful, the clipboard becomes a sign. People scan a QR code or text a keyword like DOORS to 33777, reply with their name and email, and get a "You're checked in" text back. Each one is tagged with the event as they finish.

The problem with clipboard check-in

A check-in table is a single lane. One sheet and one pen means one person at a time, while everyone else waits. Volunteers end up writing names for people to speed things along, which is how emails get misspelled.

The sheet also hides the answer you wanted. How many came? Which registrants never showed? Who walked in without registering? Those questions wait until someone types the sheet into a spreadsheet, usually days later.

And the people who came are the ones worth following up with. A thank-you, the recording, next month's date: all of it depends on an email address someone typed in correctly.

Why the usual fixes fall short

• A second clipboard halves the line and doubles the typing.
• A tablet kiosk with a form reads well and still checks in one person at a time, and it needs a volunteer to watch it.
• A registration platform's check-in app works for ticketed events, and it's built around people who registered. Walk-ins and plus-ones fall outside it.
• A QR code to a web form gets people off the line, then asks them to fill in fields on a phone while they're holding a coat.

How to set up check-in by text with Textiful

1. Start from "Grow my email list." It asks for an email, then a first and last name. Rename the first message for the door: "Welcome! Reply with your email to check in."
2. Set the trigger. A QR code is free and doesn't use a keyword, so print it on every sign at every door. If a volunteer will call it out to the line, add a keyword like DOORS on 33777 or 55444 (one keyword is included on your plan). A QR code and a keyword can each start a copy of the same flow.
3. Keep the sequence short. Email and name are enough for check-in. If you need one more thing, add a custom data step such as "Which session are you here for?" or "Who invited you?"
4. Add actions. Use "Tag the contact" with the event's name and date, such as Spring Open House 2026. Send a text that confirms the check-in and says where to go. Add them to Mailchimp, Kit, ActiveCampaign, or HubSpot if your follow-up lives there, or connect another tool through Zapier.
5. Print the sign. Download the QR code as PNG or SVG and put it at eye level at the door and on the registration table, with the keyword underneath in large type. The QR code sign guide covers size and placement.

When the doors close

Open your contacts and filter by the event's tag. That's your attendance list. Export CSV downloads exactly what the filter shows, so you can match it against your registration export in a spreadsheet and see who registered and didn't come, and who came without registering.

For a small event or a VIP entrance, turn on "Email me a notification" so a host gets an email for each arrival, with their answers and tags. For a big crowd, skip it and check the filtered list instead, or your inbox will fill up.

If a guest stops halfway, optional follow-up reminders (off by default) can nudge them once. A flow closes after 24 hours without a reply.

Variations

• Multi-day events: copy the flow for each day and give each copy its own QR code and its own tag, so day one and day two report separately.
• Sessions inside a conference: one QR code per room, each on its own copy of the flow, tagged with the session. Pair it with session feedback at the end.
• Free community events and open houses: with no registration to check against, check-in by text is the registration. The tag tells you who came.
• Volunteer shifts: ask for a name and email, and add a custom data step for the shift or role.

How many questions should check-in ask?

As few as you can. Across Textiful flows over 90 days in 2026, one-question flows finished 89.5% of the time and two-question flows 83.1%. Name and email is two. Anything you can learn later from your email tool should wait.

Before and after

	Clipboard at the door	Check-in by text with Textiful
Line at the table	One pen, one person at a time	Everyone checks in at once on their own phone
Who writes the email	A volunteer, in a hurry	The attendee, with a retry if it doesn't look right
Knowing who came	After someone types up the sheet	A tag filter when the doors close
Spreadsheet	Typed by hand	Export CSV
Follow-up list	Built later	Already in your email tool or CRM

Who this is for, and who should skip it

It fits US events where people arrive in a crowd and you want a clean list of who came: open houses, community nights, conference sessions, church events, school family nights, and volunteer days. It also covers walk-ins at registered events.

Skip it if you need ticket validation, badge printing, or a check against a paid guest list at the door; your registration platform does that. Skip it too if many attendees will be on non-US numbers, since the short codes work with US carriers only.

You pay per conversation, one for each arrival who starts the flow. Plans start from $19/month; see pricing. The conferences and events page covers more ways organizers use Textiful.

Try it at your next event → Start a free trial