Message Queue - Possible errors

These are common errors that can arise when setting up your message queue.

• An alert is issued when trying to save a message configured in the queue.

How to fix it?

💡 Solution: This alert indicates that you did not configure a default WhatsApp account when starting the initial setup of your message queue. This account refers to the sending source.

To fix it, go to your message queue list, click edit, and indicate the WhatsApp account, as shown below.

Save the configuration.

• I set up a sending sequence on a specific date and time, but the messages were not sent and no error appeared. How can I fix this?

💡 Solution: You may not have configured the message in the correct sending order. The message sending system works as follows: the message in the first position of the queue will be the first to be processed; this sequence is the system default. Check the example below:

In this example, the goal was for the message scheduled for June 29 to be sent first. But since it is second in the queue, the system will wait to send the first message, the one from July 1.

Fix it by reversing the order of the cards in the correct sequence.

• I carried out a test using a token in the message, but the token did not work. How can I fix this?

💡 Solution: If you clicked the test icon as shown in the image below, entered your test number, and received the message with the token code without the lead identification, don't worry... All message sending tests carried out in SprintHub DO NOT decode the tokens, since test sends do not have real leads.