OUR TAKE
Best fit: a product with several messaging channels
Linq’s value to an engineer is the documented platform surface rather than an impressive homepage metric. Investigate it when your application needs several forms of messaging and a coherent way to model the conversation. Pricing and contract scope must still be established directly.
A decision worksheet
| Offer | Advertised display | Resolve before purchase |
|---|---|---|
| Hobby | $0/month; 20 contacts | Which permitted project and environment? |
| Pro | From $260/month; location adds $79/month | What is the price unit and included usage? |
| Enterprise | Quoted | Which commitments appear in the signed order? |
Follow the documentation boundary
The November 8 documentation presents V3 iMessage with RCS/SMS and a separate WhatsApp surface. It does not substantiate the Apple business-channel branch described in our October review. This is a correction to that documentation description, not proof the vendor never offers another channel. Within the iMessage surface it describes iMessage, RCS and SMS, group chats, effects, receipts and webhooks. Those are different capabilities and entry rules. Select the documentation branch corresponding to the account and journey being purchased before borrowing examples.
A useful first document is a one-page purchase brief written before the demonstration. Put the product name at the top, then describe one complete customer journey: the invitation, the first reply, the staff handoff and the return visit. Beneath it, leave room for the sender identity, the channel, the organization that owns the account and the environment you can access. A proposal that names only “messaging” leaves too much room for two people to believe they agreed to different things.
Keep the commercial unit separate from the technical resource. A provisioned number in a console is not, by itself, the unit on an invoice or a promise that you can take that number elsewhere. Ask the supplier to mark which items are included, which vary with quantity and which require a new order. If the answer arrives in a sales email, retain that answer alongside the order rather than asking an engineer to reconstruct it from the dashboard months later.
- Messaging prices — November 8 ↗ · Checked
- Channel index — November 8 ↗ · Checked
Model the identifiers before the first send
Map your application action to the provider’s message and conversation identifiers. Decide how a reply is associated with a customer when the channel changes, and how attachments are retained. Channel breadth is valuable only if your system can preserve meaning across the events it receives. Inspect the current schemas rather than assuming every channel uses the same shape.
The captured V3 guide reports transport in the service field; the webhook guide gives a replay a new event identifier. Those are documented descriptions, not results from our own integration.
Draw three separate records on the design sheet: the action your application intended, the message the provider reports, and each event your system receives about it. Connect them with the documented identifiers rather than a match on message text. In a proposed recovery exercise, ask one engineer to explain an ordinary repeated delivery and another to explain a deliberately replayed historical event. They should be able to show why the same business action does not happen twice, even if the event records differ.
Then walk one conversation across a transport change without erasing the original request. Retain the requested destination and the observed channel, with a place for an unavailable receipt rather than a guessed success. Ask how the operator would distinguish “waiting for evidence” from “needs another send.” The useful output is a trace that a colleague can explain the next morning. It is not a green status chosen merely because the first HTTP exchange returned successfully.
- Access reference — November 8 ↗ · Checked
- Transport reference — November 8 ↗ · Checked
- Event reference — November 8 ↗ · Checked
Separate the proof you need
A sandbox establishes development access, not a contractual uptime commitment. Obtain current production price, sender identity, permitted direction and recovery terms. Test an ambiguous request outcome and a delayed incoming event before relying on automated follow-ups. We have not verified the vendor’s latency, security certification or capacity figures in this review.
The April 14 Partner API terms give the Order precedence and generally require 30 days’ written nonrenewal notice. The captured offer leaves included production usage, overages and port-out terms unresolved.
Close the review with two named owners. The purchasing owner should resolve the initial term, renewal instructions, tax treatment and what happens to the number at exit. The engineering owner should resolve account access, event authentication, restoration of missed history and who can authorize a recovery action. A feature can be attractive while one of these answers is still open. Mark that answer as pending and keep it out of the assumptions that allow the production release.
- Partner terms — April 14 edition ↗ · Checked
Questions before a decision
Is the Linq Pro price per number?
The captured public price does not settle that unit. Ask for a quote that states quantity, included usage and the charge for an additional resource. Do not multiply the display by a guessed number of lines or treat a missing overage figure as zero.
Is this a review of Linq digital business cards?
No. This page evaluates the messaging purchase and the evidence needed to operate it. Keep the product named on the order beside the documentation you use. A similarly branded subscription is not a substitute for the scope you are buying.
What would make the integration ready for a pilot?
A documented sender and channel scope, a trace linking actions to messages and events, and an agreed recovery owner. The exercises here are proposed acceptance work. Packet Ten has not run them against Linq or measured its delivery performance.
The decision in one sentence
Prototype a multi-channel event model with Linq if a scoped production offer and the documented channel boundary fit your architecture.
Read the primary sources
These are the provider’s own descriptions. Prices and product claims are dated snapshots, and performance claims are not our test results.
- Linq platform and channels ↗ · Checked
- Linq developer documentation ↗ · Checked
- Messaging prices — November 8 ↗ · Checked
- Partner terms — April 14 edition ↗ · Checked
- Channel index — November 8 ↗ · Checked
- Access reference — November 8 ↗ · Checked
- Transport reference — November 8 ↗ · Checked
- Event reference — November 8 ↗ · Checked