> ## 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.

# Template lifecycle

> Understanding template statuses, Meta review, and syncing

## Create templates

Create templates directly in Kapso:

1. Go to **WhatsApp** > **Templates** in your project
2. Click **Create template**
3. Choose template type and configure
4. Submit for Meta review

Alternatively, create templates in [WhatsApp Manager](https://business.facebook.com/latest/whatsapp_manager/message_templates) and sync them to Kapso.

## Template statuses

| Status   | Meaning                                   |
| -------- | ----------------------------------------- |
| PENDING  | Submitted to Meta, awaiting review        |
| APPROVED | Ready to use                              |
| REJECTED | Failed Meta review (see rejection reason) |
| DISABLED | Temporarily disabled by Meta              |

In Kapso, "Submitted" means the template was sent to Meta and is waiting for review.

## Meta review times

* Reviews typically take up to 24 hours
* First approvals on new accounts may take longer
* Kapso does not add delays — all reviews are performed by Meta

Creating a template in Meta Business Manager vs Kapso makes no difference in review time.

## Sync templates from Meta

If you created templates in Meta Business Manager:

1. Go to **WhatsApp** > **Templates** in your project
2. Click **Sync from WhatsApp**
3. All templates will be imported and available in Kapso

Sync automatically retrieves all templates from your WhatsApp Business Account, regardless of how many you have. You can also sync via API:

```bash theme={null}
POST /whatsapp_templates/sync
```

<Note>
  Sync is disabled for sandbox numbers. Connect a production number to sync templates.
</Note>

## Common rejection reasons

* Missing business verification
* Policy violations in content
* Incorrect category selection (utility vs marketing)
* Low-quality media in headers
* Misleading or spammy content