The objective is to respect the campaigns sending frequency for scheduled follow-up in email automation.

This option prevents you from sending emails to contacts that do not wish to receive your campaigns and Email automation.

Should accept:

1. domain.tld format to block the entire domain
2. user@domain.tld format to block a single email

Clients need to be able to visualize queue length for each step in email automation.                            

Enable WebHook to the interface for users to enter a URL to receive a notification on every email automation event.

Add centralized signature interface that can be called by using snippet {signature}

It will also define :

Sender profile (name, email, address) used by default in campaigns.

Add contact filtering capabilities to filter contacts based on email validation status. (valid, invalid, blocked, accept-all)        

Stopping a campaign when all contacts have reached the end of their email automation.

The objective is to provide a more user-friendly interface to choose from:

1- creating a new thread by entering a new subject line in the follow-up

2- Continue the current thread by not entering a subject line for the follow-up.

This feature is already enabled in the backend system and with early-stage implementation at the user interface.

The objective is to add Custom Fields Buttons to the HTML Designer at the campaign template.

The objective is to provide a filtering mechanism in the Prospector Contact List and enable CSV exports to respect the filter.

Filters may include: valid, invalid, accept-all, blocked

Automatic unsubscription of contact when replying with the word "unsubscribe."

The objective is to correctly manage numbers used in custom fields. /{147}/ gives problem.

Error:

SyntaxError: Invalid regular expression: /{147}/: Nothing to repeat

The objective is to enable email autoresponder on new contact list subscription activated from the subscription forms in WordPress websites. 

The system should support:

1. Automatic Response after subscribing
2. Sing Opt-in and Double Opt-in which means an email confirmation to be added to the list is required.
3. Email automation for Drip Campaigns or email series for nurturing (not intended for follow-ups)

The objective is to add double opt-in subscription processing to the MailRush subscription form.

Capabilities for Link redirect

Message customization

The objective is to allow email personalization to be used inside of the content spinning syntax.

Currently this is unsupported: {Hi {full_name}|Hello {first_name}}

The objective is to provide SSL support for link tracking. Currently, the system is using a tracking subdomain as a cname example. track.domain.com. The idea is to replace the CNAME host by using the A record for the MailRush MX and to implement SSL to be used as the tracking url.

The objective is to provide a fallback term for custom fields when their value is empty or undefined. It would be an extension of the manage labels section.

Export event timestamp for open, clicks, reply events.

Provide basic storage for images to be used in email templates. Premium Feature.

Split view showing the HTML code on one side and on the other side the previous. Modifications to the HTML code will reflect the changes in real-time on the preview side.

The objective is to provide the user with a way to reply to an email directly from the inbox section of MailRush. While this is not critical, a centralized way to reply is desirable.