[a.s] AGENT SIGNAL

Photon

Photon review: pricing, deployment choices and the Linq comparison

The distinction between shared-number evaluation and Business deployment.

Updated November 7, 2026: linked primary sources rechecked and practical evaluation guidance added. The original publication date remains above. This is a public-source assessment, not a hands-on test.

Browse practical guides →
Model users, numbers and new contacts separately when moving out of the prototype.

3 minute read · Provider review

A clear starting point

Photon offers a free tier for up to ten users and Pro at $25 per month for up to 100 users. Those plans use managed shared numbers. They can be a useful way to explore an agent experience before paying for dedicated identity.

The production step

Business is listed at $250 per line per month with dedicated numbers, a group messaging API and a daily allowance of 50 new contacts. Unlimited-user wording depends on Auto Scale. A developer should request the precise scaling and billing behavior rather than extrapolate the Pro price to a large customer base.

One more architectural choice

Photon also describes Spectrum for multi-channel agents and an open-source self-hosted path. Treat the cloud plan and a Mac-based installation as separate operating models. In an evaluation, inspect participant identity in group threads and how a conversation moves between channels. The public pages do not establish our own availability or security benchmark.

What a prototype should prove

For a fictional concierge assistant, define the smallest useful exchange: a participant asks for an available time, corrects a detail and requests a human. Write down which application record should change at each step. Keep a list of conditions the prototype does not cover so they remain visible when the team considers a launch.

Treat a move between configurations as a new acceptance decision. Ask what happens to existing participants, sender identity, stored conversation references and pending work. Obtain an answer for the intended transition and rehearse it only in an authorized setting. Nothing in this review promises that a number or message history transfers automatically.

Questions to settle before estimating scale

Make a workload table with distinct people, active conversations, newly reached contacts and sending identities in separate columns. Add a row for the busiest planned day. Ask the supplier which quantity drives each allowance and charge in your selected configuration; leave unknown answers unpriced until clarified.

For our proposed evaluation, a burst of inquiries should produce an explainable queue and a responsible operator, not a stream of improvised retries. Define what waits, what can be cancelled and what a customer sees while a request is unresolved. Those controls belong in the application plan even when the first demonstration feels immediate.

Photon versus Linq: use a common brief

If comparing these two providers, begin with the same business task and required channels. Ask each to document the sender arrangement, billable units, event contract and recovery owner for that task. Do not rank two headline prices before establishing that they purchase equivalent configurations.

Our recommendation is to choose only after the proposed launch has an evidence record distinct from the prototype. Keep provider terms, your own observations and open questions in separate columns. The companion comparison supplies a shared checklist; neither page establishes a latency winner, an independent security audit or an improved model-accuracy result.

Check Photon directly ↗

Source notes

  1. Photon pricing and number types
  2. Photon platform