many times I run into a situation where, for all sorts of different reasons: schedules, meetings, underground or on a plane, asleep someone I intend to send a message or response to is unavailable or the timing would be less than idea BUT no one, not them, not me know exactly WHEN WOULD BE ideal.

So the Textra user composes the message and INSTEAD of scheduling a send being what controls the timing of the send , the Textra user sets a TRIGGER such that (for instance) ANY/the next received message from that person immediately results in the pre-composed message being sent/delivered at that time (upon receipt).

Once that core functionality is stable, enhancements could include:

) third party (any party/persons') received text triggering send

) above functions starting a scheduled send. That is ' a received text acts to set a scheduled send at "T" plus '5' minutes, or any user definable number of minutes delay/schedule.

) Other events or conditions trigger send