Skip to main content

Campaigns and broadcasts

Campaigns enable asynchronous bulk messaging. A campaign is created automatically on the first message that uses a given campaign_name. This name must match the configuration set used in the conversation. Each campaign has its own queue, daily limit, and orchestrator.

Sending rate

Messages with a lower priority value are processed first: 1 is the highest priority and 5 is the lowest. Messages with the same priority use FIFO order. When a campaign reaches its daily limit, the next job is moved to START_HOUR on the following day. Use separate configuration sets when different rules are required.

Message types

GIA accepts three message types:
  • direct_message: sends content directly to the contact.
  • system_with_ai: gives content to the AI so it can produce the message.
  • whatsapp_template_message: sends a WhatsApp template with its parameters.
See Send campaign message for the external endpoint’s authentication, payloads, and responses.

Monitoring

Monitor messages and queues under Campaigns → History.
The endpoint response only confirms that the message entered the queue. Connection, phone number, channel, Meta, or delivery errors only appear when the message is processed.