new mtt journey: client or server side?

[tttp]

background

proca has two main mtt modes: client and server

on the server side mode, the action (including the list of targets) is sent to the server, and the server is delivering the email on the behalf of the supporter

on the client side mode, the action is sent to the server but the client opens the configured mail client (or webmail) with a pre-fill email and the supporter needs to click send from their mail client to properly send.

Both options have their pros and cons:

server:

• pro: more control on the delivery eg drip delivery, tracking of bounces, ability to switch to digest delivery
• con: easier to block by the target (comes from the same server/smtp envelope sender) and quite expensive (external delivery service)

client:

• pro: completely distributed and virtually unstoppable
• con: less visibility on the actions and the journey is a bit more clunky/potentially broken

we have mitigated some of the con, for instance instead on relying on the "mailto" being properly configured, we check if the email of the sender is google and use their own gmail.com/"create new email" url

improvement

why not implementing a dual server-client mode?
in that mode, check if the client has a high chance of working:

• on a mobile (iphone and android handle properly mailto)
• or with google suite/gmail.com domain name
• ? other criteria could be added

if the client can send emails, add a step:

how do you want us send the email?
if you can, try to send it from your device, it has more impact

** button: send it from my device **
this will open your mail client with the subject and content pre-filled, you just have to click send
** button: send it on my behalf **
we'll send it from our infrastructure

...text to be finetuned...