Message Queue - Possible errors

These are common errors that may arise when configuring your message queue.

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

How to resolve?

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

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

Save the configuration.

• I set up a sequence of sends at a specific date and time, but the messages were not sent and no error was shown. How to resolve?

💡 Solution: possibly you did not configure 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 a system default. Check the example below:

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

Fix it by swapping the order of the cards into the correct sequence.

• I performed a test using a token in the message, but the token did not work. How to resolve?

💡 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, rest assured... All message send tests performed on SprintHub DO NOT decode tokens, since test sends do not have real leads.