Twilio Dialer
> return_hub · module_loader · boot
> BOOT_SEQUENCE // ROY-HUB
HOST session.local · SEGMENT PRIVATE_NET · MEM 640K SUFFICIENT
CHECKSUM 0x9f2e · SIG VERIFIED · SESSION ACTIVE
> No clutter, no ads, no bait-n-switch—just simple tools that work at no cost
> return_hub · module_loader · boot
> return_hub · twilio_voice · boot
Twilio Dialer places outbound browser calls with your Twilio Account SID, API key, TwiML App, and a verified caller ID. Twilio bills the calls. Roy's Tools does not sell minutes.
Place browser VoIP calls with your own Twilio Account SID, API key, TwiML App, and a verified caller ID. Credentials stay under your Twilio account; this page does not sell minutes.
The page cannot invent a TwiML App. You create that app in Twilio, point it at this site’s webhook, and verify the caller ID before the keypad can connect.
No. You need a Twilio account, a TwiML App that can POST back to this site’s webhook path, and a verified caller ID. Calls are billed by Twilio, not by Roy's Tools.
You enter keys in the browser to request an access token. Do not paste secrets into a shared computer. See Privacy and Terms for hosting logs and your responsibility for vendor credentials.
Common causes: API Key and Secret not on that Account SID, TwiML App on another account, unverified caller ID, or a non-US Twilio region that needs the Account region field set.
No. It is a keypad dialer for outbound browser calls using your TwiML App. It is not inbound IVR, SMS, or recording management.
Twilio Voice in the browser expects HTTPS (and a microphone permission). Use the production site or local HTTPS when testing.