I am an ACT! Certified Consultant working in Australia and many of my clients wish to use the potentially great functionality of Smart Tasks. Obviously with the absence of a direct email mail merge function the logical choice is to use Sage eMarketing to send emails with merged fields from the contact.
However there is a major design fault with the running of these Smart Tasks. Below is the workflow to duplicate this situation.
Create an auto run smart task matching the appropriate criteria.
Add the Sage eMarketing workflow to this smart task.
Set it to auto run at a time during which the user will have ACT! open (Smart Tasks with Sage eMarketing steps cannot run without ACT! open - a potentially frustrating situation also but not my main concern).
When testing you will see the smart task run and there will be a pop up message informing the user that the smart task was sent to 1 contact, which is OK.
The problem is, this message is repeated for every individually contact that matches the smart task criteria! So if your criteria selects 100 contact to send an eMarketing email to then the user will have to press OK 100 times!
Furthermore, if you have multiple email messages to send using Sage eMarketing then each smart task run will do the same thing!
Obviously Sage and Swiftpage have positioned themselves strategically side by side to service ACT! customers. So in turn they have an obligation to fix this so that only 1 dialogue box shows up for each smart task, or to remove this notification completely as it prevents the user from using ACT!
Many of my clients users that have been trying to implement smart tasks with Sage eMarketing steps are force ending ACT! to get around the hundreds of pop up confirmation messages.
I understand that this is likely by design but surely part of the benefit of a forum like this is to listen to genuine feedback and to make to product more attractive for new and existing users.
Hope the above is clear enough, but if not please let me know and I will be happy to explain or demonstrate this issue.