A wild feature appears! Email forwarding your replies
We managed to drag ourselves away from Pokemon Go for long enough to build something into Clockwork which we think will help you out.
Introducing email forwarding for any of your keywords (which are free by the way) and Clockwork long numbers.
Traditionally we’ve kept things HTTP only when forwarding your replies because that’s the normal way you’d expect to interact with an API. With Clockwork now integrating with Bond Adapt and a few users asking us if there was a way of testing their replies while they’re setting up the web endpoints, we thought it’d be a good opportunity to put the mail servers to work.
Setting it up
When you add a keyword on our shortcode, you’ll see the option to add email forwarding after you’ve picked your keyword.
Under the “Receiving” menu you’ll now see an option for email forwarding. All of your existing long numbers and keywords can have up to 5 email addresses assigned to them and we’ll forward everything, including STOP requests. If you’ve got a full email inbox, a bad email address or we can’t get an email to you, we’ll slowly back off attempts to send and eventually stop trying to send to you.
We’d highly recommend adding
email@example.com to your safe senders list to reduce the chance of your messages getting caught by spam filters.
What about HTTP Forwards?
HTTP is still our preferred method of getting replies to you because it’s faster, doesn’t have spam filters and it’s generally more reliable. We’d really like you to use HTTP for a full 2 way SMS integration. You can use HTTP alongside Email forwarding and an SMS that’s forwarded by HTTP will still be Email forwarded (and vice versa).
Email forwarding is a great way of copying in a team of staff if your customers reply with something that your app isn’t ready for. Or as a quick way of getting something running while you flesh out the backend of your app.
If you want a hand getting started, or have any questions please get in touch