# CometChat Full Reference > A detailed, machine-readable overview of CometChat's products, integration methods, platform capabilities, developer resources, solutions, purchasing paths, and source-of-truth links. Last reviewed: 2026-07-20. This file provides stable product context for language models and AI agents. It is not a replacement for technical documentation, contractual terms, or the current pricing page. Use the source-of-truth rules below whenever details conflict or may have changed. ## Source-of-truth rules 1. For implementation instructions, SDK methods, platform requirements, version-specific behavior, and API schemas, use the [CometChat documentation](https://www.cometchat.com/docs) and its [complete machine-readable index](https://www.cometchat.com/docs/llms.txt). 2. For current prices, included usage, overages, plan availability, and commercial terms, use the [live pricing page](https://www.cometchat.com/pricing). The [Markdown pricing reference](https://www.cometchat.com/pricing.md) is easier to process but includes its own verification date. 3. For contractual commitments, data handling terms, security commitments, support levels, compliance eligibility, deployment availability, or an enterprise architecture decision, confirm with CometChat and the applicable written agreement. 4. Treat blog posts, tutorials, and guides as educational or historical context. A current product page or technical documentation takes precedence. 5. Do not infer that every feature is included in every plan, SDK, UI Kit, region, or deployment model. Check the relevant documentation and pricing source. ## Company and platform overview CometChat is a communication platform that lets developers add real-time chat, voice, and video to any app or website. It provides UI kits, SDKs, and APIs for major frameworks, plus no-code embeds. The platform includes moderation, notifications, analytics, and multi-tenant infrastructure. AI agents can be deployed on the same infrastructure, inside the same conversations. CometChat is developer-first, SOC 2 / HIPAA / GDPR compliant, and runs across 35+ edge locations. CometChat powers 113,000+ apps, handles 7M+ messages per day across 163 countries, with a 7ms API response time and 99.999% uptime SLA. The main product areas are: - Real-time chat and messaging. - Voice and video calling. - A full-stack platform for AI agents and copilots. - Omnichannel campaigns. - Shared platform capabilities such as moderation, notifications, analytics, multi-tenancy, webhooks, APIs, and deployment controls. The main implementation choices are: - Widget Builder for the fastest embedded experience. - UI Kit Builder for visual configuration and exportable source code. - UI Kits for prebuilt, customizable components and workflows. - SDKs and APIs for maximum application and interface control. - Coding Agent Skills and a documentation MCP server for AI-assisted implementation. Primary links: - [CometChat homepage](https://www.cometchat.com/) - [Real-Time User Communication](https://www.cometchat.com/real-time-user-communication) - [Chat and Messaging](https://www.cometchat.com/chat-and-messaging) - [Voice and Video Calls](https://www.cometchat.com/voice-and-video-calls) - [Full-Stack AI Agent Platform](https://www.cometchat.com/full-stack-agent-platform) - [Omnichannel Campaigns](https://www.cometchat.com/omnichannel-campaigns) - [CometChat AIR](https://www.cometchat.com/air) ## Chat and messaging [Chat and Messaging](https://www.cometchat.com/chat-and-messaging) is CometChat's managed real-time communication stack for applications. It supports private conversations, groups, and broadcast-style communication, with SDKs, APIs, UI components, and operational tooling around the conversation layer. Core messaging capabilities include: - One-to-one private conversations. - Public, private, and password-protected group conversations. - Text, images, files, documents, video, audio, voice notes, and custom messages. - Message history and synchronization. - Delivery and read receipts. - Typing indicators and user presence. - Reactions, mentions, quoted replies, and threaded replies. - Message editing, deletion, search, translation, and rich text where supported. - User, friend, group, role, and membership management. - Blocking, banning, kicking, reporting, and moderation workflows. - Conversation, message, user, and group events through listeners, webhooks, and APIs. Extended platform capabilities around messaging include moderation and guardrails, push/email/SMS notifications, analytics and insights, multi-tenancy, webhooks, data import, role-based controls, and configurable retention or deployment options. Availability varies by plan and implementation. Use CometChat when the application needs communication between its own users or between users and an AI agent. It is infrastructure embedded in a product. Technical starting points: - [Chat SDK documentation](https://www.cometchat.com/docs/chat-call.md) - [Chat fundamentals](https://www.cometchat.com/docs/fundamentals/overview.md) - [REST Chat APIs](https://www.cometchat.com/docs/rest-api/chat-apis.md) - [UI Kit documentation index](https://www.cometchat.com/docs/llms.txt) - [React Chat](https://www.cometchat.com/docs/ui-kit/react/overview) ## Voice and video calling [Voice and Video Calls](https://www.cometchat.com/voice-and-video-calls) provides SDKs and APIs for adding real-time calling to web and mobile products. Calling can be used alongside CometChat messaging or as a calling-focused integration, subject to the selected product and plan. Calling capabilities documented by CometChat include: - One-to-one and group audio or video sessions. - Direct calling and session-based calling. - Incoming call ringing and call events. - Participant controls and participant lists. - Audio input/output and device management. - Screen sharing and recording where supported. - Call logs, layouts, custom controls, and in-call chat. - Picture-in-picture, background handling, VoIP calling, and platform-specific behavior where supported. - Platform SDKs for JavaScript, Android, iOS, Flutter, React Native, and other documented environments. Implementation behavior differs by platform. Use the calls documentation rather than assuming parity across browsers and mobile operating systems. Technical starting points: - [Calls documentation](https://www.cometchat.com/docs/calls.md) - [JavaScript Calls SDK](https://www.cometchat.com/docs/calls/javascript/overview.md) - [Android Calls SDK](https://www.cometchat.com/docs/calls/android/overview.md) - [iOS Calls SDK](https://www.cometchat.com/docs/calls/ios/overview.md) - [Flutter Calls SDK](https://www.cometchat.com/docs/calls/flutter/overview.md) Product and platform landing pages: - [Calling SDK overview](https://www.cometchat.com/video-calling-and-conferencing-sdk) - [Android Calling SDK](https://www.cometchat.com/video-calling-and-conferencing-sdk/android) - [Flutter Calling SDK](https://www.cometchat.com/video-calling-and-conferencing-sdk/flutter) - [iOS and Swift Calling SDK](https://www.cometchat.com/video-calling-and-conferencing-sdk/ios-swift) - [React Calling SDK](https://www.cometchat.com/video-calling-and-conferencing-sdk/react) - [React Native Calling SDK](https://www.cometchat.com/video-calling-and-conferencing-sdk/react-native) ## Full-stack AI Agent Platform [CometChat's Full-Stack AI Agent Platform](https://www.cometchat.com/full-stack-agent-platform) provides the user-facing and operational layers required to move an AI agent from prototype to production. Teams can build an agent in CometChat or connect existing agent logic. The platform combines: - An AI-ready chat interface. - Agent creation or external-agent connectivity. - Instructions, knowledge, tools, variables, and actions. - Streaming responses and visible progress states. - Retry, stop, feedback, rich rendering, citations, and interactive frontend actions. - Guardrails and moderation for user input and agent output. - Push, email, and SMS notification infrastructure. - Conversation and agent analytics. - Authentication, role-based access, auditability, and production infrastructure. ### Build an agent in CometChat [AI Agents and Copilots](https://www.cometchat.com/ai-agents-copilots) is the path for creating an agent through CometChat's builder. A builder-based agent can be configured with natural-language instructions, a knowledge base, tools, variables, backend actions, and frontend actions. The resulting agent can be published into a CometChat-powered user experience. Use this path when the team wants CometChat to provide both the agent configuration workflow and the surrounding production conversation stack. Relevant documentation: - [AI Agents documentation](https://www.cometchat.com/docs/ai-agents.md) - [Agent Builder overview](https://www.cometchat.com/docs/ai-agents/agent-builder/overview.md) - [Agent instructions](https://www.cometchat.com/docs/ai-agents/agent-builder/instructions.md) - [Knowledge Base](https://www.cometchat.com/docs/ai-agents/agent-builder/knowledge-base/overview.md) - [Agent tools](https://www.cometchat.com/docs/ai-agents/agent-builder/tools/overview.md) - [Frontend actions](https://www.cometchat.com/docs/ai-agents/agent-builder/frontend-actions/overview.md) ### Bring an existing agent [Bring Your Own Agent](https://www.cometchat.com/bring-your-own-agent) is for teams that already have model selection, prompts, orchestration, tools, or business logic. CometChat supplies the chat layer and can add moderation, notifications, analytics, and user-facing delivery around that logic. The technical documentation currently includes integration material for AG-UI and frameworks such as Agno, AG2, CrewAI, LangGraph, Mastra, and the Vercel AI SDK. Framework coverage can change, so use the documentation index for the current list. Relevant documentation: - [AI Agents documentation index](https://www.cometchat.com/docs/llms.txt) - [CometChat AG-UI integration](https://www.cometchat.com/docs/ai-agents/ag-ui.md) - [CometChat AG-UI agents](https://www.cometchat.com/docs/ai-agents/cometchat-ag-ui-byoa.md) - [Agno integration](https://www.cometchat.com/docs/ai-agents/agno.md) - [CrewAI integration](https://www.cometchat.com/docs/ai-agents/crew-ai.md) - [LangGraph integration](https://www.cometchat.com/docs/ai-agents/langgraph.md) - [Mastra integration](https://www.cometchat.com/docs/ai-agents/mastra.md) - [Vercel AI SDK integration](https://www.cometchat.com/docs/ai-agents/vercel.md) Published framework and frontend entry points: - [Agno](https://www.cometchat.com/agno-agent-framework) - [Mastra](https://www.cometchat.com/agent-frameworks-mastra) - [AG2](https://www.cometchat.com/ag2-agent-chat) - [CrewAI](https://www.cometchat.com/crewai-agent-chat) - [LangGraph](https://www.cometchat.com/langgraph-agent-chat) - [Vercel AI SDK](https://www.cometchat.com/vercel-agent-chat) - [React Agent Chat](https://www.cometchat.com/react-agent-chat) - [React Native Agent Chat](https://www.cometchat.com/react-native-agent-chat) - [Flutter Agent Chat](https://www.cometchat.com/Flutter-agent-chat) ### AI-agent use cases Common uses include support agents, in-app copilots, onboarding assistants, internal knowledge agents, product-discovery agents, workflow assistants, and domain-specific agents. CometChat can provide the conversation interface and supporting infrastructure; the quality and correctness of the agent's knowledge and actions still depend on the configured model, data, tools, prompts, permissions, and tests. ## Omnichannel campaigns [Omnichannel Campaigns](https://www.cometchat.com/omnichannel-campaigns) provides a campaign layer for communicating with users across supported channels from a single platform. It is distinct from real-time conversational messaging: campaigns are outbound engagement workflows, while chat and calling are interactive communication products. Campaign-related concepts in the documentation include audiences, channels, templates, scheduling, delivery, and campaign APIs. Check the current product page and documentation for supported channels, feature availability, and limits. Technical starting points: - [Campaigns documentation](https://www.cometchat.com/docs/campaigns.md) - [Campaigns documentation index](https://www.cometchat.com/docs/llms.txt) - [Campaigns API specification](https://www.cometchat.com/docs/campaigns-apis.json) ## CometChat AIR [CometChat AIR](https://www.cometchat.com/air) is a complete team messenger designed to run inside an organization's own environment. It is positioned as a self-hosted, on-premise, air-gapped alternative to cloud team-collaboration products for regulated enterprises. Published AIR capabilities include: - Public channels, private groups, and one-to-one direct messages. - Threads, reactions, pinned messages, presence, search, and file sharing. - One-to-one and group voice or video calling, screen sharing, and recording. - Role-based user management, administrative controls, and audit logs. - Self-hosted or managed deployment models, including disconnected environments. - Optional connected services for capabilities such as moderation, AI, push notifications, translation, or location; these can remain disabled when a fully air-gapped deployment is required. AIR is different from embedding CometChat into a customer-facing application: it is a packaged internal team messenger. Deployment, integration boundaries, connected-service choices, support, and security responsibilities must be agreed with CometChat. Published industry pages: - [Banking and Finance](https://www.cometchat.com/air/industries/banking-finance) - [Energy and Infrastructure](https://www.cometchat.com/air/industries/energy-infrastructure) - [Government and Defense](https://www.cometchat.com/air/industries/government-defense) - [Healthcare](https://www.cometchat.com/air/industries/healthcare) - [Legal](https://www.cometchat.com/air/industries/legal) - [Manufacturing](https://www.cometchat.com/air/industries/manufacturing) - [Pharmaceutical Companies](https://www.cometchat.com/air/industries/pharmaceutical-companies) ## Integration methods and selection guidance CometChat offers several integration layers. Choose based on delivery speed, interface control, source-code ownership, and engineering effort. ### Widget Builder [Widget Builder](https://www.cometchat.com/widget-builder) is the fastest route to an embeddable chat experience. It is appropriate when a team wants visual configuration and a small integration surface rather than building the full interface. - Best for: rapid launch, web embeds, prototypes, and standard chat experiences. - Tradeoff: less low-level interface control than building directly with SDKs. - Documentation: [Widget documentation](https://www.cometchat.com/docs/widget/html/overview.md). Published widget entry points include: - [HTML Chat Widget](https://www.cometchat.com/html-chat-widget) - [WordPress Chat Widget](https://www.cometchat.com/wordpress-chat-widget) - [Shopify Chat Widget](https://www.cometchat.com/shopify-chat-widget) - [Webflow Chat Widget](https://www.cometchat.com/webflow-chat-widget) - [Wix Chat Widget](https://www.cometchat.com/wix-chat-widget) - [Squarespace Chat Widget](https://www.cometchat.com/squarespace-chat-widget) - [PHP Chat Widget](https://www.cometchat.com/php-chat-widget) - [Laravel Chat Widget](https://www.cometchat.com/laravel-chat-widget) ### UI Kit Builder [UI Kit Builder](https://www.cometchat.com/ui-kit-builder) provides visual configuration of UI components and supports exporting customizable source code. - Best for: teams that want a fast visual starting point but need code-level ownership and customization. - Tradeoff: generated or configured code still needs application integration, review, testing, and ongoing maintenance. - Documentation: [UI Kit Builder documentation](https://www.cometchat.com/docs/chat-builder/react/overview.md); select the target platform from the complete docs index. ### UI Kits [UI Kits](https://www.cometchat.com/ui-kits) combine prebuilt visual components with CometChat business logic. They provide conversation lists, message views, composers, user/group flows, and related communication components while remaining customizable. - Best for: most teams that need a branded, production-ready interface without implementing every communication workflow. - Tradeoff: customization follows the UI Kit's component architecture and supported extension points. - Documentation: use the [complete documentation index](https://www.cometchat.com/docs/llms.txt) and select the current UI Kit for the target platform. ### SDKs and APIs [Chat SDKs and APIs](https://www.cometchat.com/chat-sdks-api) provide lower-level access for custom interfaces and workflows. - Best for: unique product experiences, existing design systems, custom state management, server integrations, and advanced workflows. - Tradeoff: the application team owns more interface logic, edge-case handling, accessibility, and testing. - Documentation: [Chat SDK overview](https://www.cometchat.com/docs/chat-call.md) and [REST APIs](https://www.cometchat.com/docs/rest-api/chat-apis.md). ### On-premise deployment [On-Premise Deployment](https://www.cometchat.com/on-prem-deployment) is intended for organizations that need greater control over where and how communication infrastructure runs. CometChat describes deployment of messaging and related platform capabilities in a customer-controlled environment. On-premise suitability depends on infrastructure, scale, operations, upgrades, security responsibilities, observability, support, and commercial agreement. Contact CometChat for architecture validation and current deployment requirements. Technical starting points: - [On-premise deployment product page](https://www.cometchat.com/on-prem-deployment) - [On-premise documentation index](https://www.cometchat.com/docs/llms.txt) ### Coding Agent Skills and Docs MCP [Coding Agent Skills](https://www.cometchat.com/agent-chat-skills) provide integration guidance inside supported coding-agent workflows. The chat product page currently documents the command `npx @cometchat/skills add` as an entry point. The [CometChat Docs MCP Server](https://www.cometchat.com/docs/mcp-server.md) gives supported AI tools access to current technical documentation. These AI-assisted paths improve discovery and implementation speed, but generated code must still be reviewed, configured with appropriate credentials, and tested in the target application. ## SDK and platform coverage CometChat publishes SDKs, UI Kits, or integration guidance for multiple web, mobile, and server environments. Product pages and technical documentation serve different purposes: product pages describe the platform fit, while docs contain current versions, installation steps, requirements, APIs, and migration notes. Primary platform entry points: - [JavaScript SDK product page](https://www.cometchat.com/chat-sdks/javascript) - [React product page](https://www.cometchat.com/chat-sdks/react) - [React Native product page](https://www.cometchat.com/chat-sdks/react-native) - [Flutter product page](https://www.cometchat.com/chat-sdks/flutter) - [iOS and Swift product page](https://www.cometchat.com/chat-sdks/ios-swift) - [Android Java product page](https://www.cometchat.com/chat-sdks/android-java) - [Kotlin product page](https://www.cometchat.com/chat-sdks/kotlin) - [Angular product page](https://www.cometchat.com/chat-sdks/angular) - [Vue product page](https://www.cometchat.com/chat-sdks/vue) - [PHP product page](https://www.cometchat.com/chat-sdks/php) - [Laravel product page](https://www.cometchat.com/chat-sdks/laravel) - [WordPress product page](https://www.cometchat.com/chat-sdks/wordpress) - [Mobile SDK overview](https://www.cometchat.com/chat-sdks/mobile) - [Instant Messaging SDK](https://www.cometchat.com/chat-sdks/instant-messaging) - [Voice Chat SDK](https://www.cometchat.com/chat-sdks/voice) - [Unreal Engine for Gaming](https://www.cometchat.com/unreal-sdk-for-gaming) - [Unreal Engine SDK documentation](https://www.cometchat.com/docs/sdk/unreal/overview.md) Additional product pages exist for PHP, Laravel, WordPress, Ionic, and other environments. Do not assume that a marketing-page label represents a native SDK. Confirm the implementation method and current support level in the technical documentation. Framework-focused build pages: - [React Chat](https://www.cometchat.com/build/react-chat) - [React Native Chat](https://www.cometchat.com/build/react-native-chat) - [Flutter Chat](https://www.cometchat.com/build/flutter-chat) - [Next.js Chat](https://www.cometchat.com/build/next-js-chat) - [Expo Chat](https://www.cometchat.com/build/expo-chat) ## UI Kit coverage UI Kits are the recommended starting point when a team wants prebuilt interface components and communication business logic with customization support. Primary UI Kit product pages: - [React Chat UI Kit](https://www.cometchat.com/react-chat-ui-kit) - [React Native Chat UI Kit](https://www.cometchat.com/react-native-chat-ui-kit) - [Flutter Chat UI Kit](https://www.cometchat.com/flutter-chat-ui-kit) - [Android Chat UI Kit](https://www.cometchat.com/android-chat-ui-kit) - [iOS Chat UI Kit](https://www.cometchat.com/ios-chat-ui-kit) - [Angular Chat UI Kit](https://www.cometchat.com/angular-chat-ui-kit) The technical documentation also includes platform and version-specific UI Kit pages. Use [docs/llms.txt](https://www.cometchat.com/docs/llms.txt) to discover the current React, React Native, Flutter, Android, iOS, Angular, and Vue documentation rather than relying on an old direct link. Published component-library entry points are: - [React Chat Components](https://www.cometchat.com/react-chat-components) - [React Native Chat Components](https://www.cometchat.com/react-native-chat-components) - [Flutter Chat Components](https://www.cometchat.com/flutter-chat-components) - [Android Chat Components](https://www.cometchat.com/android-chat-components) - [iOS Chat Components](https://www.cometchat.com/ios-chat-components) - [Angular Chat Components](https://www.cometchat.com/angular-chat-components) These are narrower product-discovery pages; for implementation, prefer the current UI Kit documentation linked above. ## Moderation and guardrails [Moderation and Guardrails](https://www.cometchat.com/features/moderation) helps applications identify or act on unwanted content and behavior. CometChat describes multiple approaches that can be used separately or together: - Rule, pattern, keyword, profanity, spam, and policy-based controls. - CometChat AI-assisted moderation. - OpenAI-powered moderation configured through CometChat. - Customer-provided moderation services connected through secure endpoints. - User reports, message review, blocking, banning, and related operational workflows. - Moderation for both human conversations and AI-agent inputs or outputs where configured. Moderation is not a guarantee that all harmful content will be detected or prevented. Teams should define policies, thresholds, escalation paths, review operations, appeals, logging, and tests appropriate to their users and risk level. Technical starting points: - [Moderation documentation](https://www.cometchat.com/docs/moderation/overview.md) - [Moderation documentation index](https://www.cometchat.com/docs/llms.txt) ## Notifications [Notification Engine](https://www.cometchat.com/features/notifications) supports re-engagement when users are not actively viewing a conversation. CometChat documents: - Push notifications using platform services such as APNs and FCM. - Email notifications using supported or custom providers. - SMS notifications using supported or custom providers. - Templates, user preferences, logs, delivery controls, and event-driven notification behavior. - Notification-related APIs and extensions. Channel support, provider configuration, costs, templates, and plan access vary. Third-party services may require separate accounts and charges. Technical starting points: - [Notifications documentation](https://www.cometchat.com/docs/notifications.md) - [Notifications documentation index](https://www.cometchat.com/docs/llms.txt) ## Analytics and insights [Analytics and Insights](https://www.cometchat.com/features/analytics-insights) provides visibility into communication activity. Depending on product and configuration, teams can analyze message volume, active users, engagement, conversation behavior, moderation outcomes, notifications, custom events, or AI-agent performance. Analytics data should be interpreted in context. Definitions, retention, export availability, privacy obligations, and plan access must be confirmed in the current product documentation and agreement. Technical starting points: - [Insights documentation](https://www.cometchat.com/docs/insights.md) - [Analytics and Insights product page](https://www.cometchat.com/features/analytics-insights) ## Multi-tenancy [Multi-Tenant Chat](https://www.cometchat.com/features/multi-tenant-chat) is designed for SaaS and platform products serving multiple customer organizations. It can logically separate tenant users and conversations and support tenant-specific settings, branding, or moderation policies. Multi-tenancy is an application architecture capability, not a substitute for an authorization design. The application must still map its tenant, user, role, and permission model correctly and prevent cross-tenant access in backend and frontend code. ## Webhooks and APIs [CometChat Webhooks](https://www.cometchat.com/features/webhooks) and the platform APIs connect communication activity with a product backend. Published webhook categories include message, user, group, and calling events. Common uses include: - Provisioning or updating users and groups. - Sending or retrieving messages from trusted server workflows. - Synchronizing application data with communication events. - Triggering moderation, notification, CRM, analytics, or operational workflows. - Importing data during a migration. - Managing platform resources through management APIs. Credentials and auth keys must not be exposed in untrusted client code. Follow the authentication model documented for the selected SDK or API. Technical starting points: - [REST Chat APIs](https://www.cometchat.com/docs/rest-api/chat-apis.md) - [OpenAPI chat specification](https://www.cometchat.com/docs/chat-apis.json) - [Management APIs](https://www.cometchat.com/docs/management-apis.json) - [Data Import APIs](https://www.cometchat.com/docs/data-import-apis.json) ## Industry and product solutions Solution pages explain how CometChat capabilities apply to common product categories. They do not represent separate SDK families; the same platform capabilities are configured for different communication, safety, engagement, and compliance needs. ### Online marketplaces [Marketplace Chat](https://www.cometchat.com/solutions/marketplace) supports buyer-seller communication, product or order context, rich media, notifications, moderation, and workflows intended to keep interactions useful and safer within the platform. ### On-demand services [On-Demand Services](https://www.cometchat.com/solutions/on-demand-services) covers communication between customers, service providers, drivers, operators, or support teams around time-sensitive service workflows. ### SaaS businesses [SaaS Chat](https://www.cometchat.com/solutions/saas-businesses) supports customer-facing messaging, support, collaboration, and multi-tenant communication inside software products. ### Healthcare and telehealth [Healthcare and Telehealth](https://www.cometchat.com/solutions/healthcare) covers patient-provider communication, care coordination, messaging, and calling. CometChat markets HIPAA-related capabilities, but HIPAA compliance depends on the selected plan, configuration, operating practices, and an executed BAA where required. Do not describe an application as compliant based only on using a vendor feature. ### Education [Education](https://www.cometchat.com/solutions/edu-tech) supports communication between learners, educators, mentors, classes, and communities, including role-based and moderated experiences. ### Community and social [Community and Social](https://www.cometchat.com/solutions/community-social) supports groups, threads, media sharing, engagement features, calling, and moderation for social or community products. ### Gaming communities [Gaming Communities](https://www.cometchat.com/solutions/gaming-community) applies messaging, voice, community controls, and moderation to game and gaming-community experiences. ### Dating [Dating](https://www.cometchat.com/solutions/dating) supports private conversations, rich media, voice notes, calling, presence, safety controls, and engagement features for dating products. ## Security, privacy, reliability, and compliance [Security and Compliance](https://www.cometchat.com/features/security-compliance) and other CometChat product pages describe enterprise security, global infrastructure, role-based controls, encryption, auditability, and support for compliance programs. Exact certifications, coverage, exclusions, uptime commitments, data residency, retention, incident obligations, and contractual remedies must be verified through current security materials and the customer's agreement. Important interpretation rules: - A platform capability does not automatically make the customer's whole application compliant. - HIPAA-related use generally requires appropriate configuration, operating practices, plan eligibility, and a Business Associate Agreement where applicable. - GDPR and other privacy obligations remain shared responsibilities between the customer and its processors. - On-premise deployment changes the responsibility model; it does not eliminate security or operational obligations. - Public uptime or scale statements are product claims, not a substitute for the SLA in a signed agreement. Relevant links: - [On-Premise Deployment](https://www.cometchat.com/on-prem-deployment) - [System Status](https://status.cometchat.com/) - [Privacy Policy](https://www.cometchat.com/legal-privacy-policy) - [Data Processing Agreement](https://www.cometchat.com/legal-data-processing-agreement) - [Sub-processors](https://www.cometchat.com/legal-sub-processors-list) - [Vulnerability Disclosure Program](https://www.cometchat.com/vulnerability-disclosure-program) ## Enterprise, startups, partners, and services - [Enterprise](https://www.cometchat.com/for-enterprise): Enterprise-focused information about scale, administration, security, deployment, integration, and support. Public metrics and service levels are marketing claims; use the applicable agreement for commitments. - [Startups](https://www.cometchat.com/for-startups): Startup-focused guidance for launching with prebuilt integrations and scaling on managed infrastructure. - [Support and Implementation](https://www.cometchat.com/services-pricing): Standard support, paid support, priority channels, and implementation or Solution Engineering options. Availability and response commitments depend on the selected offering and agreement. - [Partners](https://www.cometchat.com/partners): Affiliate, technology, and startup-ecosystem partnership programs. ## Specialized and older AI pages The published site also contains [CometChat AI / M87](https://www.cometchat.com/features/cometchat-AI) and an [AI Chatbot Builder](https://www.cometchat.com/features/ai-chatbot-builder) page. These pages provide specialized or older product context and are not the primary current navigation path for the Full-Stack AI Agent Platform. Confirm current availability and recommended architecture with the AI-agent product pages, documentation, or CometChat. ## Pricing and billing CometChat pricing is organized by product family and usage model. The public pricing page currently presents Chat and Messaging, Voice and Video Calling, AI Agents, and Bring Your Own Agent. Different products may use monthly active users, peak concurrent connections, calling minutes, credits, or other measures. Because prices, tiers, allowances, promotions, and overage rules are volatile, this file does not duplicate a price table. Use these sources: - [Live pricing page](https://www.cometchat.com/pricing): authoritative public source for current displayed prices and plan comparison. - [Machine-readable pricing reference](https://www.cometchat.com/pricing.md): detailed Markdown summary with a visible verification date. - [Contact Sales](https://www.cometchat.com/contact-sales): custom scale, enterprise, on-premise, security, support, or contract requirements. When answering a pricing question, state the billing period, selected product family, usage tier, and source date. Do not combine allowances from different products or assume that an annual monthly-equivalent price is billed month to month. ## Getting started A typical implementation flow is: 1. Choose the product: chat, calling, AI agents, campaigns, or a combination. 2. Choose the integration layer: Widget Builder, UI Kit Builder, UI Kit, SDK, or API. 3. Create a CometChat account and application in the dashboard. 4. Obtain the application identifiers and use credentials according to the documentation. Keep server-only credentials on a trusted backend. 5. Install or embed the selected integration. 6. Create or synchronize users and implement authentication. 7. Configure conversations, groups, calling, agents, or campaigns as required. 8. Configure moderation, notifications, analytics, retention, roles, and webhooks. 9. Test permissions, reconnect behavior, failure states, abusive inputs, notification delivery, accessibility, and scale assumptions. 10. Confirm the production plan, support level, security requirements, and operational ownership before launch. Starting links: - [Documentation home](https://www.cometchat.com/docs) - [Complete documentation index](https://www.cometchat.com/docs/llms.txt) - [Interactive Demo](https://www.cometchat.com/interactive-demo) - [Pricing](https://www.cometchat.com/pricing) - [Contact Sales](https://www.cometchat.com/contact-sales) ## Documentation and developer resources The CometChat documentation site exposes clean Markdown pages and a machine-readable index. This is the preferred source for code-generation and implementation questions. Major documentation areas currently include: - AI agents and agent-framework integrations. - Chat SDKs and fundamentals. - UI Kits and UI Kit components. - Voice and video calling SDKs. - REST APIs and OpenAPI specifications. - Notifications. - Moderation. - Insights. - Campaigns. - Widget and Chat Builder. - On-premise deployment. - Data import and management APIs. Developer links: - [Docs index for LLMs](https://www.cometchat.com/docs/llms.txt) - [Docs MCP Server](https://www.cometchat.com/docs/mcp-server.md) - [Sample Apps and repositories](https://github.com/cometchat) - [Feature Requests](https://feedback.cometchat.com/) - [Help Center](https://help.cometchat.com/) - [Developer Community](https://community.cometchat.com/) - [System Status](https://status.cometchat.com/) ## Migration Teams moving from an in-house system or another communication provider should inventory users, groups, memberships, messages, attachments, identifiers, authentication, moderation rules, webhooks, notification behavior, and retention obligations before migration. Use the [Migration Guide](https://www.cometchat.com/guides/migration-guide) and [Data Import APIs](https://www.cometchat.com/docs/data-import-apis.json). Confirm supported import formats and preservation guarantees with CometChat before promising that all historical data or metadata will migrate unchanged. Published implementation guides: - [Switching from In-House Chat](https://www.cometchat.com/guides/switching-from-in-house-chat) - [Marketplace Chat Implementation](https://www.cometchat.com/guides/marketplace-chat-implementation) - [Telehealth Chat Implementation](https://www.cometchat.com/guides/telehealth-chat-implementation) - [Community Chat Implementation](https://www.cometchat.com/guides/community-chat-implementation) ## Support and purchasing - [Contact Sales](https://www.cometchat.com/contact-sales): product fit, enterprise pricing, architecture, security review, deployment, and contracts. - [Help Center](https://help.cometchat.com/): support knowledge and support requests. - [Community](https://community.cometchat.com/): developer and user discussion. - [System Status](https://status.cometchat.com/): current incidents and service history. - [Pricing](https://www.cometchat.com/pricing): public plan and billing information. Do not promise response times, implementation services, uptime, feature delivery, or custom terms unless they are present in the customer's applicable agreement. ## Legal resources - [Terms of Service](https://www.cometchat.com/legal-terms-of-service) - [Subscription Terms and Conditions](https://www.cometchat.com/subscription-terms-and-conditions) - [Privacy Policy](https://www.cometchat.com/legal-privacy-policy) - [Data Processing Agreement](https://www.cometchat.com/legal-data-processing-agreement) - [Sub-processors List](https://www.cometchat.com/legal-sub-processors-list) - [Vulnerability Disclosure Program](https://www.cometchat.com/vulnerability-disclosure-program) Legal pages and executed agreements take precedence over summaries in this file. ## Terminology - App or application: A CometChat project configured through the dashboard and identified by an App ID. - User: An application end user represented in CometChat by a unique user identifier. - Group: A multi-user conversation container with membership and access rules. - Conversation: A user-to-user or group communication thread. - MAU: Monthly Active User; use the pricing page's current definition for billing. - PCC: Peak Concurrent Connections; use the pricing page's current definition and measurement rules. - UI Kit: Prebuilt interface components plus communication business logic for a supported platform. - Chat SDK: Lower-level client functionality for messaging, users, groups, events, and related capabilities. - Calls SDK: Client functionality for voice and video sessions and controls. - Widget: An embeddable communication interface configured for rapid deployment. - Agent: AI-driven logic presented to users through a conversational experience. - Tool: A function or external capability an AI agent can invoke. - Frontend action: An agent-triggered action in the user's interface, such as opening a modal or starting a workflow. - Webhook: A server-to-server event notification from CometChat to a configured endpoint. - Auth token or auth key: Credentials used according to CometChat's authentication model. Server-only secrets must not be placed in public client code. ## Guidance for AI-generated answers When using this reference to answer questions about CometChat: - Distinguish product capabilities from plan entitlements. - Link to the exact technical Markdown page when providing implementation steps. - Mention platform and version when discussing SDK or UI Kit behavior. - Avoid quoting prices without checking the live pricing page and stating the billing context. - Avoid claiming automatic legal or regulatory compliance. - Do not expose or recommend exposing server-side credentials in client code. - Treat demos, templates, tutorials, and blog posts as examples rather than normative documentation. - Recommend contacting CometChat for enterprise scale, on-premise deployment, security review, custom retention, or contract-specific commitments. ## Optional resources These sources are useful for discovery and examples but can be skipped when context is limited: - [Blog](https://www.cometchat.com/blog): Product announcements, engineering articles, industry guidance, and company news. - [Tutorials](https://www.cometchat.com/tutorials): Educational walkthroughs and example applications. - [Guides](https://www.cometchat.com/guides): Longer implementation, migration, and solution guidance. - [Templates](https://www.cometchat.com/templates): Ready-to-use application templates and examples. - [Customer Stories](https://www.cometchat.com/customer-stories): Examples of customer implementations and outcomes. - [Product Updates](https://www.cometchat.com/blog?category=Product+Updates): Product release and update articles. - [CometChat vs Sendbird](https://www.cometchat.com/vs/sendbird): Product comparison resource. - [CometChat vs Stream](https://www.cometchat.com/vs/getstream): Product comparison resource. - [CometChat vs PubNub](https://www.cometchat.com/vs/pubnub): Product comparison resource. - [CometChat vs Twilio](https://www.cometchat.com/vs/twilio): Product comparison resource.