Currently the only way to setup response messages is through entries to the Action & Response models. For more complex systems, this is probably the best setup, however for quick sites, it may be best to have a setting such as the following:

DJANGO_TWILIO_SMS_RESPONSES = {
    'STOP': 'Your request to stop messages has been received.',
    'START': 'Your request to receive messages has been received.',
    ...
}

https://django-twilio-sms-models.readthedocs.org/en/latest/ is referenced in README.rst but it has not been setup.

Currently Twilio will handle STOP, START & HELP messages for long codes only: Twilio support for STOP, BLOCK, and CANCEL (SMS STOP filtering). However, these messages are typically needed to be handled internally as well.

While they could be handled internally by setting up replies in DJANGO_TWILIO_SMS_RESPONSES it may be best to check for these messages by default and setup a signal.

If DJANGO_TWILIO_SMS_RESPONSE_MESSAGE = True and a phone number has been unsubscribed by Twilio a TwilioRestException is raised with the following message "The message From/To pair violates a blacklist rule."

Need to implement an internal subscription list of unsubscribed numbers which checked against for sending a response message.

I haven't figured out how to solve this yet but thought I'd go ahead and report it. For new projects using this app, Django is confused about the DB migrations and ends up throwing InconsistentMigrationHistory.

Steps:

1. Create new Django Project. I used Django 1.10.
2. pip install django-twilio-sms-models
3. Add 'django_twilio' and 'django_twilio_sms_models' to INSTALLED_APPS
4. Add required settings like TWILIO_ACCOUNT_SID
5. Run ./manage.py migrate to configure
6. Run ./manage.py makemigrations to see error

Error:

django.db.migrations.exceptions.InconsistentMigrationHistory: Migration django_twilio_sms.0002_auto_20160512_2117 is applied before its dependency django_twilio_sms.0001_squashed_0005_auto_20160410_1948 on database 'default'.

Running ./manage.py showmigrations shows the first, squashed migration is skipped somehow: (trimmed some built-in models output)

django_twilio
[X] 0001_initial
django_twilio_sms
[ ] 0001_squashed_0005_auto_20160410_1948 (5 squashed migrations)
[X] 0002_auto_20160512_2117

I don't understand how it's bypassing 0001_squashed... But that prevents any DB migrations in the entire project since Django is confused. It both considers it not run but also apparently not important enough to run.

A method to setup response messages needs to be created. Either through admin, or views.