TwiMLTM Voice: <Reject>

The <Reject> verb rejects an incoming call to your Twilio number without billing you. This is very useful for blocking unwanted calls.

If the first verb in a TwiML document is <Reject>, Twilio will not pick up the call. The call ends with a status of 'busy' or 'no-answer', depending on the verb's 'reason' attribute. Any verbs after <Reject> are unreachable and ignored.

Note that using <Reject> as the first verb in your response is the only way to prevent Twilio from answering a call. Any other response will result in an answered call and your account will be billed.

Verb Attributes

The <Reject> verb supports the following attributes that modify its behavior:

Attribute NameAllowed ValuesDefault Value
reasonrejected, busyrejected


The reason attribute takes the values "rejected" and "busy." This tells Twilio what message to play when rejecting a call. Selecting "busy" will play a busy signal to the caller, while selecting "rejected" will play a standard not-in-service response. If this attribute's value isn't set, the default is "rejected."

Nesting Rules

You can't nest any verbs within <Reject> and you can't nest <Reject> in any other verbs.


<Reject> won't work when handling calls to the (deprecated) Twilio Sandbox number. Twilio must pick up the call to ask for the pin, at which point it's too late to reject.


Example 1: Reject a call playing a standard not-in-service message

<?xml version="1.0" encoding="UTF-8"?>
    <Reject />

Example 2: Reject a call playing a busy signal

<?xml version="1.0" encoding="UTF-8"?>
    <Reject reason="busy" />