When I receive an e-mail, I try to discipline myself to immediately save it to the record of its sender before I double-click on it in the inbox, and then click-on Reply, Reply-all, or Forward to respond.

But sometimes I forget to first save the incoming e-mail. Sometimes, even if I HAVE saved the incoming e-mail, I may forget whether I have saved it or I haven't.

Instead of searching for the sender's record in Maximizer, then checking the sender's Documents to verify whether or not I'd already saved the e-mail, I typically re-save that e-mail to Maximizer to save myself extra effort and time. That has resulted in a lot of duplicate saves.

If the incoming e-mail showing in the Outlook in-box could be 'ear-marked' once it is saved to the sender's and/or other records' then I would be saved the extra effort and time needed to create a duplicate-save, and that record's Documents would be easier to index.

The desktop version provided keyboard short-cuts to input dates and times, enabling me to keep my hands on the keyboard and my eyes on the screen continuously.

Maximizer LIVE instead forces me to constantly remove my right hand from the keyboard and shift my gaze from the screen to locate the mouse, grab it, find the cursor, move the cursor to the pertinent dialog box, search for the applicable date and time, and click it to make my selections, then return my right hand to the keyboard.

It would be MUCH less-disruptive to my workflow and faster if the capability to short-cut dates by the desktop method, which is 6 digits -- MMDDYY, which Maximizer recognized flawlessly -- were restored.

Also, restoring capability to enter time by keying-in either 3 or 4 digits plus letter 'a' or 'p' -- i.e. 632a for 6:32 AM, or 1234p for 12:34 PM which Maximizer recognized flawlessly would speed things along as well.

The point here is that the operator's hands never leave the keyboard, and his eyes never leave the screen. This improves the operator's concentration and progression from task to task.

I sense that it is young IT professionals' dependence upon the mouse -- resulting from their inability to use a keyboard without looking at it -- that has resulted in the heavily 'mouse-only' operating protocol.

They screwed up. Keyboard expertise that many (most?) older operators possess is not an ability that should be ignored, discouraged, and/or PENALIZED, just because younger developers never developed their own keyboard expertise.

I typically add a note upon completing what I am prompted to do by a Hotlist 'to-do' task. But all-too-often, I forget to either mark the Hotlist 'to-do' task as completed, or -- as is the nature of my workflow -- to revise the Hotlist 'to-do' task to schedule my next task with that particular contact.

An option to set-up the 'Notes' for prompting me to either mark the Hotlist 'to-do' task as completed, or revise/update the Hotlist 'to-do' task would help me make sure that I don't allow follow-up's to 'fall through the cracks' that jeopardize the process of converting leads into sales.

The desktop version of Maximizer enabled the user to view 'tiles' of the Company/Individual/Contact record in the Address Book with User-defined fields, (other) Contacts, Notes, Documents, Hotlist, and an Outlook display -- all in one view, without switching screens.

As you know, the Maximizer LIVE screen enables the user to see the Address Book data and User-defined fields, and EITHER the (other) Contacts, or Notes, or Documents, or Hotlist, with no view of e-mail.

I've gotten used to this limitation, but I would be able to work much faster if the lag-time between switching screens between Contacts, Notes, Documents, Hotlist, and the Outlook e-mail screens could be minimized by a single view of all these functions.

In most cases, the "allow public entries" is really limited to whether the user can create public Address Book entries or not. However, I think the concept is more granular than that.

I want users to be able to create public Address Book Entries, Notes, and Documents - but for the vast majority of users, I do not want them creating public Column Setups / Search Catalogs / Email Templates / etc. Often times, users will create these items without realizing what the implications are and it leads to clutter across the program. Certain users (department heads, admins, power users, etc.) should be allowed to create public objects which are shared across departments as required - but it would be nice to prevent users from inadvertently cluttering the database with public stuff while still giving them the ability to create the public objects that they should be creating.

When a user stops working for a company, most people will delete that user ID from the database. However, by doing so, the user is no longer available and stops showing up in various search functions (Case Owner, Opportunity Team Leader, etc.). For historical reference purposes, it would be good to keep the User ID around. However, doing this results in the various Column Setup / Favorite List / Coloring Rules / Search Catalog / Dashboard / Email Template / Action Plan screens becoming cluttered with data of users that no longer work for the company.

There needs to be an "archive user" feature which will clean up all of these personal objects from the database without removing the user from the list of users. This would allow the best of both worlds - to have the user available for historical searching / reference purposes without continuing to clutter the UI with the objects they made for themselves.

When administering a user in the Web Access Administrator, there is no way to quickly remove a user from all of their Group / Team memberships. Each box must be clicked (which triggers a postback) and then the Remove button must be clicked to execute the operation.

In the Windows Administrator, the list item could be double-clicked to remove it - or ALT+R could be used for even faster performance. The Web Access Administrator is too inefficient when working with a large number of users on a large number of Groups / Teams.

Since ALT+R would not work in a web browser, implementing "Remove All" and "Add All" would be a decent compromise that would save significant amounts of time.