Go to website
Use the articles here to understand how to test your flows and troubleshoot errors.
Tracking and Managing Opt-Outs
You may want to inform your contacts that they have the ability to opt-out at any time. Here's how to track and manage those that do so: Using an SMS gateway Twilio will automatically unsubscribe your contacts (preventing them from receiving a response) when they send a message containing one of the following keywords: STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, and QUIT. START and YES will opt contacts back in to the messages if and only if they’ve been unsubscribed. HELP and INFO wi
Twilio Trial Numbers
Twilio allows users to try out their platform using a trial number. A Twilio trial number, however, is not sufficient for testing. A number must be purchased from Twilio in order for messages to be sent or received. Learn how to purchase and connect a Twilio number here. If you'd like to test your flows prior to committing to a Twilio number, you can begin with an Android or [
Why Didn't My Message Send?
Occasionally, a message will not send properly or will not be received by a contact. When this happens, you can track down the exact error by checking the message log. View these logs on the platform by clicking on the document icon to the right of the message in the contact's history. In the log, you can see whether the message was sent by TextIt and passed to the aggregato
Troubleshooting Delivery Errors
This guide is intended to help you troubleshoot delivery errors on SMS channels. There are a few possible causes depending on the channel you're using: Android Channels An Android channel will experience sending issues if: the phone doesn't have a steady internet connection the phone doesn't have a strong cellular connection the Nyaruka Android app is toggled to "paused". Log into your account, navigate to your account page, and then click your Android
A/B Testing your Flows
Within the platform, you can use the Split Randomly action to create equally distributed pathways through which your contacts will randomly pass, enabling you to test the efficacy of your flows. We also provide a handy simulator on the same page you build your flows to allow you to test them as you build. Outside the platform, we encourage you to send real messages
Best Practices: Testing your Flows before Launching
Using the simulator is an excellent way to test a flow while building, but nothing beats a real-world test before you launch. Conducting test-runs with real phone numbers or social media channels will help you avoid common problems such as message content errors, flow logic mistakes, failed messages, channel connectivity issues, and much more. This is why we consider it a best practice to test before you
Why conduct a usability test?
Why conduct a usability test? Now that you've chosen the perfect flow, you can conduct a usability test to make sure it provides a good experience for your contacts. Usability tests encourage you to focus on your contacts’ experience by assessing ease of use and learnability. This step is important - it allows you to make the best possible impression when you send out the final version of your flow. Usability test requirements A large group of test contacts representative of you
Conducting a Pilot Test
After testing your flows in the simulator, you’re ready to move to the second step in our recommended testing protocol: the pilot test. A pilot test, or "pilot," is your first trial run; a small-scale version of your larger project, and arguably the most important step in testing your SMS program. Your SMS program will be an automated system comprised of multiple components (contacts, phones, carriers, channels and flows). Moreover, it represents your project - so it's best to test each one thor