[freeqaz]

Thanks for the help. I'm just trying to think about how it'd work.

It's probably more useful for the cloud version of our product, thinking about it more. At least if we're using Courier primarily to notify leads/customers.

In that case, would it make more sense to integrate Courier as a separate service or pipeline for managing engagement? Where is the line between something like MailChimp and Courier?

[tejaskumthekar]

Gotcha! I think easiest way would be a. You'd configure Mailchimp details (api key etc) inside Courier's provider/integrations interface b. Invoke Courier API and Courier would route it to Mailchimp

["a" can be any integration Courier supports - so it could be Twilio for SMS for instance] ["b" changes based on how you invoke the API - so you could do send just an email via Mailchimp, send just an SMS via Twilio OR both email and SMS OR SMS if email fails and so on --- this logic is configurable via both UI and API]

[freeqaz]

Ahhh, okay thank you for clarifying. The "stacked notifications", especially if something fails, makes total sense. That is what made it "click" in my head where Courier fits in the stack.

I remember Troy explaining this when we spoke about picking the best "channel" to actually reach somebody, but I guess I forgot.

[troygoode]

> Where is the line between something like MailChimp and Courier?

Mailchimp has two services: a marketing tool for e.g. newsletters and a transaction email service (previously called Mandrill). Most customers use Courier alongside marketing tools like Mailchimp's newsletter tools - we're more for your active users, not marketing to potential users.

We do integration with Mandrill / Mailchimp Transactional to add our orchestration, preference management, routing, templating, etc. tools so that you don't have to build those yourself on top of their pipes.