Call permission

call_permission_request Asks permission to call on WhatsApp.

How it works

Calling a customer on WhatsApp requires explicit permission. This model is the request: you write the reason, and WhatsApp adds the authorization part, with the name from your account profile. The CALL_PERMISSION_REQUEST component has no fields at all — its presence is what defines the model. There is no accept button and decline button in the template: WhatsApp draws the action. Meta’s documentation mentions allow calls and temporarily allow, for 7 days, plus declining, but it doesn’t describe the screen — so the preview above is an approximation, and the button arrangement on the device may differ. What is documented, and what you can rely on, is the answer: it arrives on your webhook with response as accept or reject. When the permission is temporary, is_permanent: false and expiration_timestamp come along.

Meta does not allow combining the permission component with other interactive components. No buttons, carousel or offer badge on the same template.

At creation and at send time

At creation	At send time
The text explaining why you want to call	The value of each variable
The permission component

Fields in this model

Field	What it is for	Rule
`category`	You choose	`UTILITY` or `MARKETING`
`BODY`	The reason for the call	Up to 1024 characters
`CALL_PERMISSION_REQUEST`	The authorization request	No fields

Full JSON

Two JSON payloads: one creates the template, and Meta approves it once. The other sends the message, and goes on every dispatch, with that send’s values in the variables marked with braces.

1. Create the template

POST /whatsapp/businesses/{wabaId}/templates — see API reference.

{
  "name": "exemplo_call_permission_request",
  "category": "UTILITY",
  "language": "en_US",
  "allow_category_change": true,
  "parameter_format": "NAMED",
  "components": [
    {
      "type": "BODY",
      "text": "Hi {{customer_name}}, your order {{order_number}} is confirmed and ships today.",
      "example": {
        "body_text_named_params": [
          {
            "param_name": "customer_name",
            "example": "Marina"
          },
          {
            "param_name": "order_number",
            "example": "1042"
          }
        ]
      }
    },
    {
      "type": "CALL_PERMISSION_REQUEST"
    }
  ]
}

2. Send it once approved

POST /v1/channels/{channelId}/messages — see Send template.

{
  "recipient": {
    "identifier": "5511999999999"
  },
  "content": {
    "type": "TEMPLATE",
    "attachments": [
      {
        "template": {
          "name": "exemplo_call_permission_request",
          "language": {
            "policy": "deterministic",
            "code": "en_US"
          },
          "components": [
            {
              "type": "body",
              "parameters": [
                {
                  "type": "text",
                  "text": "{{customer_name}}"
                },
                {
                  "type": "text",
                  "text": "{{order_number}}"
                }
              ]
            }
          ]
        }
      }
    ]
  }
}

What Meta rejects here

Buttons, carousel or any other interactive component on the same template.
The AUTHENTICATION category.

Channels

Messages

Templates (WhatsApp)

Flows (WhatsApp)

Webhooks

How it works

At creation and at send time

Fields in this model

Full JSON

1. Create the template

2. Send it once approved

What Meta rejects here

​How it works

​At creation and at send time

​Fields in this model

​Full JSON

​1. Create the template

​2. Send it once approved

​What Meta rejects here

How it works

At creation and at send time

Fields in this model

Full JSON

1. Create the template

2. Send it once approved

What Meta rejects here