> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/the-hub/managing-events/how-to-check-in-leads.md).

# How to check in leads

{% embed url="<https://getmobly.wistia.com/s/cybzambepr9ikqb>" %}

If your event has a registration list (people pre-RSVP'd), you can check guests in as they arrive using the Mobly mobile app. This article walks through the **CSV-upload path** — you upload your registration list to Mobly, then your staff swipes guests in from the app at the door.

> **Using Host for registration?** You don't need this CSV upload step — registrants flow into Mobly automatically. See [Checking in Host registrants](/help-center/the-hub/managing-events/checking-in-host-registrants.md) for the Host-event path.

## What you need

* **Check-in enabled for your org.** You'll see a **Registration** tab on each of your events when this is on. If you don't see it, contact your CSM.
* **A registration list** — your registrants exported from whatever tool collected them (your CRM, Eventbrite, a Google Form, etc.)
* **The Mobly mobile app** installed on your event staff's phones — [iOS](https://apps.apple.com/us/app/mobly/id6446095722) or [Android](https://play.google.com/store/apps/details?id=com.mobly.app\&hl=en\&gl=US\&pli=1)

## Step 1 — Upload your registration list

1. In the Hub, open the event you're prepping.
2. On the **Registration** tab, click the **+** button to open the CSV drawer.
3. **Download the Mobly CSV template** from the drawer.
4. Convert your registrant data into the template. Required fields: **First Name, Last Name, Company Name**. Strongly recommended: **email** — makes merging back into your CRM painless.
5. Upload your filled-in CSV.
6. If any rows are missing required fields, Mobly surfaces them — you can fill in the gaps inline or remove the rows from the upload.
7. Confirm the lead count and complete the upload.

The registrants now appear in Mobly as leads attached to the event.

> **Adding more registrants later** (last-minute sign-ups, walk-ins you want on the list): just upload another CSV with the new leads. The same template, the same drawer.

## Step 2 — Check guests in at the event

1. Each event-staff member opens the **Mobly mobile app** on their device.
2. Tap into the event — the registered leads appear in the event's lead list.
3. When a guest arrives, find their name in the list (search is fastest at large events).
4. **Swipe right** on their row to check them in.

That's it.

### Fixing an accidental check-in

**Swipe left** on the lead's row to reverse it. The lead goes back to **Registered** status.

### Walk-ins (guests not on the registration list)

For guests who weren't pre-registered:

* **If they have a badge** — scan them like a normal lead capture
* **If they don't have a badge** — enter their name manually from the capture screen

They land as a new lead in the event with **Scanned** status (different from Registered, useful for separating pre-registered vs. walk-up traffic in your reports later).

## Related articles

* [Checking in Host registrants](/help-center/the-hub/managing-events/checking-in-host-registrants.md) — for events that use Host registration (no upload required)
* [How to capture a lead](/help-center/the-mobly-app/capture-and-enrichment/how-to-capture-a-lead.md) — for walk-ins
* [How to prep for your upcoming event](/help-center/the-hub/managing-events/how-to-prep-for-an-event.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.getmobly.com/help-center/the-hub/managing-events/how-to-check-in-leads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.