| Project: | SMS Framework |
| Version: | 6.x-2.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi all,
I have written a basic archive module that will provide an audit trail of all outgoing and incoming messages. It uses SMS Framework hooks, implements Views for reporting, and installs one database table. There is a full archive view on the module settings page, and the module will trigger a watchdog message on enable/disable.
The reason I did this is because I was concerned about the traffic that was flowing in and out of our SMS system. Mainly because incorrect use of SMS messaging can expose us legal implications, but also to mitigate any unneccesary costs.
But looking at the report was even better than that because I was able to see some interesting behavior: While putting my first SMS sales lead generation campaign live, I quickly learned that our "thank you" reply message contained an opt-out clause, causing many users to panic that they had subscribed to something, and had consequently opted out immediately.
Anyway, please take a look and let me know whether you think it would be good to include it, or to submit this as a separate module.
Thanks very much!
~ap
| Attachment | Size |
|---|---|
| sms_archive.zip | 7.11 KB |
Comments
#1
Update. Fixed Views hook and adjusted text.
Found a caveat: The incoming gateway will not be captured unless the gateway module writes it's identifier to $options['gateway'] before passing to the SMS Framework.
#2
This has been committed at the sms_track module
#3
Automatically closed -- issue fixed for 2 weeks with no activity.