User Tools
goldsms_blast
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
goldsms_blast [2014/02/17 18:17] stevengraff |
goldsms_blast [2014/02/17 20:50] stevengraff |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| {{::scheduled_other_action_for_blast.png?500|}} | {{::scheduled_other_action_for_blast.png?500|}} | ||
| - | Tip: The way to do a blast, or broadcast, is to define a filter or group in GoldMine, then do a group schedule operation, using the options as above, but scheduled en masse for the filter or group. | + | |
| + | It’s all well and good to send a single ad-hoc text to a contact… but what if you’d like to send out a thousand? You can do that by creating a contact group or filter, and scheduling an Other Action for the entire filter or group en masse. | ||
| + | |||
| + | Or, if you’re skilled with GoldMine’s Automated Processes, you can configure an AP event to instantly react to one or more conditions in GoldMine by scheduling a text message for immediate delivery. | ||
| + | |||
| + | The GoldSMS component that does this is called GoldSMSBlast, and it turns Text sending into a true client/server process, with GoldMine, as the client side, setting the flag in the calendar table, for GoldSMSBlast to operate on on the server side. | ||
| Blast checks GoldMine's cal table every 10 seconds by default. | Blast checks GoldMine's cal table every 10 seconds by default. | ||
goldsms_blast.txt · Last modified: 2014/02/17 20:50 by stevengraff
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
