> ## Documentation Index
> Fetch the complete documentation index at: https://docs.suprsend.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Start setting up your notifications with SuprSend by following quick start guides for one of the mentioned channels.

You can start with your primary channel and add rest of the channels just by [integrating with their respective vendors](/docs/vendors) and [adding their template content](/docs/templates).

<CardGroup cols={4}>
  <Card title="Email" icon="envelope-dot" iconType="solid" href="/docs/email-quick-start" />

  <Card title="SMS" icon="comment-sms" iconType="solid" href="/docs/sms-quick-start" />

  <Card title="WhatsApp" icon="whatsapp" iconType="solid" href="/docs/whatsapp-quick-start" />

  <Card title="Inbox" icon="inbox-full" iconType="solid" href="/docs/inbox-quick-start" />
</CardGroup>

<CardGroup cols={4}>
  <Card title="Mobile Push" icon="mobile-screen" iconType="solid" href="/docs/mobile-push-quick-start" />

  <Card title="Web Push" icon="laptop" iconType="solid" href="/docs/web-push-quick-start" />

  <Card title="Slack" icon="slack" iconType="solid" href="/docs/slack-quick-start" />

  <Card title="MS Teams" icon="windows" iconType="solid" href="/docs/ms-teams-quick-start" />
</CardGroup>

### Setup and test notification using APIs

You can try out SuprSend APIs from our [Postman collection](https://www.postman.com/suprsend/workspace/suprsend/collection/27786422-d77a13c1-8f59-406d-9669-078a10d52521).

### What's next

1. Check out [best practices](/docs/best-practices-notification-system-design) to design the right notification experience for your users.

2. **Invite other team members**- You can invite other collaborators from your team to your SuprSend account by inviting them from [Account Settings -> Teams](https://app.suprsend.com/en/account-settings/team) page. You'll get this option by clicking on the profile icon in the top nav bar.

3. Check out [example apps](/docs/task-management-app-guide) for end-to-end implementation details.

***
