Terms
Plain-language terms
How CallSnare is meant to be used and how messaging, billing, guarantee behavior, access, and integrations are grounded in stored records.
Updated April 16, 2026. Plain-language product summary that stays tied to the operating records and workflow rules the product uses.
Short version
CallSnare runs a missed-call workflow. Customers still own setup, messaging responsibility, and business decisions.
The terms connect product use, billing, guarantee records, and integration boundaries to the operating facts stored in the product.
Product use
CallSnare is for missed-call recovery and office handoff
- The service captures missed inbound calls, sends configured follow-up texts, keeps office context attached, supports booking workflows, and preserves proof around outcomes.
- Customers are responsible for reviewing setup, keeping business details accurate, and deciding when live coverage should be enabled.
- CallSnare is not a substitute for every phone-system, compliance, emergency-response, dispatch, or customer-service obligation a business may have.
Messaging
Text messaging terms
- Customer care text messages may be sent when a business's configured workflow, consent practices, and account rules allow it.
- Message frequency varies.
- Message and data rates may apply.
- Reply STOP to opt out.
- Reply HELP for help.
- Consent is not a condition of purchase.
- Customers are responsible for using CallSnare in line with their consent practices, local rules, carrier rules, provider rules, and customer expectations.
- Opt-out controls should not be bypassed, and CallSnare may suspend or limit messaging where opt-out, compliance, provider, or carrier rules require it.
Billing
Plan state, checkout, grace, and credits follow stored records
- Stripe is the billing system of record when live paid subscriptions are active.
- Plan selection can be carried from pricing into sign-up and billing, but the paid subscription is completed through the billing flow.
- If billing becomes inactive and grace expires, inbound records may still be ingested while outbound recovery is limited or disabled.
- Credits and exceptions should be tied to billing and guarantee records, not informal verbal promises.
Guarantee
The guarantee is narrow because it is tied to proof
- The first-window guarantee depends on eligibility, setup, routing, templates, tracked usage, and billing state.
- Guarantee outcomes are evaluated from stored call, lead, booking, and billing records.
- If an eligible credit applies, it is handled through the billing system tied to the organization.
Access and integrations
Protected actions require permissioned access
- Owners and approved team members are responsible for controlling workspace access.
- External integrations should use scoped credentials and documented protected APIs where available.
- Public docs explain the product model, but they do not create broad public write access.
Availability and changes
The product may change as long as stored trust remains intact
- CallSnare may improve workflows, settings, documentation, and provider integrations over time.
- Material changes should not blur customer data, internal tooling, billing state, or guarantee evidence.
- Customers should review current docs and settings when relying on a workflow for live operations.