[Inpycon] Ticket cancellation/refund policies.
Sreekanth S Rameshaiah
sree at mahiti.org
Wed Jun 20 11:35:13 CEST 2012
On 20 June 2012 14:48, Kiran Jonnalagadda <jace at pobox.com> wrote:
> On Wed, Jun 20, 2012 at 4:12 AM, Sreekanth S Rameshaiah <sree at mahiti.org>wrote:
> Checked the refund future of doAttend. This is simple enough to manage.
>> Also, there is a edit functionality for booking, do you use this for
> Yes, when someone asks for a transfer, we use this to send it to the new
> We also ask people to NOT print tickets (the default DoAttend ticket
> template says DO print). It's easy enough to export the attendee list, sort
> it and keep a printout at the registration counter.
> When an attendee walks in, ask them to show some form of id and check
> their name off the list. Don't bother with their ticket printouts. This
> solves all problems with verifying tickets.
> We've automated all this with an open source app:
> https://github.com/hasgeek/peopleflow (repo is missing BSD license
> declaration and setup instructions since we're the only users so far).
> In Peopleflow, if you check a name off the list at one counter, it goes
> away from all other counters because it runs as a web app. This allows
> having registration desks that are physically separated from each other.
Thanks Jace. So, +1 for cancellation and transfer.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Inpycon