It would be appreciated and more proactive if the Act! installer did a check and alert wherever the 64bit version of Office is installed. This way, the Act! installation could be halted until the Office 32bit reinstalled instead, rather than needing to start all over again after Act! is installed, learning this when at the final Outlook configuration stage.
Since we upgrade ACT! every time the programming team creates a new version, which often requires uninstalling the old version and installing the new one, it would be nice to have a file stored outside of the ACT! folders (so it doesn't get deleted) that could regenerate our Customized Column settings for the multitude of views that change back to their default settings in the new version. I spend a great amount of time setting up my columns in the Contact List, Group Opportunities List, Companies Opportunity List, Contact Opportunities tab, and so on, and I also have to go through and redefine which views I prefer to have grid lines in, since they all default to being turned off. The default settings for the columns are very basic and inadequate for our purposes, so everyone in the company has to spend time changing them back to the way they like to see them, that is, if they can find the time to do it. If there was a SAVE function for the columns, which could save those settings outside of the usual ACT! folders, then we could recall those settings when we uninstall the old version and install a new version. Right now, the only way anyone can guarantee that they're setting up the next installed version like their previous version, would be to either keep screen shots of every customized view, or create some kind of document outlining the customized columns for every section. And since none of us have the time to go through and document the column headers, we have to guess, to the best of our ability, what our previous version was set up like. It's a frustrating and time consuming process that seems like it could be avoided with some sort of Save feature.
One of the useful additions to Act! was the automatic "Last Reach", "Last Attempt", "Last Letter" etc System generated fields.
What would be really useful would be the ability to define new fields like these based on User Defined Activities.
So, for example, a customer wants to differentiate between a standard Meeting and a user defined "Maintenance Visit", they could schedule a "Maintenance Visit" for their engineer in the Calendar and, when Cleared, the system would automatically generate a date in the "Last Maintenance Visit" field. This field could then be available to Lookups or, indeed, Smart Tasks to better manage customer service.
Improve the existing Act! emarketing reporting on clicks, allowing users to see which specific hyperlinks were clicked by a recipient.
This information may help to to further prioritise or route leads within a sales team, depending on exactly how the recipient has interacted with an email.
Create Lookup button for List View in web access (Cloud) is limited to current page. For example, if user creates search in Opportunities that gives as result list of Opportunities which is several pages long, user then cant apply “Create Lookup from Opportunity” button, to create lookup of all Contacts which were added to those Opportunities.
This is possible in the desktop version of Act! .
You can remove any of the other tabs from the display, EXCEPT for the Timeline. Please allow the user to remove it.
There is no function to place fields in subject lines in AMA.
I'm trying to place users first name in the subject line - this would be very handy as this will increase open rates.
ie: Your Going to miss out <first Name>
I'm sure other fields would also be useful - please fix this guys
The Go Kart Guy
On the desk top version of Act it's possible to put spaces between phone numbers to make them easy to read, e.g. 020 7123 4917, rather than a string of numbers, 02071234917.
Please can this be incorporated into Cloud Act?
Swiftpage Emails should be an independent History Type for Filtering on the History Tab and in ReportingStatus: Available in Act! v17
When sending a Swiftpage campaign the History should NOT record as a generic 'E-mail Sent'; but rather as its own independent History Type (History Type name to be determined). This feature additional would allow the user to independently 'filter out' these Swiftpage Histories. Due to the frequency in sending Swiftpage campaigns,the result is to crowd or overload the History view. the end user would be improved with this feature addition.
My company has been using ACT! since version 2.0; and we have since upgraded through the years. We just updated to version 21 and implement remote access to the database through ACT companion.
After using ACT companion for a few weeks, we have the following suggestions:
- show the company name in the contact view. Currently it only shows the name and phone number, but if you have a contact record without a contact name, it only shows the phone number.
- allow users to create alarms when they are scheduling activities through the app. Current functionality does not allow this at all.
- allow users to sort opportunities by open or closed.
- Currently there is a glitch so that when an alarm goes off, a user gets three notifications on their phone. This is annoying at the very least.
- allow users to customize which types of notifications they receive on their phone. I don't need to know when someone in my organization adds a contact.
I'm sure that my users will think of more suggestions.
Swiftpage staff, please let me know how you handle user suggestions. I would really like to see these suggestions implemented.
Balfrey & Johnston Inc.
Customizeable Surveys For Act! emarketing which data can be imported into Act! and update contact fields directlyStatus: Submitted for voting
Basically we are looking For at least the same functionality that we have for Swiftpage emarketing in the New Act! emarketing product. the ability to create surveys with custom questions and map the response back to specific fields in Act!, or have them mapped to a survey responses tab.
For a reference of Surveys and how they worked in Swiftpage emarketing please see the articles below.
When looking at Activity we have only got the Icon of the Activity and not the Activity Type name.
That is OK for the default Call, Meeting, To-Do, but useless on other Activities unless a custom Icon has been created as all the Icons are the same.
Please can we have the option to display the activity type Name
There is the ability to create a separate activity for multiple contacts in Act! for WEb, but there is no option to clear multiple histories in Act! for Web.
This feature is available in the Windows version of the software and should be available for web users also.
This came from a question - How to add a new item to an existing drop-down list?
It would be sensible to allow an option where ACT administrators can change the drop down list without having to go to Tools - Define Fields which means it throws everyone of the database or has to be done out of hours.
Simply allow an ACT administrator access to the dropdown list even when do not allow editing is ticked in the Define Fields area without having to go to define fields.
Many people assume that ACT! does this already and are somewhat perplexed to find that it doesn't. We also need to be able to automatically create companies when importing contact data. Probably the best way to handle this would be to have some additional options in Preferences.
Option 1 - Do not automatically create Companies from Contacts.
Option 2 - Always create a new company if it doesn't exist when adding a new contact and automatically add to a company if it already exists.
Option 3 - Always create and link a new company if it doesn't exist when adding a new contact and automatically link to the company if it already exists.
Can the dev team consider adding a feature to allow Act eMarketing users to cancel scheduled sends, without having to call in and wait for a support person to assist with the request. It would seem to give users great functionality and to free-up time on your support team, so that they may assist users with other "technical" issues.