Question 1

What events can send a message to Line?

Accepted Answer

Delivery exceptions and delays, shipments stuck in transit, rate changes and contract expirations, invoice discrepancies found during audit, orders that failed to route, and scheduled reports. Build the trigger, condition, and action in the rule builder, then route each rule to the Line channel or person who should see it.

Question 2

Can my team act on a shipment from inside Line?

Accepted Answer

Yes. Messages carry the actions that matter for that event, so a delayed shipment can be escalated, a customer notification sent, or an exception cleared without opening another tab. Inbound messages also create shipments and update orders for teams that work primarily in Line.

Question 3

How do approvals work through Line?

Accepted Answer

Route any decision that needs a human to the person who owns it. Rate changes above a threshold, exception handling, and cost overrides arrive in Line with the context needed to decide. The approval writes back to CommerceShip and the activity log records who approved what and when.

Question 4

What do the AI agents send to Line?

Accepted Answer

Agents monitor shipments and costs continuously and raise what needs attention: an exception pattern forming, a cost spike against the same lane, an invoice line that does not match the contract. Agents also draft customer responses and status updates, which arrive in Line for a person to review and send.

Question 5

What triggers a message through Line?

Accepted Answer

The carrier event itself. Label creation, first scan, out for delivery, delivered, and any exception are available as triggers, so timing follows the shipment.

Question 6

Can I message only the customers affected by a delay?

Accepted Answer

Yes. Filter by carrier, lane, service, or delivery date and send to that set through Line. Weather impact analytics identifies which shipments a storm is affecting, which is usually the list you want to message.

Question 7

What access does CommerceShip need to Line?

Accepted Answer

The connection uses scoped credentials limited to the record types the integration works with, and you choose which fields are included. Credentials are encrypted at rest and stored separately from your operational data. Revoke the connection from either side at any time and the access ends with it.

Question 8

How is my data protected?

Accepted Answer

TLS in transit and AES-256 at rest, with tenant isolation enforced by row-level security in the database. Role-based permissions control who on your team can see cost data or change carrier settings, and automated actions are written to an audit log. CommerceShip is pursuing SOC 2 Type II certification. The security page carries the full detail.

Event	Order #	Recipient	Channel
Label Created	#1052	+1 (512) ••• 4471	Line
Out for Delivery	#1049	+1 (303) ••• 8820	Line
Delayed	#1047	+1 (415) ••• 2210	Line

Event	Order #	Recipient	Channel
Label Created	#1052	+1 (512) ••• 4471	Line
Out for Delivery	#1049	+1 (303) ••• 8820	Line
Delayed	#1047	+1 (415) ••• 2210	Line

Send delivery notifications through Line

Line Integration Capabilities

How the Line integration works

Connect Line

Choose events and templates

Send on the carrier event

Line Integration FAQs

Send delivery updates through Line

Other Communication Tools