208397 Event Registration Forms
N/A
Paid on delivery
To familiarize yourself with the project, review and test the following forms:
[login to view URL]
[login to view URL]
[login to view URL]
Description of EXISTING set up:
The main part of the project is an online Registration form for free tickets to an Expo.
[login to view URL]
To get a free ticket, visitor is asked to fill out a Registration form. Only name and email address are mandatory fields. Visitor must register with valid email in order to receive a free ticket.
Upon registration, the validation email is sent to visitor. When visitor follows the link in the validation email, the ticket is displayed and emailed to the visitor.
Bug fixes required in the Existing set up:
- The Registration form and Tell-a-friend forms currently displays ticket confirmation in the old graphic template – programmer must fix to display the confirmation in the new template;
- In addition to displaying the ticket, it must be emailed to the visitor – programmer must add this feature.
- Each ticket has a unique number, one section of the number is pre-set and other section is random. Ticket numbers must be recorded in a MySQL database in visitor's profile.
- Contact Us email form displays wrong confirmation page – programmer must design and install appropriate confirmation page after sending email.
- Debug intro page - [login to view URL]
Changes in the existing form requested:
Existing registration form is too long. We need to split registration form into two forms as follows.
1. In the first screen, the visitor will only be asked to register with his name and email address, plus three additional fields will be added to (1)identify referral source (referred by another visitor) and to identify visitor's interest as (2) personal (check box) or professional (check box). After that the visitor will click “Send” and,
2. go to the second screen. At the same time a validation email will be sent to the visitor. In this screen the visitor will be told “thank you for your registration, the validation email should arrive in your mailbox shortly. In the mean time, please tell us a little more about yourself. Complete this form and you could win one of free vacations or a free round trip for two.” The screen will require some new contents and graphics (buttons). The Programmer is asked to design the page in attractive style within the template with banners and buttons.
3. Visitor may provide information as requested and click “Send”, or click “No Thanks”. In both cases, the third “Thank you” screen will show a new form asking visitor to “invite” friends to register. Visitor may enter friend's name and email address and click send. Validation email will be sent to the “friend” and the friend will follow steps below.
4. Programmer must develop logic for user friendly process allowing visitor to invite as many friends as they want or opt-out at any time.
Landing Page from Validation Email – “The Ticket Screen”
5. When either visitor, or the new invited “friend” clicks the email verification link in the validation email, he will be taken to the Ticket Screen where ticket is displayed with an option to print the ticket or to save information in Outlook. The ticket must have a date, location and a map. In addition to displaying the ticket, a separate confirmation email with the ticket will also be sent to the visitor. The email must contain “unsubscribe” link.
6. The Ticket Screen will be similar to screen #2 (above) asking the visitor to provide more information. In addition, the screen will also contain a form asking visitor to “invite” friends to register.
7. In addition to other registration fields, database must record referral information - who invited the visitor.
8. There will be no restriction how many times the same visitor may be invited. However, when the same email attempts to register more then once, a message will be displayed saying that
“a free ticket was already emailed to you. Please click here to retrieve your ticket. If you need more tickets for your friends, clients or associates, please use the form below to invite them to register.”
9. Database must be programmed to send automated reminder emails to all visitors every Thursday until May 1.
Develop New Form:
This form functions essentially in the same way as the previous one. Except, this is a different category of visitor an a different category of invitation.
1. In the first screen, the visitor will be asked to register for special events by checking off on the events of interest from the list and by providing registration information on the form (a list of fields will be given to the programmer). After that, the visitor will click “Send” and follow the same email validation steps as in the previous form.
2. When visitor follows the link to verify his email, he will come to the second screen where ticket confirmation will be displayed. At the same time a confirmation email will be sent to the visitor. In this screen another form will be displayed asking visitor to “invite” friends to register. The form will allow the visitor to enter friend's name and email to send an invitation and specify if “client” has a “personal” or “professional” interest in the event.
3. The database must record the visitor as a referral source when the “friends” follow the link to retrieve their ticket.
4. The registration screen will require some new contents and graphics (buttons).
5. The friends registration will follow the same logic and steps as in the previous form.
6. Database must be programmed to send automated reminder emails to the special events visitors every Thursday until May 1.
7. On May 1, the last email will be sent asking the visitor to follow the link to confirm his attendance.
Other requirements:
The database also records information from other emails sent from the site. Programmer is asked to add appropriate fields to the database be able to sort which form (registration, contact-us, tell-a-friend, etc.) was responsible for recording the visitor information in the database.
Programmer is asked to complete the design of user friendly online interface for administration of the database (the admin interface work has been started by the previous programmer but not completed).
Project ID: #1954622
