Change Log

QuickProsp release v1.30.0 changed the default opt out for new cold campaigns. Recipients are now asked to reply to stop instead of clicking an unsubscribe link, and the bulk mail unsubscribe headers that mailbox providers use to file mail as promotions are left out, so cold emails go out as plain messages with the opt out as the last line. Existing campaigns keep their current settings.

A reply to stop request can meet the CAN-SPAM opt out rule, but Gmail and Yahoo require one click unsubscribe headers from bulk senders, so higher volume teams should check this new default before relying on it.

QuickProsp v1.27.0 adds a Personalized and Merge tags switch to the email preview and the live editor preview, and the preview now names any merge tag that has no data for the previewed contact instead of quietly substituting neutral wording. Campaigns are also saved as drafts automatically from step 2 of setup, with a Save draft and exit button.

A tag pointing at a field that was never imported previously looked correct in preview and only went wrong in the recipient's inbox, so senders now get a real check on what goes out before launch.

QuickProsp shipped four feature releases between 8 and 19 September. They add conditional sequence branches based on prospect responses, a separate tracking domain for each sending domain, warmup limits per mailbox with an API endpoint to set them, scheduled replies and wider automatic suppression. Version 1.26.0 on 19 September adds Microsoft permissions that let warmup mark messages as read and move them out of Junk.

Most of this is sending discipline: tracking aligned to each sender and warmup controlled mailbox by mailbox. The Microsoft change asks for broader mailbox permissions, and existing connections pick them up when reconnected, so admins should know what they are granting.

QuickProsp released version 1.19.0, introducing AI driven campaigns that research prospects and draft personalized emails against a campaign specific offer. The update adds support for bringing your own OpenAI, Anthropic or Gemini API keys, custom Message IDs for SMTP sending, an option to skip List Unsubscribe headers, and a bulk mailbox deletion API endpoint.

Bringing your own model key removes the markup on AI credits and puts the model choice in the buyer's hands. The List Unsubscribe toggle cuts the other way: one click unsubscribe headers are a bulk sender requirement at the major mailbox providers, so shipping an option to omit them is a control a compliance minded team will want switched on rather than off.