A JOURNAL OF MESSAGING INFRASTRUCTURENO. 01 / 2026
Protocol Review

Linq

Linq: evaluate the common interface carefully.

A multi-channel infrastructure proposition with public developer documentation.

Browse practical guides →
Channel breadth is useful only if the application can observe the differences.

Platform shape

Linq promotes native iMessage, RCS, SMS and voice, together with a developer API, CLI and sandbox. This makes it a relevant candidate for a product team building several communication paths rather than buying only a web inbox.

Selection follows iMessage → RCS → SMS; inspect the reported service. preferred_service is deprecated. RCS typing documentation differs by product area; the early-access number guide does not establish RCS Business Messaging entitlement.

Commercial evidence

November 10 update: Hobby is free for personal projects with 20 contacts; Pro starts at $260/month with a seven-day trial; Enterprise is custom. The separate $79 label’s attachment remains unclear. Supply expected lines, contacts, message activity and voice needs when requesting terms.

Technical evidence

Read the current event schemas for channel selection, delivery state and participant identity. Ask which rich-message capabilities survive a fallback and which require application behavior. Request the documents relevant to your security review directly from the vendor. The existence of a claim or badge is not an audit performed by Protocol Review.

Signed webhooks allow duplicates: ten-second timeout, about ten retries within 30 minutes. Retries retain event identity and content, including zero-day-retention messages; replays need resource-ID reconciliation. Error 4006 means uncertain delivery: reconcile before resubmitting.

Check Linq directly ↗

Source notes

  1. Linq platform
  2. Developer documentation
  3. Plans
  4. Protocols
  5. Webhooks
  6. RCS