Tips

Why an SMS from a call scenario doesn’t arrive: a mistake in element order

← All articles

This is one of the most common requests to our support, and it almost always sounds the same. “The scenario has an SMS element, the report shows that contacts pressed the key, but not everyone got the message. Where did the sends go?”

They didn’t go anywhere. They never happened. The fault isn’t in the system, it is in the order of elements in the branch. It takes fifteen seconds to fix.

How a scenario actually runs

A scenario is a chain of elements that the call goes through step by step. Audio played, on to the next element. Key pressed, off to the matching branch. And so on to the end.

The key point is that a live call goes through the chain. While the contact is on the line, the steps run one after another. As soon as they hang up, the call ends, and everything further down the chain doesn’t run. Ever. It isn’t a delay, and it won’t “send later”. The next step simply never happens.

The “SMS to contact” element is no different from audio in this respect. It isn’t put in a separate queue that gets worked through after the call. It fires at the exact moment the call reaches it along the chain. Reached it, the message went out. Didn’t reach it, it didn’t.

The trap almost everyone falls into

Here is what happens next. Someone builds a branch and reasons logically: first we warn the contact, then we send.

“Thanks for your answer! You’ll get an SMS with a link in a moment” → send SMS.

As polite conversation, this is flawless. As a phone call, it is a trap. Having heard “you’ll get an SMS in a moment”, the contact got the main point and often hangs up right on that phrase. They don’t listen to the end, it is all clear to them already. And the call drops exactly between the warning and the send.

The most frustrating part is that the clearer and more polite your audio, the more sends you lose. The contact hangs up precisely because you explained it well.

This happens especially often in branches after multi-branch elements, where the contact pressed a digit or answered by voice. By that point they have already made a decision, consider their part of the conversation done and are least of all inclined to listen for another ten seconds.

The right order: send first, then speak

The fix is embarrassingly simple. Swap the two elements.

✕ How it is usually built

Branch “pressed 1”Play audio: “You’ll get an SMS with a link in a moment”
↓
NextSend SMS to contact

Hung up during the audio, and the SMS didn’t go out.

✓ How it should be

Branch “pressed 1”Send SMS to contact
↓
NextPlay audio: “You’ll get an SMS with a link in a moment”

The SMS went out right away. The audio is for those who stay on the line.

Sending happens instantly and doesn’t need the contact to stay on the line. The message goes out the moment the call passes through the element. After that the person can hang up whenever they like, they will get the SMS anyway.

The phrase doesn’t lose its meaning either. “You’ll get an SMS in a moment” plays after the message has actually been sent, but for the contact there is no noticeable difference. The message still arrives within a few seconds.

The same goes for HTTP request and “SMS to me”

A lost SMS to the contact is only half the trouble. It is much worse when, for the same reason, an HTTP request to your system doesn’t run.

A typical setup looks like this. The contact pressed “1” to book an appointment, next comes the audio “Thank you, you’re booked, goodbye” followed by an HTTP request to the CRM. The contact heard “goodbye”, did exactly what you told them and hung up. The request didn’t go out, there is no lead in the CRM. The person is sure they are booked, but your system has no record of them.

“SMS to me”, the notification to a manager about a new hot lead, gets lost the same way. The rule is general and simple. Everything that has to outlast the call goes before the audio, not after it. Audio comes last in the branch.

How to check that an element ran

No need to guess, the report shows everything element by element. Open the campaign and look at the results table, where each scenario element has its own column.

  • “+” in a cell means the call reached the element and it ran. For SMS, this means the message was sent.
  • An empty cell means the call never got to the element. Either the contact hung up earlier, or the call went down a different branch.

If the SMS element’s column is empty for a noticeable share of contacts who did reach the right branch, you have found your problem. Compare two columns, the branching element and the send element. The difference between them is exactly your lost messages.

The builder now warns you itself

We added a check for this case to the scenario builder. If in some branch a send element comes right after audio, the error panel shows a tip with an explanation and a “Swap” button. It swaps the two elements and reconnects the arrows for you.

It is a tip, not an error: it doesn’t stop you from saving and launching the scenario. We have no right to forbid an order that may be deliberate. But keeping quiet about a pitfall almost everyone steps into would be wrong too.

When the reverse order makes sense

There is one honest case when the audio goes before the send on purpose. That is when the SMS should go only to those who listened to the end. Then the audio works as a filter, screens out those who are not interested, and you don’t pay for messages nobody was waiting for.

It is a valid strategy, especially if the SMS in your scenario is long and costs noticeable money on a large list. Just make sure you chose this order deliberately, not by accident. Only you can see the difference between these two situations.

Quick checklist

  • In every branch, the send (SMS, SMS to me, HTTP request) comes before the goodbye audio.
  • Audio is the last element of the branch, not the second to last.
  • Everything that must outlast the call runs before the contact is given a reason to hang up.
  • After launch, compare the branching element and send element columns in the report. A big gap means losses.
  • If the audio before the send is there on purpose as a filter, keep it, but make sure it is your decision.

The rule in one line. Do it first, talk about it after. On a phone call, the contact leaves whenever they want, and anything you put off “for later” may never happen at all.

Frequently asked questions

Why doesn’t every contact get the SMS from the scenario?

A send element fires at the moment the call reaches it along the chain. If an audio recording comes before it and the contact hangs up before it ends, the call simply never reaches the send element, and the message doesn’t go out. The longer the audio before the send, the bigger the losses.

In what order should SMS and audio go in a scenario?

Send element first, then audio. Sending happens instantly and doesn’t need the contact to stay on the line, and the phrase “you’ll get an SMS in a moment” plays after the message has actually gone out. The contact gets the SMS either way, even if they hang up on the first word.

How can I tell whether the SMS element ran on a specific call?

In the campaign results table, each element has its own column. If the element ran, its cell for that call shows “+”. An empty cell means the call never reached the element. Either the contact hung up earlier or the call went down a different branch.

Does this also apply to HTTP request and “SMS to me”?

Yes, fully. These elements follow the same rule: they run only when the call has reached them. If the request to your CRM sits after the goodbye audio, some leads won’t make it into the system even though the contact has already agreed.

Is the reverse order ever needed on purpose?

Yes. If the SMS should go only to those who listened to the message to the end, the audio is placed before the send on purpose and works as a filter. In this case the builder shows a hint but doesn’t block anything. The decision is yours.

If you are unsure about your scenario, build it and run a test call to your own number right from the builder. Hang up in the middle of a branch and check the report for what managed to run and what didn’t. It is the fastest check there is.

Build a scenario that loses nothing

The builder will flag the element order, and a test call will show the result before you launch the campaign.

Try it free →