Pricing & scope

Plan the scope.
Understand the cost.

Channel access, implementation, notifications, and human coverage are separate decisions. Use these planning tracks to describe a useful setup before discussing any commercial arrangement.

What this page offers

These are planning tracks, not purchasable subscription plans. No fixed InstaPager software pricing, provider allowance, or self-service checkout is published. Any implementation scope and commercial terms need to be established separately.

STARTER / SCOPING TRACK

One source. A focused brief.

For a solo operator or a small team defining its first message-review process.

  • One authorized source and a documented account owner
  • A short set of routine, urgent, and digest examples
  • One primary role with a realistic review window
  • Minimal notification previews and a manual fallback
  • A synthetic test set and a written acceptance check
Discuss a starter scope
TEAM / SCOPING TRACK

Several sources. Explicit ownership.

For workflows that need source-specific permissions and handoffs between multiple responders.

  • A channel-by-channel access and receiving review
  • Separate support, moderation, and business destinations
  • Primary and backup roles with agreed coverage
  • Repeat handling, handoff history, and failure review
  • A change owner and ongoing rule-maintenance plan
Discuss a team scope

What belongs in a realistic budget?

Begin with the actual receiving path. A business-number provider, an account-scoped API, a bot, and a manual review process have different requirements. Identify the approved account arrangement before assuming a channel can be included.

ComponentWhat to establish
Platform accessEligible account, application authorization, and the provider’s current arrangement.
ImplementationWho builds and maintains receiving, routing, credentials, and monitoring.
Usage & deliveryRelevant provider charges, notification destinations, expected activity, and retry behavior.
Human coverageWho reviews, accepts, replies, and provides any agreed backup.
Information handlingSource permissions, destination visibility, and the purpose of retained notes.

Prepare a useful scope request

Name the channels and accounts involved without including credentials. Describe the messages that need action, the team roles, the review windows, and the consequence of delay. Include approximate activity patterns when you know them, but distinguish estimates from measured volume.

Also describe the outcome you need. “A support owner accepts a current-booking problem” is a clearer requirement than “connect every inbox.” For channels with unavailable or unverified access, specify whether an authorized manual handoff would meet the need.

What is not included by assumption?

No source is treated as automatically connected, no continuous staffing is implied, and no delivery guarantee is made. Provider approval, a production implementation, and commercial terms are separate from these published planning resources.

Pricing questions

Are provider fees included?

No provider fees or allowances are sold here. They must be evaluated against the selected platform and account arrangement.

Can I buy a plan through this site?

There is no checkout or self-service account. Use the contact email to discuss a scope or ask about the published material.

Can a manual workflow be a valid starting point?

Yes. A clearly owned manual handoff may meet the need where automated access is unavailable or has not been verified.