LINE Service Messages Explained: When to Use Them and When to Use a Webhook

LINE service messages are a LINE MINI App feature for sending important notifications that respond to, or confirm, a user’s action inside the MINI App. They are not the same thing as a general LINE Messaging API push, a free-form chatbot reply, or a customer-service inbox. Use them for approved transactional updates; use a webhook intake when the job is receiving and routing user messages.

Key takeaways

• LINE’s official documentation defines service messages as LINE MINI App notifications connected to a particular user action.
• A service message needs a reviewed service message template and a service notification token.
• LINE documents examples such as reservation completion and reminders, and says a single reservation action can send up to five service messages.
• If your team needs to receive LINE messages, triage support, or route chat across LINE, WhatsApp, Zalo, and other channels, design that as an inbound webhook layer instead.
• For the adjacent decision, read LINE Service Messages vs Messaging API and the implementation detail in sending service messages with a notification token.

What LINE service messages are

The official LINE Developers guide describes service messages as a LINE MINI App feature that notifies users about information they should know in response to, or confirmation of, a user action inside the MINI App. The important boundary is the trigger: the message follows a user action in the MINI App, such as a reservation or purchase-related step.

That makes service messages a narrow transactional notification tool. They are useful when your product already runs as a MINI App and you need a controlled message after a user action. They are not a replacement for a live support inbox, a multi-agent message queue, or a generic outbound campaign system.

The official service-message path

LINE’s documented path has three moving pieces:

1. Add a service message template to the LINE MINI App channel in the LINE Developers Console.
2. Pass the template review before using it with the Service Message API.
3. Issue a service notification token after the user action and send the service message with that token.

The same LINE guide says templates are selected from templates provided by LY Corporation, and that up to 20 service message templates can be configured per LINE MINI App channel. For a first implementation, treat the template inventory as a product-design constraint, not just a backend task.

A useful planning checklist:

Question	If yes	If no
Is the message tied to a specific MINI App user action?	Consider service messages.	Use another messaging or support path.
Do you already have a LINE MINI App channel?	Prepare templates and tokens.	Service messages are probably not your first integration.
Can the content fit an approved template?	Submit and test the template.	Rework the notification or use a different channel.
Do you need users to reply and start a support conversation?	Add a separate inbound queue.	Keep it as a one-way notification flow.

Where templates differ from LINE chat UI choices

Do not confuse service message templates with Messaging API chat templates. LINE’s Messaging API docs describe template messages such as buttons, confirm, carousel, and image carousel templates. Confirm templates contain two buttons; quick replies can show up to 13 reply buttons on supported messages.

Those UI objects help a LINE Official Account conversation ask the user for a choice. Service messages are a MINI App notification mechanism with its own token and review flow. If the search question is “what are LINE service messages?”, the shortest answer is: reviewed MINI App notifications after a user action, not a general-purpose chat template.

When a webhook intake is the better layer

If the user can respond, ask a new question, or move from LINE to WhatsApp, Telegram, Zalo, TikTok, or X, the integration problem changes. You no longer only need to send a controlled notification. You need to receive inbound events, verify them, store them, and route them to the right human or AI workflow.

UnifyPort’s API reference documents a normalized message.received event for LINE and other supported providers. The event envelope carries fields such as id, type, provider, account_id, occurred_at, and data; the message data includes data.conversation, data.sender, and data.message. Webhook delivery can be protected with signing_secret and HMAC-SHA256 verification. See the deep docs for standard webhook events and signature handling.

A typical intake payload looks like this shape:

{
  "id": "evt_2f9c1a4b7e",
  "type": "message.received",
  "provider": "line",
  "account_id": "acc_8c21d0",
  "occurred_at": "2026-06-08T12:34:56Z",
  "data": {
    "conversation": { "id": "line_user_123", "type": "user" },
    "sender": { "id": "line_user_123", "type": "user", "name": "Jordan Lee" },
    "message": {
      "id": "msg_10472",
      "text": "Can I change my reservation time?",
      "direction": "inbound",
      "sent_at": "2026-06-08T12:34:55Z"
    }
  }
}

That is a different job from service-message sending. One confirms the action; the other becomes your durable intake contract.

Decision rule

Use LINE service messages when the notification is tied to a MINI App action, fits a reviewed template, and does not need to become the primary support inbox. Use a signed webhook intake when the main job is to receive, classify, and route messages from LINE or multiple platforms.

If you are still comparing official LINE surfaces, start with LINE Service Messages vs Messaging API. If you are ready to build the inbound layer, open the standard webhook events reference and register the intake endpoint first.

FAQ

Are LINE service messages the same as Messaging API push messages?

No. Service messages belong to LINE MINI App and are tied to user actions and templates. Messaging API push messages belong to the LINE Official Account messaging surface.

Do service messages receive user replies?

The service message itself is a notification mechanism. If users need to reply and your team needs to route the conversation, add an inbound webhook queue.

How many service message templates can a MINI App channel configure?

LINE’s service-message documentation says you can configure up to 20 service message templates per LINE MINI App channel.

What should I read next?

For official service-message implementation, read UnifyPort’s notification token guide. For inbound support, read the webhook event reference.

Sources checked on 2026-08-27

• LINE Developers: Sending service messages
• LINE Developers: Message types
• LINE Developers: Use quick replies
• LINE Developers: Re-review after updating your verified MINI App