How to configure one-time messages and business hours ​

One-time messages are automatic WhatsApp texts sent at most once per situation. In AvenPing, open Settings → One-time messages, pick a line, set weekly hours, then enable Welcome message, Away message, and optionally Contact request. Click Save.

Prerequisites ​

  • An active WhatsApp line. The page asks you to activate a line before you can configure messages.
  • A timezone that matches when your team is actually open.

Step-by-step ​

  1. Open One-time messages
    Go to Settings → One-time messages. Select the WhatsApp line.

  2. Set weekly business hours
    Enable each weekday you are open. Choose start and end times and a timezone (for example Asia/Kolkata). Away messages send only outside these hours (once per closed period).

  3. Configure Welcome message
    Toggle Welcome message and write the body. It is sent once when Meta sends request_welcome, or on the first inbound message for that contact on this line. It is off by default.

  4. Configure Away message
    Toggle Away message and write the body. It is sent once per closed business-hours period when a message arrives outside hours. Off by default.

  5. Review Contact request and save
    Contact request is sent after the first inbound when the contact has no phone number, using Meta’s fixed “Share contact info” button. It is on by default. Click Save.

TIP

Keep welcome and away copy short. Do not duplicate a chatbot greeting that already fires on first message, or contacts will see two openers.

FAQ ​

Why did nobody get the away message?

The contact messaged inside business hours, already received an away message this closed period, or the toggle is off. Check timezone.

Is Contact request the same as the chatbot Request Address node?

No. Contact request is a Meta share-contact button on first inbound when the number is missing. The chatbot Request Address node is disabled in Components.

Do one-time messages use template credits?

They are session/utility automations Meta allows for this Cloud API feature, not Broadcast campaigns. Still keep copy policy-safe.