LINE Confirm Template: Two Actions, Buttons Four, and What to Use Next

A LINE confirm template is the right choice when the user must choose between exactly two actions: yes or no, accept or decline, confirm or cancel. If you need three or four visible actions, use a buttons template. If you need a temporary menu with more choices, use quick replies. If the choice is visual or item-based, consider a carousel or Flex Message instead.

Key takeaways

• LINE’s official message types page describes confirm templates as a text slot plus two buttons.
• The Messaging API reference lists confirm template fields as type, text, and actions; the actions array is the two-button decision point.
• A buttons template is a different template type and supports up to four action objects, which is why our separate LINE buttons template alternatives guide starts there.
• Quick replies can show more choices, but LINE documents them as temporary buttons that can disappear when the chat moves on.
• UnifyPort is not a replacement for LINE’s native template UI. It fits after the tap or user reply, when you need to receive and route LINE messages alongside WhatsApp, Zalo, Telegram, TikTok, and X.

What LINE officially means by “confirm template”

LINE’s message types documentation lists template messages as predefined layouts: buttons, confirm, carousel, and image carousel. In that list, a confirm template is specifically described as text plus two buttons. The Messaging API reference is the deeper source for the object shape and describes the confirm template as a template with two action buttons.

That narrow shape is intentional. A confirm card should not become a miniature menu. It works best for binary decisions:

• “Confirm booking” / “Cancel”
• “Use this address” / “Edit address”
• “Talk to support” / “Keep browsing”
• “Approve” / “Reject”

If your copy needs to explain four paths, or if the user is choosing from product categories, a confirm template is already the wrong component.

Confirm template vs buttons, quick replies, carousel, and Flex

LINE surface	Best for	Main interaction limit	When to choose it
Confirm template	One binary decision	Two action buttons	A clear yes/no or accept/decline step
Buttons template	A compact card with a few primary actions	Up to four action objects in the template	Three or four equally important choices on one card
Quick replies	A temporary next-step menu	Up to 13 quick reply buttons, but they can disappear	Short-lived choices that should be answered immediately
Carousel template	Browsing repeated items	Multiple columns with consistent structure	Products, plans, locations, or similar cards
Flex Message	Custom visual hierarchy	More JSON and rendering checks	Branded layouts or information-dense decisions

For teams coming from search queries such as “LINE Messaging API confirm template actions limit,” the practical answer is: do not force a confirm template past two actions. Choose the component that matches the shape of the decision.

If you are comparing this with a LINE MINI App custom action button, read the MINI App custom action button implementation guide first. MINI App sharing, LIFF, and Messaging API templates are related LINE surfaces, but they are not the same API task.

A practical decision tree

1. Is the user making one binary choice? Use a confirm template.
2. Do you need three or four visible actions on one card? Use a buttons template.
3. Do you need five to thirteen immediate choices? Use quick replies, and design for the fact that the buttons are not permanent.
4. Are the choices repeated objects such as products or locations? Use a carousel template.
5. Is the problem layout, hierarchy, or branding? Use a Flex Message, then test the final object across devices.
6. Is the real job receiving the user’s reply and routing it to your backend? Keep the official LINE UI where it belongs, then put the inbound event into a signed queue.

Where UnifyPort fits

UnifyPort does not send LINE confirm templates, buttons templates, quick replies, carousel templates, or Flex Messages as native LINE UI components. Use LINE’s official Messaging API when the message your account sends must render as one of those components.

UnifyPort fits the inbound side: once a LINE user replies, the same webhook handler can process that event alongside other messaging platforms. The documented event envelope uses real fields such as id, type, provider, account_id, occurred_at, and data; for incoming messages, subscribe to message.received.

{
  "id": "evt_01j7lineconfirm8p7m4w6n2a",
  "type": "message.received",
  "provider": "line",
  "account_id": "acct_line_support_01",
  "occurred_at": "2026-08-25T09:30:00Z",
  "data": {
    "message": {
      "id": "msg_line_4281",
      "direction": "inbound",
      "type": "text",
      "text": "Confirm"
    },
    "conversation": {
      "id": "conv_line_2841"
    },
    "sender": {
      "id": "user_line_73"
    }
  }
}

For the product boundary, check the UnifyPort provider message support matrix before choosing an outbound design. If your next step is receiving replies reliably, the webhook events reference is the deeper implementation path.

This is the same architectural split discussed in LINE Service Messages vs Messaging API: use the official LINE surface for native LINE presentation, then keep customer-service intake separate and normalized.

Limitations and trade-offs

Choose the official LINE Messaging API when you need exact LINE-native presentation, Official Account features, template delivery analytics, rich menu behavior, or Mini App-specific flows. Choose UnifyPort when the harder problem is receiving messages from ordinary operational accounts and routing them into one backend across multiple platforms.

The important rule is not “use one tool for everything.” It is to keep UI rendering and inbound intake as separate decisions.

FAQ

How many actions can a LINE confirm template have?

A confirm template is designed for two action buttons. If the decision has more than two choices, use another LINE message type.

Is a LINE confirm template the same as a buttons template?

No. LINE lists confirm and buttons as separate template message types. Confirm is for two-choice decisions; buttons templates cover a compact card with more primary actions.

Can quick replies replace a confirm template?

Sometimes. Quick replies are useful for temporary choices and can show more buttons, but LINE documents conditions where they disappear as the conversation continues. Use them when the user should answer immediately.

Does UnifyPort send LINE confirm templates?

No. UnifyPort is relevant when you need a normalized inbound webhook after the user replies, not when you need to render LINE-native template UI.

Next step

If your flow depends on LINE-native templates, implement the message UI with LINE’s official Messaging API. If your flow depends on collecting replies from LINE and other platforms in one backend, review the UnifyPort webhook events reference and connect the inbound queue.

Sources

• LINE Developers: Message types
• LINE Developers: Messaging API reference
• LINE Developers: Use quick replies
• LINE Developers: Flex Message elements

Checked on 2026-08-25.