Seems tricky to build whilst optimizing for message number (SMS is expensive if you're poor) and usability (large % of users are poorly educated).
As we roll out two-way messages, I've been contemplating internationalization. Date formats are somewhat universal, but for things like shift swapping - I think that we could overcome a lot of usability issues by adding Spanish support quickly.
Regarding cost and education - we also learned in user tests that we still need to support a print schedule. We're in the process of building that out. Our focus is on making structured, accurate scheduling data available to other systems (such as payroll). If that means that we need to focus on a printable view, that's fine :-)
I built it last year. It has basic white-label support, but I'd be happy to work with you guys to integrate the UI more closely with what you already have.
I'm working on a better landing page with screenshots; in the meantime here is a PDF with more info: http://www.blackchair.net/hubfs/SMS_Inbox.pdf
I'll be digging into the beta :).
Lots of API goodness: https://textit.in/api/v2
For my current product I'm looking for a human-human SMS interface in a browser. Ideally, it should just drop-in and work.
SMSInbox pulls outbound messages directly from Twilio logs and creates an embeddable iframe interface. Does Textit.in offer similar functionality?
I do have other ideas that involve bot replies but have some concerns due to the complexity of the workflows in this product. There are dozens of variables involved.