Would Courier be a good fit for an Open Source product like what we're building[0]?
Hey hey! yep I think Courier can totally be a good fit! Do you have a way to expose any plugin-like interface which can connect to external services? I'd be more than happy to contribute! Feel free to reach out anytime :)
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?
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.
["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]
I remember Troy explaining this when we spoke about picking the best "channel" to actually reach somebody, but I guess I forgot.