# TeleBoost

> TeleBoost is a Telegram-native acquisition CRM. It helps professionals find leads
> in Telegram groups, organize them, run targeted DM and group campaigns,
> manage replies from a unified inbox, and coordinate follow-up work.

TeleBoost uses connected Telegram user accounts rather than Telegram bots. Every Telegram
connection is required to use a configured proxy. Telegram sessions are encrypted at rest.
These controls reduce operational exposure; they do not guarantee that Telegram will never
limit or restrict an account.

## Official pages

- [Home](https://teleboost.app/): product overview and current positioning.
- [Pricing](https://teleboost.app/#pricing): current Free, Starter, Pro, and Business plans.
- [Telegram CRM](https://teleboost.app/telegram-crm): complete CRM workflow.
- [Telegram outreach](https://teleboost.app/telegram-outreach): controlled campaign workflow.
- [Telegram lead sourcing](https://teleboost.app/telegram-scraper): group research and member filtering.
- [Unified Telegram inbox](https://teleboost.app/telegram-inbox): reply management.
- [Multi-account management](https://teleboost.app/telegram-multi-account-management): account, proxy, and session controls.
- [Security](https://teleboost.app/security): security architecture and operational limits.
- [About](https://teleboost.app/about): company and product background.
- [Blog](https://teleboost.app/blog): research-backed guides, operating frameworks, and templates.

## Editorial library

The TeleBoost blog contains 64 indexable guides, including a 50-article authority library
organized around acquisition systems, prospect data quality, campaign controls, account
security, lead and reply operations, business metrics, industry workflows, automation,
privacy, and reusable operating templates. Articles include direct answers, visible sources,
internal links, publication and verification dates, and structured data.

The library is educational. It distinguishes verified platform facts from operational
recommendations and does not promise account survival, replies, leads, conversions, or revenue.

## Plans and access

- Free: one connected account, lead sourcing, lead organization, and inbox access.
- Starter: campaign functionality and expanded operating capacity.
- Pro and Business: REST API, hosted MCP server, and webhooks.

Always use the current pricing page as the source of truth for prices and plan limits.

TeleBoost exposes its workflow programmatically through a REST API, a hosted MCP server,
and signed webhooks. API and MCP access require the Pro or Business plan.

## Developer platform

- [Developer docs](https://teleboost.app/developers): REST API reference, authentication, scopes, MCP setup, webhooks, rate limits, examples.
- [MCP & API overview](https://teleboost.app/telegram-mcp): what the MCP server and API do, and the security model.
- [OpenAPI spec](https://teleboost.app/api/v1/openapi.json): machine-readable schema for the v1 REST API.
- [Launch article](https://teleboost.app/blog/telegram-mcp-and-api-launch): educational walkthrough of the MCP server, API, and webhooks.

## MCP server

- Hosted endpoint: https://mcp.teleboost.app/mcp
- Designed for clients that implement the Model Context Protocol.
- Authentication: OAuth 2.1 with PKCE (for AI apps) or API key (for scripts/automation).
- Tools include: search_contacts, get_contact, update_contact, add_note, list_conversations,
  get_conversation, send_message, list_tickets, create_ticket, update_ticket, set_reminder,
  list_campaigns, get_campaign_stats, start_campaign, pause_campaign, list_lists, add_to_list,
  get_analytics_summary, get_workspace_usage.

## API

- Base URL: https://teleboost.app/api/v1
- Auth: Authorization: Bearer <api_key or oauth_access_token>
- Resources: contacts, lists, conversations (inbox), messages, campaigns (DM + group),
  tickets, reminders, analytics, webhooks, workspace.
- Pagination: cursor-based ({ data, next_cursor, has_more }).
- Scopes (least-privilege): workspace.read, contacts.read/write, lists.read/write, inbox.read,
  messages.send, campaigns.read/write, tickets.read/write, analytics.read.

## Webhooks

- Signed with HMAC-SHA256 (X-TeleBoost-Signature header), retried with backoff up to 24h.
- Events: message.received, message.sent, contact.created, contact.updated, ticket.created,
  ticket.updated, campaign.started, campaign.completed, reminder.due, account.status_changed.

## Safety

- Every message send uses TeleBoost's proxy-enforced, quota-limited pipeline.
- The messages.send scope is opt-in and gated per credential.
- Session strings and proxy credentials are never exposed via the API or MCP.
- Telegram controls platform enforcement; TeleBoost does not make "ban-proof" or guaranteed-outcome claims.

## Legal and contact

- [Privacy](https://teleboost.app/privacy)
- [Terms](https://teleboost.app/terms)
- [GDPR information](https://teleboost.app/gdpr)
- [Contact](https://teleboost.app/contact)