A JOURNAL OF MESSAGING INFRASTRUCTURENO. 01 / 2026
Protocol Review

Buying guide

Keep an evaluation register.

A simple way to separate what is published, promised and observed.

Browse practical guides →
Every important requirement should have a source and a status.

Published

Record the exact plan, billing basis and source URL. A shared-number plan, dedicated line and self-hosted package should remain visibly distinct. Add the date because public terms change.

Confirmed

Ask the vendor to resolve ambiguous limits, missing features and inconsistent pages in writing. Keep that answer with the quote. A sales assurance is useful evidence of the proposed scope; it is not an independently observed result.

Observed

In a permitted evaluation, record the specific setup, input and outcome. Do not generalize one successful send into an uptime claim. A small test should answer a narrow question about the workflow you intend to buy.

Unresolved

Leave unknowns visible. An empty field should not quietly become a checkmark in a comparison table. If a requirement remains unconfirmed, keep it in the decision record until the team resolves it.

Source notes

  1. Plans and sandbox
  2. Integrations
  3. Contiguity pricing
  4. iMessage product