View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 07346 | Feature requests | Import/Export | public | 2009-10-07 15:18 | 2014-05-03 21:35 |
| Reporter | Assigned To | c_schmitz | |||
| Priority | normal | Severity | feature | ||
| Status | closed | Resolution | fixed | ||
| Summary | 07346: timed generation of tokens and mail sendout | ||||
| Description | to use limesurvey as a customer survey tool. a customer database is synchonising with limesurvey. so new users appear in this table, for this we need to log in and send these new customers a survey. | ||||
| Additional Information | A possible solution: timed sending. allso with big surveys, this can be used auto email the survey to groups 100 each time to avoid spam problems. | ||||
| Tags | No tags attached. | ||||
| Bug heat | 8 | ||||
| Git branch / Pull Request URL | |||||
| Users affected % | |||||
|
Related to this I think that will be desirable if I can specify a time interval (or throttle valve) to send each email (invitation or reminder) in order to avoid spam problems. |
|
|
This mail send-out could be maid from a new customer or trigered by a recent customer contact to the call center of instance |
|
|
The problem with automatically sending email invitations or reminders is that someone has to trigger the process. The best solution for this is a stand alone script which can be called at a certain interval by the server by using cronjobs. Have a look at the availabe Limesurvey Cronjob Script (http://www.limesurvey-templates.com/limesurvey-cronjob-scripts-c-29.html) at the Limesurvey Template Shop: http://www.limesurvey-templates.com/index.php |
|
|
This is now possible using RemoteControl2. You can write a small program that is started every x minutes and using that function you can send out invitations. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-03-12 14:45 | c_schmitz | Note Added: 24672 | |
| 2013-03-12 14:46 | c_schmitz | Note Edited: 24672 | |
| 2013-03-12 14:48 | c_schmitz | Status | acknowledged => resolved |
| 2013-03-12 14:48 | c_schmitz | Resolution | open => fixed |
| 2013-03-12 14:48 | c_schmitz | Assigned To | => c_schmitz |
| 2014-05-03 21:35 | c_schmitz | Status | resolved => closed |