Its important to consider how the packages are named in the CRM because these are also what the bookers see in the portal.
The naming needs to be clearer and consistent. When a user goes to book TAI they will be presented with a dropdown list of 15 ticket options in the portal.
Renaming these packages with the proposed below should hopefully make it easier for users to quickly scan, understand and find the package for them
|
Current name
|
Proposed name
|
|
TAI Day 1
|
TAI Conference – Day 1
|
|
TAI Day 2
|
TAI Conference – Day 2
|
|
TAI both days
|
TAI Conference – Both Days
|
|
Asset Management Summit - day 1
|
Asset Management Summit – Day 1
|
|
Development Summit - day 2
|
Development Summit – Day 2
|
|
TAI day 1 with conference dinner
|
TAI Conference – Day 1 + Conference Dinner
|
|
TAI day 2 with conference dinner
|
TAI Conference – Day 2 + Conference Dinner
|
|
TAI both days with conference dinner
|
TAI Conference – Both Days + Conference Dinner
|
|
Conference dinner only
|
Conference Dinner Only
|
|
Asset Management Summit - day 1 with Conference dinner
|
Asset Management Summit – Day 1 + Conference Dinner
|
|
Development Summit - day 2 with Conference dinner
|
Development Summit – Day 2 + Conference Dinner
|
|
Asset Management Summit -day 1 and TAI day 1
|
TAI Conference – Day 1 + Asset Management Summit
|
|
TAI day 1 and Development Summit - day 2
|
TAI Conference – Day 1 + Development Summit (Day 2)
|
|
Asset Management Summit - day 1 and TAI day 2 with dinner
|
TAI Conference – Day 2 + Asset Management Summit (Day 1) + Conference Dinner
|
|
TAI day 1 and Development Summit - day 2 with dinner
|
TAI Conference – Day 1 + Development Summit (Day 2) + Conference Dinner
|
I would also suggest we re-order the packages in the CRM/portal so we organise by both days first, the conference day 1 options, then day 2 options, and then the summit, and finally the conference dinner.
Hopefully this makes it easier to navigate to the relevant package:
Currently, we're presenting all the member and non-member ticket combinations in one long table. Even with clearer package names, that's still a lot of information for users to work through.
I'd suggest breaking the information into smaller tables, grouped around the main attendance options.
Ticket option |
Price |
|---|---|
TAI Conference – Both Days |
Free |
TAI Conference – Both Days + Conference Dinner |
£95 |
Ticket option |
Price |
|---|---|
TAI Conference – Day 1 |
Free |
TAI Conference – Day 1 + Conference Dinner |
£95 |
TAI Conference – Day 1 + Asset Management Summit |
Free |
TAI Conference – Day 1 + Development Summit (Day 2) |
Free |
TAI Conference – Day 1 + Development Summit (Day 2) + Conference Dinner |
£95 |
Ticket option |
Price |
|---|---|
TAI Conference – Day 2 |
Free |
TAI Conference – Day 2 + Conference Dinner |
£95 |
TAI Conference – Day 2 + Asset Management Summit (Day 1) + Conference Dinner |
£95 |
Ticket option |
Attendance only |
With dinner |
|---|---|---|
Asset Management Summit (Day 1) |
Free |
£95 |
Development Summit (Day 2) |
Free |
£95 |
Ticket option |
Attendance only |
With dinner |
|---|---|---|
Asset Management Summit (Day 1) |
£295 + VAT |
£390 + VAT |
Development Summit (Day 2) |
£295 + VAT |
£390 + VAT |