What are the responsibilities and job description for the Mail Revolution position at mypresta.rocks?
Newsletters sent from the same address as order confirmations share one reputation, and a single bad campaign is enough to push receipts into spam. Mail Revolution keeps bulk sending on its own verified identity, builds audiences from your customer and order data and sends from your own server, on your schedule.
Email Campaigns – Mail Revolution treats a shop's mail as two different jobs. A letter goes to one customer – a review invitation, a quote follow-up, a post-delivery check-in – and it should read as though a colleague typed it. A newsletter is a broadcast and should be built and delivered like one. Both live inside PrestaShop, sharing campaigns, templates and audiences at the top and splitting into two strictly separated delivery paths underneath, where a campaign, a template and a sender profile will only pair with their own kind.
A message that looks like a person wrote it
The personal pipeline starts from a specimen: one real email exported from the mail client your team actually uses. Its MIME structure, its signature with the embedded images, its client fingerprint and its plain-text part are all preserved, and only the body is swapped per recipient. There are no tracking pixels, no rewritten links and no campaign markup of any kind, so what arrives carries the same structure as mail written by hand.
Approved recipient by recipient, on the record
Manual and semi-automatic campaigns create a queue item for each recipient, and each one waits for votes from the employees allowed to give them. The queue shows the exact rendered email for that customer; staff edit the personal paragraph inside the preview, leave comments for one another and vote. An edit invalidates earlier approvals, every decision carries the employee's name, and an append-only log keeps the actor, shop, action, reason and outcome. Sending installs disabled and refuses to run until a healthy default sender and a secure unsubscribe route exist.
Keep sensitive back-office actions protected and attributable
Templates combine customer, order and shop variables with conditional blocks – trade against retail, a recent order against a settled one – and rotating phrase variants, so identical wording is the exception rather than the rule. Variant choice is deterministic per recipient, which is what makes a preview a promise instead of a sample. Every template holds a version for each shop language, and publication is gated by a linter that checks syntax, unknown variables and the review-request wording that gets merchants into trouble.
The audience is your order data, read at send time
Recipient rules are built from live PrestaShop data: products bought, order states, dispatch and delivery dates, workflow statuses, support threads and consent flags. There is no export, no separate contact database to keep in step and no connector to an outside platform that can quietly stop syncing. Customers with an open support issue are deferred rather than silently dropped, and every message is checked against suppression lists, bounce history and a one-per-campaign guard immediately before it is handed to the transport.
Give every recipient a signed one-click unsubscribe
A broadcast campaign requires its own verified sending identity – a dedicated subdomain or an SMTP provider – and every message carries HTTPS List-Unsubscribe and one-click headers backed by shop-specific signed tokens, with bounce and complaint handling behind them. The link exposes no email address and creating the same suppression twice changes nothing. Bulk volume stays off the address your team writes from, which is how the bulk-sender requirements the large mailbox providers enforce stay away from your day-to-day mail.
No external platform needed to run it
PrestaShop 1.6 through 9 on PHP 7.1 or newer, multishop-aware, open code, and nothing outside your own shop is required to operate it. Back-office actions require POST, an authenticated employee and a matching shop and token, so a stray link cannot fire a campaign. Suppressions are indexed by email hash with only masked addresses on screen, the queue resists duplicates through unique constraints, row locks and leases, and campaign history, consent evidence and the audit trail are deliberately left in the database when the module is removed. Scheduling runs on the shared MPR cron infrastructure.
- Bulk volume never touches your own address. Newsletters go out on their own verified identity, so bulk volume never rides on the address your team writes from every day.
- Cloned from a real message. Campaign messages start as an actual message exported from your mail client, keeping its structure, signature and plain-text part instead of a template layout.
- Nothing leaves without a person saying yes. Hold every message for a named colleague to review and edit before sending - and loosen to semi-automatic or scheduled modes once a campaign has earned it.
- The preview is the message. What the approver saw is precisely what the customer receives - wording, variables and variant choice are locked the moment a message is approved.
- No exports, and no sync to break. Targeting reads your orders and consent flags at send time, so an audience is never a stale CSV.
- Sent at the pace a person sends. Personal campaigns respect a daily cap, working hours and randomised gaps, spreading sends the way a person actually writes email.
- Review requests checked before they publish. The template linter flags incentive wording and satisfaction-conditioned asks that commonly conflict with Google review policies and UK fake-review rules.
- Your consent evidence outlives the module. Suppression lists, consent evidence and the audit trail are deliberately preserved in the database even if the module is removed.
Email Campaigns – Mail Revolution treats a shop's mail as two different jobs. A letter goes to one customer – a review invitation, a quote follow-up, a post-delivery check-in – and it should read as though a colleague typed it. A newsletter is a broadcast and should be built and delivered like one. Both live inside PrestaShop, sharing campaigns, templates and audiences at the top and splitting into two strictly separated delivery paths underneath, where a campaign, a template and a sender profile will only pair with their own kind.
A message that looks like a person wrote it
The personal pipeline starts from a specimen: one real email exported from the mail client your team actually uses. Its MIME structure, its signature with the embedded images, its client fingerprint and its plain-text part are all preserved, and only the body is swapped per recipient. There are no tracking pixels, no rewritten links and no campaign markup of any kind, so what arrives carries the same structure as mail written by hand.
Approved recipient by recipient, on the record
Manual and semi-automatic campaigns create a queue item for each recipient, and each one waits for votes from the employees allowed to give them. The queue shows the exact rendered email for that customer; staff edit the personal paragraph inside the preview, leave comments for one another and vote. An edit invalidates earlier approvals, every decision carries the employee's name, and an append-only log keeps the actor, shop, action, reason and outcome. Sending installs disabled and refuses to run until a healthy default sender and a secure unsubscribe route exist.
Keep sensitive back-office actions protected and attributable
Templates combine customer, order and shop variables with conditional blocks – trade against retail, a recent order against a settled one – and rotating phrase variants, so identical wording is the exception rather than the rule. Variant choice is deterministic per recipient, which is what makes a preview a promise instead of a sample. Every template holds a version for each shop language, and publication is gated by a linter that checks syntax, unknown variables and the review-request wording that gets merchants into trouble.
The audience is your order data, read at send time
Recipient rules are built from live PrestaShop data: products bought, order states, dispatch and delivery dates, workflow statuses, support threads and consent flags. There is no export, no separate contact database to keep in step and no connector to an outside platform that can quietly stop syncing. Customers with an open support issue are deferred rather than silently dropped, and every message is checked against suppression lists, bounce history and a one-per-campaign guard immediately before it is handed to the transport.
Give every recipient a signed one-click unsubscribe
A broadcast campaign requires its own verified sending identity – a dedicated subdomain or an SMTP provider – and every message carries HTTPS List-Unsubscribe and one-click headers backed by shop-specific signed tokens, with bounce and complaint handling behind them. The link exposes no email address and creating the same suppression twice changes nothing. Bulk volume stays off the address your team writes from, which is how the bulk-sender requirements the large mailbox providers enforce stay away from your day-to-day mail.
No external platform needed to run it
PrestaShop 1.6 through 9 on PHP 7.1 or newer, multishop-aware, open code, and nothing outside your own shop is required to operate it. Back-office actions require POST, an authenticated employee and a matching shop and token, so a stray link cannot fire a campaign. Suppressions are indexed by email hash with only masked addresses on screen, the queue resists duplicates through unique constraints, row locks and leases, and campaign history, consent evidence and the audit trail are deliberately left in the database when the module is removed. Scheduling runs on the shared MPR cron infrastructure.