Monday, October 13, 2008

New Feature: Include CC Addresses

JangoMail has added the ability to specify a CC (carbon copy) address that will be visible to message recipients. You may also use personalization coding in this CC field as you compose your messages.

The CC feature allows you to specify an address that will receive a clear (address IS visible to the email's direct recipient) copy of the message as it is sent out. It is found under Advanced Options as you compose in the Send E-mail tab.



For example, you send a personalized message that starts: Dear Kim, Dear Joe, Dear Susie, etc. Kim, Joe, and Susie each receive their individual emails, showing the appropriate personalization. At the same time, the address given in the CC field also receives 3 emails: copies of the separate messages for Kim, Joe, and Susie.

You may want to specify a single address to receive the CC. This can be used to create an arachive for businesses with compliance needs, for example.

You can also use our personalization coding to send the CC email to an address stored in each record in your database. For example, addresses might have a particular representative assigned to them. The email can be copied to a customer's specific representative, while the message itself may be "From" the main corporate headquarters.

From Address: announcements@browniekitchen.com
CC Address: %%repemail%%
(where data associated with each address record contains a field called "repemail")

Then, Kim, Joe, and Susie would each see that their own representatives were copied on the messages as well -- also a good reminder of that direct contact information should the recipients have any questions.

Note: When using the CC feature, JangoMail is generating two emails for every one recipient address. This will double your email sending volume for pricing purposes. If you use this feature along with our BCC feature, then you will be tripling your volume for pricing purposes.

Friday, October 10, 2008

New Feature: Add Personalization to the BCC field

JangoMail has added the ability to use personalization coding in the BCC field as you compose your messages.

The BCC feature allows you to specify an address that will receive a blind (address not visible to the email's direct recipient) copy of the message as it is sent out. It is found under Advanced Options as you compose in the Send E-mail tab.

For example, you send a personalized message that starts: Dear Kim, Dear Joe, Dear Susie, etc. Kim, Joe, and Susie each receive their individual emails, showing the appropriate personalization. At the same time, the address given in the BCC field also receives 3 emails: copies of the separate messages for Kim, Joe, and Susie.

Previously, you could only specify a single address to receive the BCC. This was often used for businesses with compliance needs that required an archive of messages sent.

Now, you can use our personalization coding to send the BCC email to an address stored in each record in your database. For example, addresses might have a particular representative assigned to them. The email can be "signed" from the representative in the message body:

Regards,

%%repname%%
%%repemail%%

Now, these representatives can also receive a behind-the-scenes copy of what "they" sent out via the JangoMail system, so that they won't be surprised with direct responses from their clients. If this data is stored in a field called "repemail" for each record, just put %%repemail%% in for the BCC.

Note: When using the BCC feature, JangoMail is generating two emails for every one recipient address. This will double your email sending volume for pricing purposes.

Thursday, October 09, 2008

New Feature: Specify an SMS Text Message

JangoMail has added an SMS Text Message feature to our Messages composition page. Now you can send a specific message to an SMS address, instead of the HTML or Plain Text message types. Be courteous to your recipients receiving messages by text and build a message tailored to them.

You will find the new field on the Messages composition screen, under the SMS tab. Specify a message here for any text users. If an email address is in one of the listed SMS email gateway domains, then this SMS Text Message will be sent from your JangoMail account instead of the standard HTML/Plain Text multipart message.


If the SMS Text Message field is not set, and a recipient's domain is an SMS email gateway domain, then the email message will be assembled as normal, including the HTML Message, Plain Text Message, and any attachments.

A full list of SMS email gateways is available at http://en.wikipedia.org/wiki/SMS_gateway.

The following properties are ignored when an email message to an SMS email gateway is assembled:
  • Open Tracking
  • Click Tracking
  • Wrapping
  • Plain Text Message
  • HTML Message
  • Attachments
  • Triggers

Friday, October 03, 2008

New Feature: Calendar/Time controls added to Send E-mail page

JangoMail has made it easier to get the format right when entering date/time information for scheduling emails to be sent in the future or on a recurring schedule.

We have introduced new calendar and time controls for these fields to help you get it right the first time.

How do you use the new tools? Look to the right of the scheduling fields for the calendar and clock symbols.



Click on the calendar to set the date.



Now, click on the clock to set the desired time.



You'll wind up with the right format each time.

Thursday, October 02, 2008

New API Methods and Enhancements

JangoMail has launched some new API methods, and some enhancements to earlier methods.

Retrieve Complaint Data

JangoMail now allows you to pull the data behind the "Complaints" column of your General Job Statistics report via the API. This reflects addresses that have used their "this is spam" reporting tools via their ISP, which JangoMail receives via feedback loop.

Check Job/Campaign Status

Once you send, your campaign goes through three stages:

  • Preprocessing -- where the message is prepared for sending, removing duplicates, bounces, unsubscribes, etc. prior to sending.
  • Sending -- where the message is personalized and launched from our network of senders.
  • Complete -- where your campaign has fully completed sending.

These states are shown in the JangoMail interface under Reporting, and you can now confirm the current status of any campaign by API as well.

GetMassEmailStatus returns the current status for the given job/campaign ("Preprocessing", "Sending", or "Complete").

Enhancements to the "Send..." Methods

The CustomCampaignID can now be specified in the "Options" parameter of the "Send" methods (SendMassEmail, SendMassEmailPrevious, SendMassEmailPrevious2, SendMassEmailRaw). For example, Options can now include the following parameter: CustomCampaignID=FinalMailer.

Attachments will now validate during sending. This will alert you if you specify an attachment in the "Options" parameter that does not exist on the server. Previously, such a campaign would still go through, but missing the attachment, and the method would return a SUCCESS message. Now if the attachment doesn't exist, an exception will be thrown and no campaign will be sent or saved.

Enhancements to AddGroupMember and EditGroupMember

JangoMail has a new setting to prevent duplicates from being added to a Group. With the API, the AddGroupMember and EditGroupMember methods reflect this change as well. Both will now throw exceptions if the Group is set to disallow duplicates and you:
  • attempt to either add an already existent address, or
  • edit an address such that it would match an already existent address.

For the full web-based reference on all available methods and their signatures, including the new methods and enhancements, click here.

New Feature: Prevent Duplicates in Groups

JangoMail now allows you to prevent duplicate addresses from being added to a Group.

To turn this setting ON, go to Groups and E-mail Addresses and select your Group. Click the "Enable/Disable Duplicate Members" button in the right hand pane.


With this setting enabled, if you attempt to add an address to a Group that already contains that address, it will prevent the new entry. The method of adding a Group member will not affect this setting.

Manual entries will display an error, and imports will skip addresses already in the Group. If you are using a web site sign up form, the user will get an error if they are already in the Group, preventing a second entry for that email address.

Note the difference between this and a Scrub (Scrub Group Members), for a Scrub does not prevent duplicates from being added--it just clears duplicate entries (by email address) when executed.

Note: If you enable this setting on a Group that already has duplicates, the existing duplicates are NOT deleted unless you run a Scrub.