07-27-2018 05:12 PM - edited 07-30-2018 01:04 PM
The problem the community has Jon is with Swiftpage not being proactive in providing information in a timely fashion and without our having to continuously prod for answers to important questions that have commercial impact on customers. If Swiftpage have closed or abandoned a published issue, the latter I believe to be the accurate term, then please have the good grace tell the community. Go back to posts about problems with Auto-attach and be proactive in responding. Not leave customers hanging.
You will know I've posted elsewhere on this and it isn't because I like spending my day posting on this, it is about getting the most up to date information so I can offer best advice. In this case I have a 22 user site hanging onto Outlook 2010 so that Auto-attach, critical to how they use Act!, continues for later upgrades which they desperately are wanting to do as is their hosting provider to get them into a later version of Office. That's reasonable isn't it?
I'd like Swiftpage to A/ understand that and B/ operate on that basis. Thank you
I understand your argument Neil and yes, Zoho is a powerful and progressive product which does eat into Act! market share, I know that because I have customers move to it from Act!. However Act! holds a position in the marketplace where, by nature of it being a Windows installed product as well as web capable, provides useful unique solutions to many. In terms of your issue with Outlook sync and the exhaustive detail of working with Swiftpage you so usefully published here, is remarkable and a credit to you. For myself, I didn't have faith in the sync integration as provided at that time and with which you had issue. We chose, at that time, not to recommend it to clients.
07-28-2018 12:21 AM - edited 07-28-2018 12:22 AM
I understand your frustration.
I have for a long time recommended using Act4Outlook which just works with practical features answering all your problems.
And it's only $37 one-off purchase! Worth every penny/cent !!
07-28-2018 02:28 AM
07-30-2018 01:47 AM
07-30-2018 01:25 PM
I suggest that you make use of the Status attribute and that a status of 'Assigned Defect Number' be allocated to threads where Swiftpage has issued a defect number. Then they are readily grouped. Such as was once done for Share Your Ideas as here.....
You might like to commence with a defect my client has a strong interest in; Defect number D-07472, first issued September 2017 I believe. :-)