Miscellaneous Suggestions

Christopher,
I am very new to the NS Pro product and am still learning.  Here are just a couple of suggestions for your consideration.

1.  When you have defined a newsletter and saved it, it would be nice to send a "test email" so you can ensure that images are displayed properly and that all the links are problem working when a client receives the email.  This was a nice feature when we had used MailChimp.

2.  Default Mailing List.  When you create a new newsletter, the default appears to be to send it to ALL subscribers.  I think it might be better to force the user to select a mailing group versus defaulting to all subscribers.  The reason for this is that someone may forget to define the mailing list.  This could result in subscribers receiving newsletters that are targeted for another audience.  Forgetting to define the mailing list is a situation that I can see happening when it takes a few days to finish a newsletter.  If you don't do it at the start,  you just may forget.  

Thanks again for your work.
 

I'll have to look at the toolkit. Maybe from a ease of use, it would be nice to be able to send the test email on the page where your constructing the email without having to save, go out to the toolkit and then come back in.

As for the default newsletter, let me get back to you on this a bit afte I think about this more. My first thought is I would rather force a user to select a mailing list BEFORE the newsletter can be saved. The reasoning is if you are targeting a specific newsletter for promotions and send it to all subscribers, it could be viewed as SPAM cause they never agreed/signed up for that particular content. I think that is what I would prefer to avoid. I have to run but I'll think about this some more and throw a few suggestions out there for your consideration.

Great extension!!

We sent out our first newsletter today without any issues. The cron job worked like a charm. As for sending a TEST .. I think a toolbar option when constructing the newsletter for sending a TEST would be great. The toolkit option for sending a test, while I do not think optimal, it really wasn't that big of a deal.