Share article:
Fail-safe your application with Social Sending
Getting an unwanted (and sometimes illegible) message late at night from a good friend is almost instantly forgiven, but how long would it take to forgive getting a message from a business during the night?
Businesses conduct their activities in traditional business hours usually from 8-6pm and customers expect their relationships with businesses within or close to these hours. However, it’s not uncommon for businesses to process activities in batches after hours due to low-activity. This works well for the business but the same cannot be said for the customers. Why? Batch processes usually involve sending out notifications to customers and more often than not, these occur at odd hours, causing disruption to the customers.
What if your application was to enter into an unexpected recursive loop and started spamming all your customers with notifications? Restarting the servers should fix it, right? Imagine if this was to happen at 2am. Chances are you wouldn’t be able to get someone to look at the problem until the following morning and that is ONLY if you identify the problem in the first place. It would be nice to have a safety net to fall back to. We call this safety net “Social Sending”.
By enabling this no-cost feature, you can ensure messages are only sent during 8am to 6pm, or “sociable hours” and messages sent outside of these hours are scheduled to be released at 8am the next day. The business logic and code has already been added for you and all you need to do is ask for the feature to be switched on. After all, why reinvent the wheel when you have a perfectly functioning one waiting for you?
