Bring messages into the queue
The intended connector would associate LINE conversations with a connected business account and inbox source.
Integrations LINE
LINEPlanned
LINEPlannedLINE conversations, planned for Message Inbox.
Explore the planned LINE messaging connector: incoming customer messages, agent replies and source filters in one support workspace.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
Messaging
What we’re planning to connect.
- 01LINE
- 02Planned connection
- 03Message support
Reply in context
The planned response path should keep replies on the original LINE conversation and respect provider messaging rules.
Keep customer identity scoped
A display name is not sufficient to merge a LINE contact with a private order or an existing customer account.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Connected business account
Permitted messages
Provider-scoped customer ID
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Identify the business account and the region where your customers use LINE.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Test duplicate delivery, an expired reply window and two contacts with the same display name.
Before you connect
LINE integration questions
Can I connect LINE to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Test duplicate delivery, an expired reply window and two contacts with the same display name.