Linq vs. Photon: compare the production path for a messaging agent
Evaluate the channel contract, shared and dedicated numbers, production pricing and the handoff from a prototype.
Read the comparison →PROTOCOL NOTES / VOL. 01
12 infrastructure reviews. The limits, number models and event questions between a working demo and a useful agent.
READ THE NOTES ↘THE LOOP TO EVALUATE
Verify the event.
Check authority.
Track the send.
Handle the retry.
Publisher disclosure: the team behind Miss Blue operates Agent Signal. Read the evidence policy.
An API plus a shared Message Center, evaluated as one human-and-agent workflow.
$99/line/month saleREAD NOTE ↗AS/02The inbound-first AI Agent plan and the sandbox’s missing webhook coverage.
$100/line/month inbound-first; outbound quotedREAD NOTE ↗AS/03Reading the commercial number types before selecting an agent plan.
$89/month commercial shared; $289 dedicatedREAD NOTE ↗AS/04A developer-facing platform spanning iMessage, RCS, SMS and voice.
Hobby $0; Pro starts at $260/month; Enterprise customREAD NOTE ↗AS/05The distinction between shared-number evaluation and Business deployment.
Free; Pro $25/month; Business $250/line/monthREAD NOTE ↗AS/06Why the base subscription is only one component of an agent’s sending plan.
Light from $59.99/month plus optionsREAD NOTE ↗AS/07A low-cost agent channel whose personal tiers are not open business lines.
Base $5/month; Agency $199/subtenant/monthREAD NOTE ↗AS/08A self-hosted route with a very different operating burden from a managed API.
Free base; optional Pro; your Mac and operating costsREAD NOTE ↗AS/09A managed agent API with a published dedicated-line plan.
$99/line/month; free sandboxREAD NOTE ↗AS/10Managed infrastructure with API events, multi-recipient threads and fallback.
Request a production quoteREAD NOTE ↗AS/11Evaluate Programmable Messaging when SMS, MMS or RCS fits the job, without assuming native iMessage support.
US long-code SMS $0.0083/segment plus other chargesREAD NOTE ↗AS/12An SMS/MMS API alternative with documented event IDs, delivery retries and failover behavior.
US local SMS from $0.004/part plus carrier feesREAD NOTE ↗Engineering notes on repeated events, changing channels, and the boundary between a model’s answer and an authorized action.
Evaluate the channel contract, shared and dedicated numbers, production pricing and the handoff from a prototype.
Read the comparison →A developer comparison of sandbox visibility, production pricing, sender continuity, channel events and integration work.
Read the comparison →Compare deterministic routing with language-based assistance, then assign each a narrow role in a business texting workflow.
Read the guide →A practical test plan for normal requests, ambiguity, duplicate events and human takeover, with expected outcomes defined before the assistant runs.
Read the guide →A worked design for ambiguous replies, current-record checks and human handoffs before an assistant changes a business appointment or order.
Read the guide →A familiar conversation can be a useful front door for a narrowly scoped business assistant.
Read the guide →A compact acceptance plan for a messaging agent.
Read the guide →Design a repeated-event path that does not make the customer receive the same answer twice.
Read the guide →Specify what changes when a conversation moves between iMessage, RCS and SMS.
Read the guide →A practical action boundary for models that can read a conversation and request a send.
Read the guide →