Loading…
Topic
66 posts about Twilio. Every summary links to the original.
See the idea
The Branded Calling trust chain, layer by layer: how identity, STIR/SHAKEN attestation, Rich Call Data, and carrier delivery combine so a verified brand name reaches the recipient's screen.
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
This webinar addresses the gap between impressive voice AI demos and reliable production deployments, focusing on global rollout barriers such as spam-flagged outbound calls, legal delays, latency, and custom integration work. It presents Twilio Voice and AI through the Guinness Price Index case, alongside reported examples from Docplanner and audibene, whose use of the Twilio platform is said to halve costs, double booking efficiency, and improve inbound reachability by 30 percent. A developer demonstration shows how Twilio Skills and an AI coding agent configure an initial setup, while an open-standard Model Context Protocol (MCP) Server and Twilio Agent Connect SDK replace growing custom glue code. It also covers Conversation Relay for real-time audio, Conversation Memory and Conversation Orchestrator for AI-to-human handoffs, and connections to privately hosted models to retain cloud and roadmap control. The session frames compliance, privacy, personalisation, and vendor lock-in as operational concerns in scaling voice AI.
Video calling can add direct, personal communication to customer and patient interactions without moving conversations to a third-party app or website. The post outlines an integration path based on choosing a platform, selecting development-specific SDKs, and either building a custom application or deploying and adapting an open-source one. Twilio is presented as a cloud communications platform offering APIs, SDKs, reference apps, and documentation, with SDKs for JavaScript, Android, and iOS; listed build examples also use Svelte, Go, Python, ASP.NET Core, Angular, Node.js, TypeScript, and Express. Open-source options provide features such as screen sharing and network-condition monitoring, while Twilio Video supports branded virtual backgrounds and layouts, but the source does not report implementation results.
Passwordless authentication replaces passwords with one-time codes delivered by SMS, and this tutorial builds a Rust app around that flow. The app uses Twilio Verify for OTP generation and validation, with GET and POST routes at "/" for collecting a phone number and at "/verify" for entering the received code. It sets up a Cargo project with Axum, Handlebars templates, sessions, dotenvy configuration, and the rustlio Twilio client, while environment variables hold the Account SID, Auth Token, and Verify Service SID. The implementation also serves HTML forms and static assets, with verification status rendered as a success or error message. Running cargo run starts the server on port 8080, where users can submit a number, receive an SMS, and see whether the verification code is valid.
Passwordless authentication with PHP and Twilio Verify replaces password entry with a phone-based one-time passcode flow, intended to reduce password-related risk and simplify sign-in. The tutorial uses a Slim base project, Composer dependencies, Dotenv configuration, a Twilio Verify Service SID, and PHP session state to support the flow. Users submit a phone number through the root route; the server asks Twilio Verify to send an SMS OTP, redirects to /verify, and checks the submitted code through the verification endpoint. The example’s verification form restricts input to a six-digit numeric value, and the application reports whether verification succeeded or failed after testing locally with composer serve on port 8080.
The tutorial builds a passwordless authentication flow in Go that uses Twilio Verify to send and validate one-time passwords (OTPs) by SMS, avoiding the need for users to manage passwords. It defines a small net/http API with GET and POST handlers for "/" and "/verify": the first collects a mobile number and starts verification, while the second accepts the received code and displays the result. The setup covers Go 1.23 or later, module dependencies, dotenv configuration for the Twilio Account SID, Auth Token, and Verify Service SID, plus session handling for the phone number. The verification check calls Twilio's CreateVerificationCheck() and renders success or failure using templates; running go run main.go starts the server on port 8080 for testing.
Passwordless authentication can replace passwords with time-based one-time passwords (TOTP), but implementing the setup and verification flow requires coordinating an authenticator app with a verification service. This tutorial builds a web-based PHP application using Twilio Verify, Slim, Twig, and the Twilio PHP Helper Library. Users submit a username, create an initially unverified Factor resource, scan a QR code or enter its setup code, and submit the first six-digit code; later, they enter codes generated by the authenticator app for validation. The project configures Twilio credentials and a Verify Service SID through environment variables, adds session and flash-message support, generates QR codes, defines routes and templates, and runs locally with composer serve on port 8080. The conclusion presents TOTP passwordless authentication as more convenient and potentially more secure than passwords, while acknowledging added application complexity.
The best engineering reads, once a week.
