[a.s] AGENT SIGNAL

LoopMessage

LoopMessage review: pricing options and an outbound budget

Why the base subscription is only one component of an agent’s sending plan.

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 →
An agent that initiates needs more than a basic dedicated subscription.

3 minute read · Provider review

Add the required pieces

Dedicated Light starts at $59.99 per month. A phone number adds $15 monthly, the fallback option another $15, and initiating conversations another $30. That example totals $119.99 monthly before one-time option fees. It is an example configuration, not a quote for every application.

Read the contact definition

Light lists 300 unique active daily contacts. That figure is not an allowance to start 300 new outbound conversations. The provider’s outbound requirements include a dedicated sender, the initiation option, warm-up and recipient consent. Ask for the limits that apply to your intended launch.

Exercise a complete turn

In a pilot, send to a supported recipient, receive an answer and associate it with the correct agent session. Then inspect an unavailable channel and a deferred send. Keep the number, fallback and initiation selections in your deployment documentation so a later plan change does not silently remove a required capability.

Build the budget around a selected configuration

For a proposed appointment-reminder service, create a bill of materials before comparing providers. List every selected option, whether its charge recurs, any one-time cost and the unanswered tax or contract questions. Keep the resulting estimate tied to one configuration. A number copied from a different use case is not a budget for this one.

Give each option a reason in the service brief. If the reason is “we might need it later,” decide whether it belongs in the first launch. Record what should happen if the team removes or changes an option, and who checks the resulting behavior before that change takes effect. This is a proposed purchasing discipline, not a statement about how the provider handles upgrades.

Plan the first reminder and its exceptions

Use fictional bookings to describe a normal reminder, a changed appointment, a customer reply and a request for staff. Decide which current business record controls the outgoing text. If a booking changes after a reminder is queued, your acceptance case should show whether the old draft is cancelled, rebuilt or sent for review.

Keep a separate launch checklist for permission to contact the recipient, the selected sender and unresolved operating limits. Ask the supplier to confirm the conditions for your intended start. Avoid scheduling a large rollout around an assumption that an allowance for active people also defines how many new conversations you may initiate.

Our verdict and the handover record

We would choose a configuration only when the recurring estimate, launch conditions and recovery process are understandable together. A team willing to maintain that configuration record has a clearer basis for evaluation than a team shopping on the base subscription alone. Open questions should delay the relevant feature rather than disappear from the spreadsheet.

Before handover, name the person who owns a deferred message and the evidence they need to resolve it. Preserve the last known business state and the send attempt reference. A later reply must reach the current task owner even if the original automation has stopped; treat that as a requirement to test, not a capability assumed from the plan name.

Check LoopMessage directly ↗

Source notes

  1. Detailed pricing and options
  2. Channels and capabilities