You can move guests from one event to another. The process is dependent on what type of event the guest started in (originating event) and what type of event you want them to end up in (receiving event).
This article reviews how to move guests from a free event within a recurrent set to a different event within that recurrence. For example, I'm managing a weekly ceramics class. A guest reached out and asked if they could be transferred to another week.
To do this, first navigate to GUEST LIST.
Identify the guest that you want to move, then click the move icon in their row.
The MOVE... window will appear. Click SELECT RECURRENT EVENT.
You will be redirected to the event page for your recurrence.
Scroll down and click the chiclet for the event you want to move your guest to.
The registration input fields will automatically populate with the contact information of the guest you are moving. Check the box next to I AM NOT A ROBOT, then click REGISTER.
The moved guest will receive an updated confirmation email.
When you move guests between events, both the originating event and the receiving event are impacted. You can monitor this page by page in both events.
First, navigate to GUEST LIST within the originating event.
The confirmed guest count will have decreased by 1, and the number of spaces now available will have increased by 1. To view the moved guests, click the filter icon, then click VIEW MOVED.
The guests who have been moved from this event will display. Moved guests are denoted with a purple dot.
If you navigate to STATUS within the originating event, the guest who was moved no longer counts towards the guest totals.
If you navigate to GUEST LIST within the receiving event, you can see the guest we moved appears as confirmed (denoted by a green dot).
And within the STATUS page of the receiving event, this guest counts towards the numbers, and availability of spaces.
Thank you! If you have questions about this process, or any other features in SeatRobot, please reach out to support.
Comments
0 comments
Article is closed for comments.