Skip to main content
  • Home
  • >
  • Reject Calls with Blocklist

Reject Calls with Blocklist

By Twilio

  • Voice
  • Twilio
  • Quick Deploy
  • Applications

How it works:

  • User enters a comma-separated list of phone numbers that they wish to reject
  • User calls their Twilio phone number from a phone number in the blocklist. The user should receive a message and the call will not go through.
  • User calls their Twilio phone number from a phone number not in the blocklist and not their own phone number. The call should go through.
Launch and test this app in a few minutes with Quick Deploy. No server needed. Quick Deploy will automatically configure and deploy this app using Twilio Functions. Learn more about Twilio Functions
Step 1:Log in to Twilio
Step 2:Set up your application
This application requires a Twilio-supplied phone number to work properly.
Get a Twilio phone number
You will get a US number that is configured for this application. You can change this or port over an existing number later.International number regulations
Step 3:Deploy your application and try it out!
Deploy this application
This will use the details entered above to deploy your application to Twilio Functions. You will be able to view the application in the browser and edit it using the Functions UI. Learn more about Twilio Functions
Deploying applicationThis might take up to a minute
Success! Your application has been deployed.
Oops...something went wrong. Retry
Step 4:View and edit your application
Once deployed, any changes to the fields above will not be applied to your app. To make changes, here are two options
Refresh the page, edit customizations and re-deploy the application
Edit your customizations directly in code
Why use Quick Deploy?
No coding required to launch
Easy to edit and iterate post launch
No server management
Scales automatically
Secure by default

Don't see what you want? Request a code sample Explore Docs

Questions about scaling, pricing, or which products/features to use? Get a consultation

There was an issue loading the page.

Please try again in some time.