> For the complete documentation index, see [llms.txt](https://docs.messageflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.messageflow.com/rcs/rcs-flow-studio-creating-messages-and-scenarios/features-shared-by-content-nodes.md).

# Features shared by content nodes

Content nodes (Text, File, Card and Carousel) share a set of features that make it easier to build, check and close the conversation: the Auto-forward connection, Preview node, single-node testing and Reaction to inactivity.

#### Auto-forward connection

Each content node has two outputs. The Message Input output defines where the conversation goes when the recipient replies with typed text. The Auto-forward connection output lets you send the next node immediately after the current one — without waiting for the recipient’s reaction.

This way you can combine several messages into one sequence. For example: you add a Text node and, below it, connect a Carousel node via Auto-forward connection. The recipient will receive both messages one after another: first a short introduction, then right after it the carousel with the offer.

*Example: Text “We have new arrivals from the autumn collection for you” → (Auto-forward connection) → Carousel with four products and “View” buttons.*

{% hint style="info" %}
Good practice: use Auto-forward connection to link nodes that together form one thought (e.g. teaser + offer). Set the buttons and further conversation paths in the last node of the sequence — that is the one the recipient will respond to.
{% endhint %}

#### Preview node

Below each content node on the canvas there is a Preview node button. Clicking it opens a preview showing how the recipient will see the configured node — handy for quickly checking the content and layout before you launch the campaign.

#### Test this node

In the properties of each content node you will find the Test this node section. It lets you test a single element of the flow without launching the whole campaign: enter a phone number and click Send — a test message with this one node will be sent to that number.

{% hint style="info" %}
Tip: use a phone with an active RCS service for the test. The test covers only the selected node — to check the entire conversation path, go through it “as the recipient” once the flow is live.
{% endhint %}

#### Reaction to inactivity

Reaction to inactivity lets you define what should happen if the recipient does not react to a message within a set time. You configure it directly in the properties of the given content node, in the Reaction to inactivity section — choose the behavior in the Action field. The default value is Null, which means the conversation simply waits for the recipient’s reply.

<figure><img src="https://1762163817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDIGjHYIXYoHyJoOeeUgD%2Fuploads%2FucqbaXMdQpqWzu4pDw2H%2FZrzut_17.png?alt=media&amp;token=a18c738f-dc9e-44bb-a0c1-389488a85d9f" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Timer or Reaction to inactivity? Both mechanisms respond to time passing without a reply from the recipient. Timer is a separate node on the canvas that holds the path for a set time and — with Cancel on user action turned on — stops working when the recipient reacts. Reaction to inactivity is set in the content node itself, without adding another node — it works well when you want to handle a lack of response to a specific message.
{% endhint %}
