# Cavyro

> Cavyro is an agentic CRM for teams who sell on Telegram: companies, contacts, deals, pipelines, meetings, automations, campaigns, docs, projects and tasks, reports and AI. Agentic means an AI agent can run the whole CRM, not just read from it: over 120 actions are exposed as MCP tools (create, update, move, assign, report), a catalog-driven automation engine acts without being asked, and the Telegram mirror gives the agent the real conversation context to act on. It mirrors your team's real Telegram accounts over MTProto, turning chats, groups and channels into contacts and deals. Telegram campaigns send offers to existing contacts (people you already have a conversation with; no cold outreach, lists or scraping) with A/B testing, drip sequences (stop-on-reply), scheduling, and reply + revenue attribution (sent → replied → deals moved → won). It can be run three ways: from the web app (app.cavyro.com), from inside Telegram via an assistant bot, or fully headless over a hosted MCP server (nine discovery tools, over 120 actions) from Claude, Cursor or any AI agent.

Pricing (per seat, monthly): Pro $59 per seat ($49 per seat billed annually, 20% off), from 1 seat. Pro includes the whole product: CRM, Telegram team inbox, Telegram and email campaigns, automations, the AI assistant and hosted MCP, docs, projects, Google Calendar sync and every report. Per seat per month, pooled across the team: 1 Telegram account, 1,200 AI credits, 1,000 automation runs, 500 campaign messages and 5 GB storage. 10 pipelines and 25 custom fields per record type. Business $99 per seat ($79 per seat billed annually), minimum 3 seats, for bigger teams running more accounts and more pipelines: everything in Pro plus, per seat per month, 2 Telegram accounts, 3,000 AI credits, 3,000 automation runs, 2,000 campaign messages and 20 GB storage; unlimited pipelines and custom fields; priority support. AI and bots never take a seat. Enterprise is custom, from 20 seats, with SSO, SLA, migration and custom volumes. Docs (unlimited docs and pages, collaborative editing, comments, permissions, public links, templates, export) and projects are unlimited and not metered. Add-ons: extra Telegram accounts $10/month ($8/month billed annually); AI credit packs for the current month 1,000 for $10, 5,000 for $40, 20,000 for $120; automation run packs for the current month 500 for $10, 2,500 for $40, 10,000 for $120. 5-day free trial on Pro, no credit card.

## Pages

