Overview

WhatsApp Direct Send allows messages to be sent directly from a Journey node without waiting for Meta's standard template pre-approval process.

This feature is useful for sending time-sensitive, one-time messages without creating reusable WhatsApp templates. Direct Send messages are created and managed within individual Journey nodes.

Create a Direct Send Message

Follow these steps to create a Direct Send message in a Journey:

1. Open the required Journey and navigate to the WhatsApp node. Refer here to create a new WhatsApp journey node.

2. Open the template picker.

3. Select Direct Send from the available options.

   Note: Direct Send appears only when the feature is enabled for the WABA and no active restrictions prevent its use.

4. Select the message type:

   • Text: To create a text-based message.
   • Media: To create a message containing media.

5. Configure the message using the existing template editor. Add the required message content, media, and call-to-action buttons, as applicable.

6. Save the message.

The Direct Send message is saved specifically for the selected Journey node. It is not added to the reusable WhatsApp template list.

Edit a Direct Send Message

An existing Direct Send message can be updated from its associated Journey node.

1. Open the Journey containing the Direct Send message.
2. Navigate to the WhatsApp node.
3. Reopen the Direct Send editor.

The editor displays the previously saved message. Make the required changes and save the configuration.

Changes update the existing message within the same node. A separate message copy is not created.

Message Delivery

At the time of sending, Direct Send uses a dedicated delivery process instead of the standard WhatsApp template-send process. This allows messages to bypass Meta's usual pre-approval requirement.

Important Considerations

• Node-specific configuration: Each Direct Send node maintains its own message configuration.
• No template reuse: Direct Send messages are not available in the reusable template list.
• Independent messages: Messages created in different nodes, including nodes across different Journeys, are stored separately.
• WABA-level availability: Direct Send availability depends on feature activation and the restriction status of the WABA.

Frequently Asked Questions

Q. Why is Direct Send not available in the template picker?

A. Direct Send may not be enabled for the WABA, or the WABA may be under an active restriction. Contact the Netcore account team or support to verify availability.

Q. Can a Direct Send message be reused in another Journey?

A. No. Each Direct Send message is associated with an individual Journey node. Messages cannot currently be shared or reused across nodes.

Q. Why does Direct Send not require Meta's pre-approval?

A. Unlike standard WhatsApp templates, Direct Send follows a dedicated delivery process that checks the message after it is sent rather than requiring Meta's approval beforehand.