New Idea

Isn't it about time that ACT! supported field calculations?


In contacts, Companies, Groups and  Sales Opportunities

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.

Reschedule Multiple Tasks

Status: Available in Act! v16
by on ‎07-08-2009 08:38 AM

I want to highlight and move 2+ tasks to the next day, but there is no way to do this.  You mean I have to move them one-by-one? What a waste of time!

Status: Available in Act! v16
Did it!

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.



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. 




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.


Mike Lazarus
ACT! Evangelist
GL Computing, Australia

GL Computing Facebook Page -
LinkedIN ACT! Fanatics Group -

Here's my first feature request for the next ACT!:
Please try not to 'lose' anything that's been in ACT! 2005, 2006, 2007, 2008, and 2009.
For example, please don't 'lose' the Group selection drop-down that was in the upper right corner forever.

Losing features = losing credibility = losingcustomers = losing revenue = losing partners.

Stupid me!  I thought that would be self-evident!
Message Edited by tmergel on 11-10-2009 10:36 AM

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.

Status: Available in ACT! 2010
Available with known issues in ACT! 2010. Full support in ACT! 2011.

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.

Share your Ideas

We want to hear your cool ideas for improving Act! products and services. So add your own ideas or kudo (vote) on the ideas of others here!

I have an idea! How do I get started?

  1. Read our submission guidelines.

  2. Search for your idea. If you don't see it, submit a new one!

  3. Provide feedback on the ideas of others by voting with kudos and adding comments.

  4. Track your ideas and those you like. Once you've posted or kudoed and idea, subscribe to be notified via email of the latest updates to the idea. From within the idea, click "Idea Options" which appears above the idea title and choose, "Subscribe to this idea".

Be sure to check back from time to time to see new ideas and status updates!

Here is a quick list of the ideas for speedy browsing!