> ## Documentation Index > Fetch the complete documentation index at: https://docs.kapso.ai/llms.txt > Use this file to discover all available pages before exploring further. # For your team > Use Kapso for your own WhatsApp operations Use Kapso when your own team needs to run support, sales, operations, or outbound messaging on WhatsApp. The common patterns below cover most internal use cases. * [Use Kapso as your WhatsApp API](#use-kapso-as-your-whatsapp-api) * [Use workflows to automate WhatsApp](#use-workflows-to-automate-whatsapp) * [Connect your team WhatsApp Business apps](#connect-your-team-whatsapp-business-apps) * [Use Broadcasts for mass messaging](#use-broadcasts-for-mass-messaging) * [Use the shared team inbox](#use-the-shared-team-inbox) ## Use Kapso as your WhatsApp API Connect your company WhatsApp numbers to Kapso and use it as your operational WhatsApp layer. This setup works when you want to: * send notifications and outbound messages with templates * receive WhatsApp messages through webhooks * let AI agents or backend systems operate on conversations * monitor activity from the inbox, webhook deliveries, and execution logs This is the best fit when WhatsApp is part of your product or operations stack and you want one API surface for sending, receiving, and observing activity. ## Use workflows to automate WhatsApp Kapso can also sit on top of your number as the automation layer. Use workflows and functions when you want more than simple message sending. Typical uses: * build AI agents, such as a support or qualification agent * build deterministic workflows for reminders, routing, handoff, and follow-up * call your own systems through APIs * combine human and automated handling in the same conversation flow This is the right setup when you want WhatsApp to behave like an operational system, not just a messaging endpoint. ## Connect your team WhatsApp Business apps You can also connect the WhatsApp Business apps used by your own team. A common example is a sales team that wants to keep using the WhatsApp Business app while centralizing automation and visibility in Kapso. With this setup, you can: * sync your CRM automatically through APIs and webhooks * analyze conversations with LLMs * manage multiple numbers from one project * keep a centralized record of activity instead of relying on each phone separately This works well when the team still needs the app experience, but you also want shared visibility and programmatic access. ## Use Broadcasts for mass messaging Use Broadcasts when you need mass outbound messaging with approved templates. This is a better fit than manual inbox sending when the same campaign or notification needs to reach many recipients with tracking and delivery stats. Typical uses include reminders, promotions, re-engagement campaigns, and operational notifications. ## Use the shared team inbox Use `inbox.kapso.ai` when your support or operations team needs a dedicated workspace for live conversations. This is especially useful when you want a mix of AI and human support: * AI can automate parts of the conversation through workflows * humans can take over through the inbox when needed * the team can work in one shared interface instead of separate phones This is often the best setup for support teams that want structured operations without giving every operator full dashboard access. ## Invite unlimited team members Kapso does not charge per seat. Invite as many people to a project as you need, on any plan. Each member gets a role: * `owner`: full access, including billing and adding other owners * `admin`: manage the project and its members * `member`: use the dashboard * `human_agent`: inbox only, no dashboard access Use `human_agent` for support staff who only handle conversations. Invite from **Project settings → Members**. ## Next steps Connect your first production number. Start handling conversations from the shared inbox. Send approved template campaigns at scale. Add automation, handoff, and AI-driven flows.