It would be great if deleted contacts just was put in a trash bin for a time before they disapear totaly. This would make it possible to re-activate a contact that was deleted by misstake. The time a deleted contact stays in the trash bin should be customizable.
Zoft 80 AB
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.
"Left message" it should not update the date reached. Obviously if I had to leave a message I DID NOT REACH THE CLIENT. This makes the last reach date in the record worthless and I need this to be accurate. Left Message means I have left them a message and is different from call attempted.
It's time to standardise where attached documents go in ACT! At the moment, if I'm looking for attached documents they could be in a number of different places:
The Documents Tab
Attached to a History record
Attached to a Note
Attached to an Activity
This makes them difficult to find.
Can I propose that ALL attached documents and Links to Documents go into the Documents Tab
History, Notes and Acivities show Links to the relevant document or link in the Documents Tab.
Can we not make colour coding in calendars and task-lists more flexible?
Many people have asked me if they could colour code the ACT! Users (i.e. sales people or service people) to make it easy to see what they are doing on the calendars and task lists.
A known issue with ACT! is that if Windows font size is anything other than 96 DPI strange things begin to happen (refer to KB 26349). The current 'fix' is to change your font size back to 96 DPI.
I would like to see this fixed so that any other font size can be used.
There are two primary reasons for this that I see are that
1. more people are buying large LCD monitors;
2. the workforce is aging and their eyesight is not getting better.
My fear (as an ACT! Certified Consultant) is that unless Sage fix this issue so that we can use larger font sizes in Windows without adversely affecting our use of ACT! we will have clients look for products that don't break, that allow them to use large font sizes on their large LCD screens.
Can we please have this fixed properly?
This is ONLY going to become a 'bigger' issue (pun intended).
It would be a great benefit if ACT had the capability to highlight something from another source (i.e.internet) and then drag and drop it in a 'Contact record' and ACT would automatically insert the information in the respective fields. In other words, suppose the below is the information you found on a website.
456 Main Street.
Somewhere, CA 92445
phone : 223-456-7890
All you would have to do is highlight the above and drag it and drop it in a blank Contact form in ACT and the fields would be auotmatically populated.
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.
Many of the error messages are pretty easy to resolve with the right search of the knowledge base... but:
- Many users are not aware of the KB
- Searching the KB often needs you to select the right words with the addition of functions like +
This would make it much easier for users to find an answer and should significantly reduce support costs
With OS and Office upgrades, when ACT! was with Symantec, while they never supported the beta releases, they did release patches within 30-60 days of retail release.
This changed when MS released Vista and Office 2007... This wasn't an issue to most users, as the uptake of these was very slow and users saw many other products took some time to add support also.
However, the current policy caused quite a bit of pain when Microsoft released Office 2010... Not just because of the extended time (and upgrade fee) for it to be added to ACT! 2011, but because Sage kept saying there would be an "announcement" regarding ACT! 2010 support for Office 2010 for months (even after the release of ACT! 2011. I mentioned this in this blog post:
Many of the vendors ACT! connects to are moving to more rapid development cycles - Windows 8 due next year; Windows Server 2011 out now; Office 365 due soon; IE 9 out now; Firefox 4.0 out now and 5.0 due soon; Google Chrome; Citrix; VMWare; etc...
One of the issues with some of these is that they are auto-rolled out to users (the three browsers for example) or will be installed by default on new hardware (eg Windows and Office).
With ACT! 2012 about to go beta, and being demonstrated in a North American Roadshow, I think it's crucial that Sage management implements a plan to support upgrades for products they support in a version of ACT!. More importantly, they need to announce the policy for this publicly - either that updates won't be supported for any of these till the next major release (and users will need to make the choice to wait or look at other options); or that they may be supported, depending on the effort required. If the later, Sage must be prepared to announce the fate of each of the possible patches at (or prior) to the release of the upgraded products you integrate with.
Every ACT! add-on vendor has to test (and usually update) their products with each Sage release of ACT! ... they start testing during Sage's beta period and try to have their updated code close the the release by Sage.
I accept that some updates require to much resources to do in a patch ... when this is the case, Sage should communicate this to users before they have started rolling out updates that prevent access to the functionality of ACT! that they need.
GL Computing, Australia
GL Computing Facebook Page - http://www.facebook.com/GLComputing
LinkedIN ACT! Fanatics Group - http://www.linkedin.com/groups?gid=49896
The menu structure and toolbar can be customised in ACT. Using Tools -> Customise -> Menus and Toolbars...
ACT 2010 introduced the "Big Buttons" that sit between the menu bar and the toolbar. Can we have the option to customise these as well?
I would like to be able to:
a) remove them
b) make them smaller
c) add commands and custom commands to them
Depending upon my client's needs.
I would like to propose an additional icon in Outlook: "Go to Contact", which takes you directly to the ACT! Contact based on an email match.
In fact, a combined " Create and Go To" and "Attach and Go To" options would be welcomed as well as you often need to add some changes to a record as a result of receiving an email from that Contact.
ACT! has the capacity to have custom tables available as sub entities to the major entities such as Contact, Company etc.
Unfortunately to make use of this capability either a third party software needs to be purchased or development skills are required to create the tables through ACT!'s software development kit (SDK).
It is reasonable to expect the Premium (desktop) version to allow an ACT! administrator user to create tables by way of a native table design tool, accessible through the Tools menu.
It is critical that ACT!2010 users who upgrade to Outlook 2010 (final) maintain integration with ACT, as well as avoiding any other major Office 2010 incompatibility. When I upgraded to Office 2010 last week, I found that the integration was lost. Tech Support gave me a workaround, but this should be more fully documented and formally supported. I was shocked to be told by customer service that ACT did not support Office 2010, as if it were a minor or unexpected product introduction. I think Sage will end up losing business by appearing to be clueless and inept in preparing for a game-changing Office 2010 product introduction by Microsoft. I think it is totally unacceptable to wait until ACT!2011 to provide reasonable compatibility.
I have been an ACT user in my IT consulting business since before 1994, and have lived with the slow evolution of ACT to interoperate adequately with MS Office. I advise many large user organizations on use of software. I am also a Microsoft Registered Partner and recognized industry Analyst. Along with thousands of other users and IT experts, I converted last week to Office 2010 including Outlook, and am transitioning from MOSS 2007 to SharePoint 2010. I think there are dramatic improvements which will cause customers to move far more quickly than past Office introductions, partly due to SharePoint, mobile and web capabilities. Last October, 7000 Microsoft users and solution providers converged on Las Vegas, eager to hear the latest about the expected 2010Q2 release of these long awaited products. May 12 was the official launch and channel and technet partners were able to download fully released product on that date. June 15 may be the retail release, but many users will convert before that time.
I have Act 2013 (so apologies if this is included in the latest version).
Many people may not be aware of this but ACT does not really work well if font sizes bigger are set higher than 100% (in Win 7 this changed under screen resolution --> Make text and other items larger or smaller). If you change from the default the ACT screen struggles to display some elements correctly. See below at the maximum 150%
In the past this was not really an issue. However I think more people will experience this limitation as PC's and Laptops attempt to complete with Apples Retina display and resolution sizes get larger, especially on smaller screens where using the default font size becomes impractical. I have a Window 8 Tablet which has a gorgeous 1080p display but unless the font size is at the maximum size onscreen text nearly unreadable.
I think this is going to become more of a problem especailly with laptops, ultrabooks and Win8 Tablets. I suggest that better support for larger fonts would be great.
Right now when you create a new history it defaults the history type Appointment or whatever is top of the list alphabetically, under the preferences there should be a setting where you can change the default type for new histories, say from appointment to meeting.
We just upgraded to AFFP 11 from version 6. My boss is about to kill me because he can't view both Notes and History in one place. There has to be a custom tab someone has built to accomplished this. Thanks.