Should we prioritize coding for "out-of-app messages?"

I was thinking: does it make sense to send a message, like through a in-app screen that can be 'printed', an email, a text message, or the like, that includes the information people need to actually make the delivery?

I already wrote the copy for a pop-up screen that shows up on the platform after the delivery; it's right here: https://docs.google.com/document/d/1DAxB7nN-rikKENXGyGnM-elES-sTFF3xbYkjzBmxVCw/edit#bookmark=id.4yj92tm27wu6

But, it would also be useful for us to build the functionality for people to save the information they need in platforms they're likely to engage with.

I remember @dpollock talking about the https://www.intercom.com/ resource to utilize communication AI and communication decision trees that get people the info they need.

For example, if a requestor asks for a product somebody can supply, then a supplier gets an email/text for a specific need to be filled; or
If a supplier 'delivers' a product in the platform, then they get an email saying 'Expect a delivery!'

All of those functionalities. Is it worth working to build this in, or is it more work than should be created for the 1st iteration? I don't think so, but wanted thoughts.

Review the linked Google Doc copy and the Intercom reference first. This issue has no named files, tests, or implementation entry point; done would require a documented decision about whether out-of-app messaging belongs in the first iteration and a concrete scope for the supported triggers and channels.

Written by the indexing model from the issue text.