Planned

Searching via phone and postcode in Constituent Search (Ticket Orders Screen)

We've recently upgraded to v16 and have had several of our teams flag the removal of phone numbers from the Advanced Search options. In v15 this was a very helpful search option for both our Ticketing team and Development team for finding a constituent record following a missed call. 

Similarly, the removal of Basic Search from the Constituent Search while in Ticket Orders screen is also proving tricky. While you can still search for it in the regular Constituent Search, our Ticketing team will primarily be in the Ticket Orders screen where this would be more useful. Postcodes are extremely effective at searching for constituents as they are the most unique bits of information, along with email addresses, and are usually the quickest way to find previous bookers. It is also extremely helpful for differentiating between two constituents (individuals or Organizations) with the same name.

Is there any scope to reintroduce these two bits of functionality? 

Parents
  • We are also having problems with the Basic search, the team used to be able to toggle between the Const screen and ticket orders and now they can't do this, and the limitations on the new search screen mean that we are seeing lots of duplicate records , and finding it more difficult to locate customer records

Comment
  • We are also having problems with the Basic search, the team used to be able to toggle between the Const screen and ticket orders and now they can't do this, and the limitations on the new search screen mean that we are seeing lots of duplicate records , and finding it more difficult to locate customer records

Children
No Data