> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/events/create-an-event/manage-attendees/how-to-add-a-customer-to-an-event-after-its-over.md).

# How to add a Customer to an Event after it’s over

* If a Customer forgot to sign up for an Event and their participation in an Event slipped through the cracks, you’ll want to add the Customer into the Event, even if the Event is over.
* To do this,
  * Click into the Event
  * Scroll down in the side panel that popped up
  * Click Add Participant
  * Click Guest (no charge, does not count towards quota) at the top
    * You need to click this button because you will not be able to add the Customer as a Regular Participant once the Event is over. If you try, you will see an error message.
  * Search for the Customer’s name
  * Click the plus button on the right side of their name
  * Click the Add Participant blue button
  * Click Save at the bottom of the side panel
* Now the Customer has been added to the Event, even though the Event is over. This is a great way to ensure that all Customers who attended an Event are included in that Event’s history.
* As a likely next step, you may also want to charge this newly added Customer for their Event participation. To do so,
  * Click back into the Event
  * Click on the Purchases tab of the side panel
  * Click on the Charge button
    * The newly added Customer will be on this dropdown list of Event participants
  * Click on the Customer’s name
  * Click Add Item
  * Navigate to the Booking item
  * Type in the cost
  * Write in the details of this charge
  * Click the blue button Add
  * Click the blue button Create Charge
* Now this newly added Customer will have the proper charge for their Event participation


---

# 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://docs.podplay.app/events/create-an-event/manage-attendees/how-to-add-a-customer-to-an-event-after-its-over.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.