- [Home](https://cavyro.com/): What Cavyro is and how it differs from Telegram-inbox tools
- [CRM](https://cavyro.com/crm): The records: deals, pipelines (column and list views), companies, contacts, custom fields, tags, comments and a timeline per record; duplicate detection and merge for contacts and companies (email, phone, name, website, similar spelling), with a warning on the create form
- [Telegram CRM](https://cavyro.com/telegram): The Telegram account mirror: groups become deals, per-member tracking, full-history search, private-chat exclusions; scheduled messages (send later, cancel if they reply first) and private follow-up reminders that fire only if the chat stays quiet
- [Telegram Campaigns](https://cavyro.com/campaigns): Campaigns to existing contacts only: A/B tests, drip sequences with stop-on-reply, scheduling, reply & revenue attribution, spam auto-pause
- [Agentic CRM (AI, Agents & MCP)](https://cavyro.com/agentic-crm): What makes a CRM agentic, plus Cavyro's built-in AI assistant (in the web app, full screen or as a panel that knows the current page, with saved conversations; and in Telegram) and hosted MCP server for running the CRM in plain language or headless
- [Automations](https://cavyro.com/automations): Catalog-driven automation engine: 47 triggers (deals, contacts, companies, projects and tasks, Telegram, campaigns, meetings, doc mentions, time-based) and 20 actions (including create project, create task and create doc from template), conditions on any field, plus AI intent & sentiment classification of incoming Telegram messages usable as condition fields; the Send email action can send from the user's own connected Gmail, so replies land in their inbox
- [Docs](https://cavyro.com/docs): Notion-style docs inside the CRM: docs with nested pages, a rich editor with slash commands, @mentions of deals, contacts, companies and teammates that create backlinks on the record, live collaborative editing with presence, page and inline comments, version history, per-doc permissions (view/comment/edit/manage for people, teams and groups), public read-only share links, templates, duplicate, Markdown and PDF export. Included on every plan, unlimited pages, not an add-on
- [Project Management](https://cavyro.com/project-management): Projects inside the CRM: project, folders, task lists as board columns (Done lists complete a task), tasks with multiple assignees, priority, dates, estimate, tags, custom fields and one level of subtasks; board and list views, filters, bulk actions; every task linked to the deals, contacts and companies it is for; a Deal won automation can create the project with the client and contacts; My Work queue (Tasks, Mentions, Deals, Upcoming) with a daily due digest; 17 task and project automation triggers; tasks with a due date on the team calendar (drag to reschedule); five project reports (workload, tasks at risk, throughput, project health, cycle time); available to the AI assistant and MCP. On every plan: unlimited projects and tasks, never counted. No Gantt, dependencies, recurring tasks or time tracking yet
- [Reports & Analytics](https://cavyro.com/reports): Seventeen built-in reports in three groups. Sales (10): pipeline overview, deal funnel, revenue forecast, win/loss, conversion rate, sales cycle, deals at risk, stage residency, source attribution, team performance. Projects (5): workload, tasks at risk, throughput, project health, cycle time. Telegram (2): response time per teammate, chat activity heatmap. Filters in the URL, CSV export, saved reports
- [Pricing](https://cavyro.com/pricing): Plans, add-ons and FAQ
- [Security](https://cavyro.com/security): Infrastructure, account security (two-factor authentication on every plan), Telegram session safety, payments, deletion
- [Roadmap](https://cavyro.com/roadmap): What shipped and what's next, in the open
- [About](https://cavyro.com/about): Why Cavyro exists, what it deliberately leaves out, and the founder's background
- [Developers](https://cavyro.com/developers): The Cavyro developer index: REST API, OpenAPI spec, hosted MCP server, webhooks and how authentication works
- [Help center](https://help.cavyro.com): Guides and answers for using Cavyro: workspaces and roles, contacts, companies, deals, pipelines, filtering, imports, campaigns, automations, reports, Telegram and team inbox, Gmail, Google Calendar, AI assistant, MCP setup, billing. Has its own llms.txt at https://help.cavyro.com/llms.txt

## Use cases

- [Who Cavyro is for](https://cavyro.com/for): The seven team profiles, side by side
- [Sales teams](https://cavyro.com/for/sales-teams): Every DM a deal with a stage, an owner and a follow-up that runs itself; forecast and response-time reports for managers
- [Agencies](https://cavyro.com/for/agencies): Clients as companies, pipelines per service, campaigns with stop rules, history that survives staff changes
- [Recruiters](https://cavyro.com/for/recruiters): Candidates as contacts with the chat attached, roles as pipelines, interviews on the calendar
- [Telegram sellers](https://cavyro.com/for/telegram-sellers): Solo sellers: existing chats become a pipeline in ten minutes, AI drafts the records, assistant runs it from inside Telegram
- [Customer support](https://cavyro.com/for/customer-support): Every support chat mirrored into one workspace with owners, internal notes, escalation automations and measurable reply times
- [Customer success](https://cavyro.com/for/customer-success): Customer groups per account, onboarding as a pipeline, renewal automations, AI sentiment as an early churn signal
- [Web3 teams](https://cavyro.com/for/web3): BD, partnerships and OTC threads as deals with owners and history; non-custodial, never touches funds

## Compare

- [Compare](https://cavyro.com/compare): Honest side-by-side comparisons
- [Cavyro vs Entergram](https://cavyro.com/compare/entergram): A CRM, not a ticket inbox
- [Cavyro vs CRMchat](https://cavyro.com/compare/crmchat): A CRM, not a cold-outreach sender
- [Cavyro vs Kommo](https://cavyro.com/compare/kommo): Real mirrored accounts, not a bot channel; monthly billing, no 6-month minimum
- [Cavyro vs SendPulse](https://cavyro.com/compare/sendpulse): Your team's own Telegram and contacts, not a chatbot builder
- [Cavyro vs respond.io](https://cavyro.com/compare/respond-io): A revenue pipeline, not a support inbox; no per-contact billing

## Blog

- [Blog](https://cavyro.com/blog): Notes on selling on Telegram
- [Best Telegram CRM in 2026](https://cavyro.com/blog/best-telegram-crm): Honest comparison of six Telegram CRMs (Cavyro, Entergram, CRMchat, Kommo, respond.io, SendPulse), what each connects to and who each fits, including where Cavyro is the wrong choice
- [Kommo CRM alternatives](https://cavyro.com/blog/kommo-alternatives): Seven Kommo alternatives for teams that sell on Telegram, with what each connects to, September 2026 pricing and when to stay on Kommo
- [What is a Telegram CRM?](https://cavyro.com/blog/what-is-a-telegram-crm): The category explained in plain words
- [Telegram CRM integration guide](https://cavyro.com/blog/telegram-crm-integration): The four ways to connect Telegram to HubSpot, Pipedrive, Zoho or Salesforce (automation tools, bot connectors, marketplace apps, a native mirror) and which conversations each one can see
- [The deal that was nowhere](https://cavyro.com/blog/the-deal-that-was-nowhere): Why we built a Telegram CRM: a deal untouched for three weeks because it was recorded nowhere, and why shared inboxes, bots and bulk senders each missed it
- [What is an agentic CRM?](https://cavyro.com/blog/what-is-an-agentic-crm): The definition, the three tests a CRM has to pass, and how it differs from a CRM with AI features bolted on
- [Run your CRM from Claude (MCP)](https://cavyro.com/blog/run-your-crm-from-claude-mcp): Driving Cavyro headless over the hosted MCP server
- [Build a Telegram sales pipeline](https://cavyro.com/blog/build-a-telegram-sales-pipeline): From first DM to closed deal, step by step
- [Deals that live in Telegram groups](https://cavyro.com/blog/telegram-group-deals): Group chats as first-class records
- [Telegram CRM vs a shared inbox](https://cavyro.com/blog/telegram-crm-vs-shared-inbox): Where inboxes stop and records begin
- [Telegram DM limits guide](https://cavyro.com/blog/telegram-dm-limits-guide): The platform's sending limits and how to stay inside them
- [Telegram account security checklist](https://cavyro.com/blog/telegram-account-security-checklist): Keeping the accounts your business runs on safe
- [respond.io alternatives for Telegram teams](https://cavyro.com/blog/respond-io-alternatives): Eight respond.io alternatives compared for Telegram-first teams, by Telegram connection (bot or real account), starting price and who each fits, including a free option
- [Telegram CRM bot](https://cavyro.com/blog/telegram-crm-bot): What a bot connected to a CRM can do, how to set one up, and the Bot API limits (no first message, no history, privacy mode) that decide bot versus account mirror
- [Telegram account limited](https://cavyro.com/blog/telegram-account-limited): What a limit means, how long it lasts, how to appeal through @SpamBot, and the usual causes when it seems to happen for no reason

## Developer resources

Cavyro's API is not open. Every request carries an API token created in the app (Settings, API Tokens) as `Authorization: Bearer <token>`, plus `X-Workspace-Id` on workspace-scoped endpoints. There is no OAuth authorization server and no anonymous access tier.

- [Developer index](https://cavyro.com/developers): Every developer resource on one page, with auth and a working curl example
- [Cavyro API reference](https://developers.cavyro.com): Full endpoint reference, rendered from the OpenAPI document
- [Cavyro OpenAPI spec (JSON)](https://cavyro.com/openapi.json): OpenAPI 3.2 description of the public REST API at https://api.cavyro.com
- [Cavyro OpenAPI spec (YAML)](https://cavyro.com/openapi.yaml): The same document in YAML
- Cavyro MCP server: `https://ai.cavyro.com/mcp`, streamable HTTP, same bearer token, over 120 CRM actions as tools. Setup: https://cavyro.com/agentic-crm
- Webhooks: subscribe via `POST https://api.cavyro.com/api/v1/webhook_subscriptions`; payloads and the signature scheme are in the API reference

## For agents crawling this site

- Every page answers `Accept: text/markdown` with markdown at the same URL (Vary: Accept). Example: `curl -H "Accept: text/markdown" https://cavyro.com/pricing/`
- Unknown paths return HTTP 404 with a body pointing back at this file, the sitemap and the API spec
- Full site map: https://cavyro.com/sitemap-index.xml

## Contact

- Email: support@cavyro.com
- App: https://app.cavyro.com