Paul Battaini
My feedback
81 results found
-
13 votesPaul Battaini
shared this idea
·
-
17 votesPaul Battaini
shared this idea
·
-
17 votesDeclined · 0 comments · Feature Suggestions for Maximizer CRM » Business Intelligence - Reports & Dashboards · Admin →Paul Battaini
shared this idea
·
-
111 votesUnder review · 5 comments · Feature Suggestions for Maximizer CRM » Business Intelligence - Reports & Dashboards · Admin →Paul Battaini
supported this idea
·
-
119 votesPaul Battaini
shared this idea
·
-
3 votesPaul Battaini
shared this idea
·
-
190 votes0 comments · Feature Suggestions for Maximizer CRM » Customizations - Labels, Icons, Display · Admin →Paul Battaini
supported this idea
·
-
25 votesPaul Battaini
supported this idea
·
-
14 votesPaul Battaini
supported this idea
·
-
9 votesPaul Battaini
supported this idea
·
An error occurred while saving the comment -
15 votes
An error occurred while saving the comment Paul Battaini
commented
In a related request, improve the 'Move Up' and 'Move Down' to not have to reload the screen as well. In a large list it takes a very long time to update the order of items.
Paul Battaini
shared this idea
·
-
143 votes
Please note Maximizer’s professional service team have created integrations with Avaya AES among others so feel free to contact them directly if you have an acute need for this type of integration.
Paul Battaini
supported this idea
·
-
117 votes
Could you please provide more detailed use cases and examples. Basic UDF inheritance can be complicated and confusing for new entries or for those that are left blank on purpose etc.
Paul Battaini
supported this idea
·
An error occurred while saving the comment Paul Battaini
commented
Rather than a system-wide behaviour of UDFs, this should be a settable field property. There should also be a rule to decide if existing Contact level values are overwritten or added to.
-
154 votes
You can create a custom field (UDF) and then set it to True or False. Then using Advanced Search you can filter whether to show entries based on this custom field (UDF).
An error occurred while saving the comment Paul Battaini
commented
There is also the issue of what to do with the Notes from these contacts. In one respect they are communications with the parent Company as well and should stay visible regardless of the Contact status. But History items like Campaigns to this Contact are of less value and should be Hidden. Should the default visiblity levels be configurable at a DB level by the Admin?
Paul Battaini
supported this idea
·
-
4 votes
An error occurred while saving the comment Paul Battaini
commented
I think with the new Filter by Date setting which can default to a last-used value this suggested feature would not be needed. Merging older Notes looses a lot of information and search-ability for little gain that I can see. Maybe a flag similar to UDF for "Hidden" would be good so less critical Notes can be excluded from day-to-day activity but still accessed if needed?
-
47 votesPaul Battaini
supported this idea
·
-
173 votesPaul Battaini
supported this idea
·
-
143 votesPaul Battaini
supported this idea
·
-
97 votesPaul Battaini
supported this idea
·
-
37 votesPaul Battaini
supported this idea
·
Not sure if you mean the "Default Entry" feature or the standard copy-down from a Company to the new Contact screen. In the later case, you can alter the Phone details per-Contact as needed. They copy from the Company since the majority of Contacts do share some details and at least if left unaltered they are better than being left blank (for tools such as the Phone Dialer).