Sending overview

With OMNI Agent, you INSERT a record into the msg_tran table and the Agent collects it automatically and sends it through the channel API.

Send flow

Send flow

1Customer system

msg_tran INSERT (msg_status = '1')

2Collector

Collect recipients → enqueue

3Sender

Communication API call

4Receiver

Receive the report → update the status

Common fields

These are the fields shared by every channel.

ColumnRequiredDescription
channel_orderSend channel order. Single (sms) or Fallback (alimtalk,sms)
recipientRecipient number. Domestic: 01012345678 / International: 821012345678
msg_statusFixed to '1' (waiting to send)
request_dateSend request time (NOW() or the reservation time)
callbackSender number. Required when you send text or RCS. You can specify one per channel, separated by ;
priorityPriority (veryfast / fast / slow). Defaults to slow when omitted
payment_codeDepartment code used for settlement
ttlSend time-to-live (seconds). Defaults to 86400 (24 hours) when omitted
etc_text_1~3User-defined fields

channel_order channel keywords

Channel keyword (channel_order)

Fallback (failover)

If you list channels in channel_order separated by ,, the send switches automatically to the next channel when the earlier channel fails.

Automatic failover

channel_order: alimtalk,rcs,sms
Alimtalk On failureRCS On failureSMS

If the preceding channel fails, it switches to the next one automatically. You can specify up to 3 channels (2 failovers).

Specify the sender number (callback) for Fallback

When you send text (SMS/LMS/MMS) or RCS, separate the sender numbers with ; so that they line up with the channel order.
Alimtalk and Brand Message do not use a sender number, so leave their slots out.

TEXT
channel_order: alimtalk,rcs,sms
callback:      ;01500000001;01500000002
              ↑ alimtalk(omitted) ↑ rcs   ↑ sms