🎯 Description
The “Try now” section lets you test your AI’s behavior before (or without) connecting an official line. There are two test modes:
• Test on WhatsApp
• Manual tests
────────────────────────────────────────
A) 📱 Test on WhatsApp
1) Open the “Test on WhatsApp” section. You will see:
• A QR code to scan with your phone.
• The “Open in WhatsApp” button to start the conversation on the current device.
• A dropdown list to choose the starting pipeline.
2) You’ll be taken to a WhatsApp screen with a default message:
<alphanumeric code> Hi, how are you?
⚠️ Important: do not delete the alphanumeric code between “<>”. That code identifies the AI you want to test. You can edit the text after it (“Hi, how are you?”).
3) Send the message and chat freely with the AI.
💡 This option shows you how your AI Worker conversation would look on WhatsApp without having connected an official line yet.
────────────────────────────────────────
B) 🧰 Manual tests
1) Go to the “Manual tests” section.
2) At the top you’ll see these options (from left to right):
• “Start test from pipeline”: a dropdown to begin the conversation from the start of the selected pipeline.
• “View chats”: opens the test conversation within the “Conversations” section.
• “Reset conversation”: clears the current test’s history to start a new test.
3) In the conversation area, you can run as many tests as you want and evaluate the AI’s performance by sending messages, checking responses, and fine-tuning the flow based on the results.
────────────────────────────────────────
📝 Notes and best practices
• “Reset conversation” in Manual tests is equivalent to sending the message: #reset
(Applies to: Test on WhatsApp, Manual tests, and also when the line is connected to Meta’s official API).
• After sending #reset, wait for the AI’s confirmation that the history has been cleared. Only then start a new conversation.
• If you make any changes to the AI’s configuration (of any kind), send #reset so the AI picks up the new change and you can test with the updated configuration.
• 📊 Both testing methods do not affect production metrics. Therefore, they’re the recommended option to evaluate your Worker’s performance without impacting real reports or analytics.
• Test common scenarios, but also difficult or ambiguous queries.
•Repeat tests after major changes, not just the first time.
•Use realistic test messages, similar to what an actual customer would send.
When should you use it?
- To check whether the flow responds as expected.
- Before launching a new configuration.
- After making changes to a Pipeline, Stage, or Worker.
- To validate an improvement before it affects real conversations.
- During team training processes.
- To compare expected vs. actual results.