Template-type LINE notification messages combine LY Corporation's predefined text with details such as delivery dates or reservations, then send them by phone number. This guide covers setup and testing in Lumo after approval.
For initial inquiries and applications, see Applying to use LINE notification messages.
Official information checked on September 9, 2026. The steps focus on LINE Official Accounts in Japan.
What you need to use this feature
You need an approved LINE Official Account and recipient phone numbers to send template notifications.
- An Enterprise plan in Lumo
- The sending LINE Official Account connected to Lumo, with the notification application completed
- All reviews and procedures required for the intended purpose completed
- Phone numbers and details to include, such as delivery dates or reservation numbers
- A connected HubSpot or Klaviyo integration if you send from that service
Even with templates, six uses require UX review: points awarded, coupon acquired, points expiration, coupon expiration, miles awarded, and miles expiration. Check the conditions for each purpose in the template UX guidelines updated September 8, 2026.
Consulting Marketing Agent
Marketing Agent can help organize the purpose, sending timing, and information to merge into a notification.
For example, ask it to prepare a shipping confirmation with the tracking number and delivery-status link. Compare the prepared content with your approved purpose. Lumo's execution approval is separate from LY Corporation's service approval and UX review.
For manual setup:
- Create a notification template
- Create an Auto Send Message that uses it
- Add notification delivery to a Workflow or integration
- Test with designated recipients before starting regular delivery
Creating a notification template
Save notification content under "Automation" > "LINE Notification Messages" in Lumo.
- Click "Create LINE Notification Message"
- Enter a recognizable "Name", such as “Shipping confirmation”
- Choose the "Region" matching the sending LINE Official Account; choose "Japan" for a Japanese account
- Select the appropriate "Template key", using categories or search to narrow the list
- Fill in "Item Settings" and "Button Settings"; optionally add "Highlighted Item Settings"
- Check the preview on the right, then click "Save content"
The official title, description, header, and footer aren't freely editable. Region selects the templates for the sending account; it isn't a translation setting. See LINE Developers' template, item, and button lists.
If an official template isn't available in Lumo, ask your representative about support instead of substituting a different purpose.
Setting items and buttons
Enter the facts needed for the notification and link buttons to pages related to that notification.
For a shipping confirmation, use items permitted for that purpose:
| Setting | Example | What to verify |
|---|---|---|
| Template key | Shipping confirmation, shipment_completed_ja
|
Trigger it after shipment is completed |
| Merge key and value | Tracking number from the carrier | The number belongs to this order |
| Highlighted display text | Expected delivery date, September 12 | The final value stays within 15 characters |
| Button label and URL | Check delivery status, with the tracking URL | It opens the correct shipment |
Lumo supports up to 15 regular items, two buttons, and one optional highlighted item. Choose button labels from the provided options.
Using variables
Use variables that match the data supplied by your sending system. A tracking number passed from Klaviyo Flow can use {{ data.trackingNumber }}. Entering a variable name alone doesn't supply a value; the Flow must pass data with the same name.
LINE display names and other friend-specific data may be unavailable for phone-only recipients. Use data supplied by the source system and test empty and long values. The highlighted item's 15-character limit applies after variable replacement.
Personal information and destinations
Don't include names, phone numbers, email addresses, addresses, or other explicitly identifying information in the notification body. Authenticate recipients before displaying personal information on a linked page. Link to information related to the notice, not advertising. Template UX guidelines
Creating an Auto Send Message
Select the saved notification template in an Auto Send Message so a Workflow or integration can call it.
- Open "Automation" > "Auto-Send Messages"
- Click "Create auto-send message" and enter a name
- Choose the LINE notification message type
- Select your notification template
- Click "Save content"
A template-type Auto Send Message must contain exactly one notification. Don't add text, images, or other message types to it. Before sending, make sure the message is active.
Editing a shared notification template changes its content wherever it is used. Check its usage before changing a template already in operation.
Setting the timing and recipients
Use a notification action or integration that sends by phone number.
Sending from a Lumo Workflow
- Open the Workflow under "Automation" > "Workflows"
- Set the sending LINE Official Account and a trigger matching the approved purpose
- Add "Send LINE Notification Message"
- Select the prepared notification in "Auto-send message"
- Check the target customer's stored phone number and save
Lumo Workflows use the phone number stored for the target customer. This screen isn't for entering a list containing only phone numbers. To notify HubSpot contacts or Klaviyo profiles before they add you as a friend, configure the corresponding service integration. Creating a Workflow
Sending from a HubSpot workflow
Add Lumo's LINE notification message action to a contact-based workflow.
| Field | Value |
|---|---|
| Recipient phone number | The contact property containing the phone number |
| LINE Official Account | The approved sending account |
| Auto message | The prepared notification Auto Send Message |
| Country-code completion | Japan (+81) when using a Japanese domestic-format number |
Don't enter content directly in Message 1–3. Check re-enrollment conditions for recurring notifications. LINE actions in HubSpot workflows
Sending from Klaviyo Flow
In the Auto Send Message details, get the Klaviyo Flow connection information for the sending account. Copy the webhook configuration to the Flow and pass the recipient's phone number and order data. Use phone numbers with country codes. Sending from Klaviyo Flow
Testing before launch
Check the preview, then send through the same route you will use in production to designated test recipients only.
- Verify that the test phone number matches the number registered on LINE
- Enable receipt of notification messages and make sure the test account hasn't blocked the sender
- Restrict the Workflow or Flow to test customers
- Activate the Auto Send Message and test the trigger
- Check the received body, merged values, and button destinations on a device
- Confirm the results before setting the regular audience and timing
You can also test template notifications with "Delivery confirmation" in the Auto Send Message editor. Select a friend registered as a test recipient for the sending account, and ensure their customer record has a phone number. Test external variables and recipients who aren't friends through HubSpot or Klaviyo as well.
If LINE requests SMS verification, follow its instructions. See the receiving flow for details.
Checking results and missing deliveries
Successful send processing doesn't necessarily mean delivery to the recipient is complete.
For HubSpot or Klaviyo sends, check the sent and delivered timestamps in the Auto Send Message's recipient list. Non-friends appear as "Notification recipient". Template notifications don't support open tracking. CTA button clicks can be recorded when tracking is enabled. For Lumo Workflows, also check the execution history.
| Problem | What to check |
|---|---|
| Can't select a template | Enterprise plan, correct region and filters, and Lumo support for the template |
| Can't save | Highlighted text within 15 characters and no mixed message types |
| Empty merged values | Matching variable names and data available for that trigger |
| Nothing is sent | Active message, trigger conditions, approved sender, and valid phone number |
| Success shown but nothing received | Matching LINE phone number, receiving settings, blocks, and SMS verification |
| Empty opened timestamp | Expected for template notifications; use delivery and clicks instead |
See the technical specifications for receiving requirements and the difference between request success and delivery completion. Don't repeatedly resend the same notification without checking the cause.
If the issue continues, contact support with the Lumo ID, sending account, notification name, sending time, Workflow or Flow, and displayed error.