- Teams serving markets where LINE is already a standard support channel.
- Deployments that need one inbox across LINE and the rest of the support stack.
- Flows where AI should answer first, then hand sensitive cases to operators.
LINE channel
Run an AI support agent inside LINE.
Use LINE when your customers already write there and you want webhook-based inbound messages, AI replies, operator handoff, and the same runtime as your other channels.
- LINE dialogs appear in the same Conversations view, operator flow, and usage tracking as your other channels.
- The agent can answer from knowledge, call APIs, and keep the conversation moving inside one thread.
- Operators can take over the same LINE dialog without moving into a separate LINE-only tool.
- LINE is activated through Messaging API credentials and a public webhook URL, not through a single bot token.
- The current connector is text-first and can send quick replies for short guided choices.
- The cleanest proof of success is one real LINE message that reaches Conversations and receives a reply.
Setup instructions
- Prepare the LINE channel access token and channel secret in LINE Developers Console.
- Open LINE activation on the agent page and fill both values.
- Copy the BldBot webhook URL into LINE Developers and enable webhook delivery.
- Send one real message from LINE and confirm that the dialog appears in Conversations and gets a reply.
What to verify after activation
- A real LINE inbound message appears under the correct agent.
- The reply goes back to the same LINE dialog, not only into internal logs.
- If handoff is enabled, the same conversation can move to an operator and later return to AI.
Typical issues
- The channel access token or channel secret is wrong.
- Webhook delivery is disabled or the public URL is unreachable from LINE.
- The team activated the fields but never tested a real inbound LINE message.
Ready to launch this channel?
Open the app, connect the channel, and test it with one real message before you scale it further.