Documentation that helps operators, integrators, and models find the right entry point fast

Use these pages to understand how CallSnare handles missed calls, leads, bookings, permissions, and protected external access without scraping the dashboard UI.

Start with overview Open llms.txt

Technical enough for partners and models, clear enough for owners who want to understand the workflow before they sign up.

Docs navigator

Product model

Overview and workflows for buyers and operators.

Access boundaries

Permissions, security, and protected integration rules.

Model entry points

llms files and agent-access guidance for approved systems.

Docs map

Choose the category that matches the question in front of you

These docs are organized around the real operating surface: workflow logic, permissions, protected access, and the machine-readable discovery layer.

Overview

What CallSnare does, who it is for, and the main missed-call-to-booking flow.

Open page

Workflows

Public explanation of missed call, text-back, booking, reminder, and handoff behavior.

Open page

Actions

Canonical action vocabulary, current protected endpoints, and planned external actions.

Open page

Permissions

Roles, scopes, trust boundaries, and audit expectations for CallSnare access.

Open page

Agent Access

Public status page for machine-readable docs and protected integration access.

Open page

Security

Authentication, authorization, rate limiting, webhook validation, and audit posture.

Open page

Webhooks

Inbound provider callbacks and the current status of public outbound event delivery.

Open page

Use the docs this way

Three audiences, one documentation surface

The goal is navigability first: show people where to begin, which docs are public, and which files exist for models.

Owners and operators

Understand the product model, workflow boundaries, and what stays in team control.

Approved partners

See where protected integrations fit, what access is available, and which boundaries are intentional.

Models and crawlers

Use the public docs plus machine-readable discovery files instead of scraping the dashboard UI.

Machine-readable discovery

/llms.txt

Short model-readable summary for CallSnare.

/llms-full.txt

Expanded model-readable briefing for CallSnare.

Next step

Start with the doc that answers the immediate question

If you want the product model first, start with the overview doc. If you need integration boundaries, jump into permissions, actions, or agent access.

Markdown mirror