|
ReWegar
|
July 15, 2015 at 4:13 pm
Hey,
I want a lot of espresso event to use my coming event. (soon)
It is possible to build this case?
This is a two-day event.
– One of the principal ticket for both days (paid) (buyer information)
– 4 separate workshops where additional (paid)
– Lunch on the first day (payable) (choice of food? It is not necessary, but it would be good)
– Lunch next day (payable) (choice of food? It is not necessary, but it would be good)
– Presence on aterparty (free) (custom field?)
Then everything will be for check-in with one “paper” and if selected will each workshop or separately?
Thank you very much!
|
|
Lorenzo Orlando Caum
|
July 16, 2015 at 2:01 pm
Hi there, I think Event Espresso 4 would work for your registration needs. Here is what it might look like:
Principal ticket (enabled for day 1 and day 2) – required ticket
-Workshop 1
-Workshop 2
-Workshop 3
-Workshop 4
Lunch for Day 1 (enabled for day 1)
Lunch for Day 2 (enabled for day 2)
Afterparty (enabled for day 2)
You would be able to collect custom questions and this would be on a per-event basis so you could use a general text area field for notes on the registration and this field could be used to collect lunch preferences.
—
Lorenzo
|
|
ReWegar
|
July 16, 2015 at 2:58 pm
ok,
It is necessary if the visitor wants everything to have 8 tickets, or you can have one?
At check-in you will need to scan 8x?
thanks
|
|
Lorenzo Orlando Caum
|
July 17, 2015 at 10:48 am
Hello again, that is a good question. A ticket would be assigned for each different pricing option (each ticket option).
If an attendee bought the same ticket multiple times (e.g. Workshop 1), then their ticket would allow scanning for the number of times that is was purchased.
—
Lorenzo
|
