School: Minister Destiny Testimony Schools Track: Adult Class: Certificate Topics — Year 1 (Foundations) · Home: Schools — Adult track Certificate behind this topic: "Twilio Essentials Unit 2: Programmable Voice" — LinkedIn Learning, earned by Minister Destiny Marie Morgan (Jun 06, 2025) Founded and presented by: Minister Destiny Marie Morgan, Minister
This lesson is educational information from Minister Destiny Testimony Schools. It teaches the public body of knowledge in this subject — the same ground Minister Destiny studied for her certificate — in this school's own words. It is not the original course, it does not award the original credential, and it is not legal or medical advice. If you are in danger right now, call 911.
Before you start
- This school never asks your name. Your progress is saved to your student record, so you can pick up on any device. If you pass this unit's quiz (80% or higher, retakes allowed), you earn a downloadable certificate with a blank line — you write your own name on it after you save it. Quiz answers are not shown; if you miss a question, re-read the lesson and try again.
- Minister Destiny studied programmable voice through a course that used one platform — Twilio — as its teaching example. This unit teaches the concepts every such platform shares, with Twilio named only as that historical example. No platform's course material is reproduced here.
- This is the voice companion to the Programmable Messaging unit. If messaging was software sending texts, this is software making, receiving, routing, and — carefully, lawfully — recording telephone calls.
The lesson
Part 1. How internet voice works — VoIP in plain language
For a century, phone calls travelled as a dedicated electrical circuit between two telephones. Voice over Internet Protocol (VoIP) replaces the circuit with packets: your voice is sliced into small digital pieces, each labelled and sent across internet-style networks, then reassembled at the other end fast enough that the conversation feels continuous. The labelling and handshaking follow public standards — SIP is the best-known signalling protocol, the "phone book and doorbell" that sets calls up, rings them, and tears them down, while the voice packets themselves ride alongside.
Programmable voice begins where VoIP meets software. When calls are packets and signals, a program can participate: it can decide where a call rings, play a message, listen for a keypad press, join two people together, or start a call by itself — a reminder call to a patient, a callback to a customer waiting in a queue. The platform sits between the organisation's software and the world's phone networks, translating instructions ("call this number, play this, connect to that team") into real calls on real carriers, and translating events back ("they pressed 2," "the call ended after four minutes," "no answer") into data the software can act on.
Voice packets hate delay and jitter, so call quality depends on connection quality in a way email never does. And because a program can place calls, scale cuts both ways — the same machinery runs a clinic's reminder system and, in dishonest hands, a robocall flood. The consent and identity rules in Parts 5 and 6 are what separate the two.
Part 2. Call flows and IVR — the phone tree, designed honestly
A call flow is the planned path of a call from first ring to goodbye: what the caller hears, what choices they get, where each choice leads, and what happens when nobody answers. The interactive part — "press 1 for appointments, press 2 for… " — is an IVR (interactive voice response) system: the caller responds by keypad or, in modern systems, by speaking, and the flow routes accordingly.
Everyone has suffered a bad IVR, so this unit teaches the rules that separate a tool from a trap. Keep menus short — three or four choices, most common first. Always provide a path to a human; a flow designed to exhaust callers into hanging up is abuse wearing a headset. State waits honestly, offer a callback when waits grow (the system keeps your place and calls you), and test the flow by calling it yourself, with background noise, as your least technical customer would. A call flow is public writing performed aloud: clarity, brevity, and a visible exit are the whole craft.
Part 3. Programmable call control — what software can do inside a live call
Once a call exists, software can steer it. The standard repertoire is small and powerful. Answer and greet: play information or connect the caller onward. Gather input: keypad digits or spoken answers that branch the flow ("enter your account number"). Transfer and bridge: connect the caller to a person or team, possibly after a whisper message only the staff member hears ("caller from the billing menu"). Conference: join several parties — the doctor, the interpreter, the family member — into one call. Queue: hold callers in order with music or messages, tracking position and wait. Record: capture some or all of the call (Part 4's consent rules govern this absolutely). Call back and call out: originate calls — reminders, alerts, follow-ups — on schedules or triggers, exactly as the messaging unit's API did for texts.
Two disciplines keep this power safe. First, every automated behaviour needs a stop: campaigns must honour do-not-call requests, queues must not trap, recordings must be pausable for sensitive details like card numbers. Second, events are logged: who was called, when, from what number, what path the call took, and how it ended — the voice equivalent of messaging's delivery receipts.
Part 4. Recording calls — consent is not a footnote
Programmable voice makes recording effortless — one instruction in the call flow — which is exactly why the law around it must be learned before the feature is admired. The general landscape, taught here at orientation level only (real programmes need legal advice for their states and countries): in the United States, federal law generally follows one-party consent — a recording is permitted if one party to the conversation consents, which covers a participant recording their own call. A number of states require all-party consent (often called two-party): everyone on the call must agree. Other countries differ again, and a call crossing borders can be governed by more than one regime at once.
The professional practice that satisfies nearly every regime: announce and obtain consent — "this call may be recorded for quality and training; please tell us if you'd rather it wasn't" — and honour a no. Businesses record for real reasons: training, quality, dispute records. But a recording is sensitive data: stored securely, kept only as long as its purpose justifies, never mined for purposes the caller never agreed to. Technology made recording cheap; consent keeps it legitimate.
Part 5. Caller ID and anti-spoofing — why you can trust a number again (partly)
Caller ID was built in a trusting era: the originating network simply asserted the number, and every network downstream believed it. Fraudsters industrialised that trust — spoofing a bank's, a hospital's, or a neighbour's number so the victim answers — until the phone became the least trusted device in the house. The repair is STIR/SHAKEN, the caller-ID authentication framework the FCC requires U.S. voice providers to implement: STIR is the technical standard, SHAKEN is how carriers apply it, and together they work like a signature. The originating carrier digitally signs a call, attesting how confident it is that the caller is entitled to use that number; receiving carriers verify the signature and can label or handle the call accordingly — the "verified" marks some phones now show.
For builders, the duties are plain: only present numbers your organisation is entitled to use, attest outbound calling honestly, and never spoof — not for jokes, not for "testing," not to raise answer rates. For everyone else: STIR/SHAKEN has made spoofing harder, but it has not ended robocalls, so a familiar number remains a hint, not proof — call sensitive callers back on a number you looked up yourself.
Part 6. Accessibility and abuse prevention — the responsibilities of scale
A system that can call thousands of people carries duties in two directions. Toward the people it calls: accessibility is a design requirement, not a favour. IVR menus must be usable by people who cannot hear well, cannot speak easily, or cannot press keys quickly — which means speech options where feasible, generous timeouts, text alternatives (the messaging channel from the companion unit), and above all that human path from Part 2. Callbacks and reminders must respect time zones and quiet hours, identify the caller immediately, and stop on request — the TCPA consent principles from the messaging unit apply to automated calls with equal or greater force, and the national do-not-call rules sit beside them.
Toward everyone else: platforms and customers share responsibility for preventing abuse — rate limits, authentication of callers, monitoring for fraud patterns, and swift shutdown of abusive campaigns. A legitimate organisation helps by keeping its own account secure, because a hijacked voice account can flood a city in an afternoon. Programmable voice is care delivered by software, precisely as long as its builders treat consent, identity, and accessibility as the product.
Words to know — Programmable Voice — Phone Calls Built by Software (Twilio Essentials)
- VoIP (Voice over Internet Protocol) — carrying voice as digital packets over internet-style networks instead of a dedicated telephone circuit.
- Call flow — the planned path of a call: greetings, choices, routing, and what happens at every branch and ending.
- IVR (interactive voice response) — the menu system that lets callers respond by keypad or voice and routes the call accordingly.
- Callback — a system that keeps a caller's place in line and calls them back instead of making them hold.
- One-party / all-party consent — the two recording-law families: one participant's agreement suffices, or everyone on the call must agree.
- Spoofing — falsifying the caller ID so a call appears to come from a different, often trusted, number.
- STIR/SHAKEN — the FCC-required caller-ID authentication framework: originating carriers digitally sign calls and receiving carriers verify the signature.
- Attestation — the signed statement of how confident the originating carrier is that the caller may use the number shown.
- Queue — an ordered line of waiting callers, with position and wait time tracked by the system.
- Do-not-call — the registers and rules requiring organisations to stop marketing calls to numbers that have opted out or registered.
Myths vs facts — Programmable Voice — Phone Calls Built by Software (Twilio Essentials)
- Myth: If the caller ID shows my bank's number, it is definitely my bank. Fact: Caller ID could historically be asserted without proof, and spoofing persists; STIR/SHAKEN verification helps, but calling back on a number you looked up yourself remains the safe habit.
- Myth: Recording calls is legal everywhere if the business announces it in its terms and conditions. Fact: Recording law varies — federal one-party consent, all-party consent in a number of states, different rules abroad — and announced, honoured consent is the practice that satisfies them.
- Myth: A good IVR should handle everything so callers never need staff. Fact: An IVR with no reachable human path is a trap, not a tool; honest design always keeps a way to a person.
- Myth: STIR/SHAKEN has ended robocalls. Fact: It has made spoofing harder and legitimate calls easier to verify, but unauthenticated traffic persists and vigilance is still required.
- Myth: Automated reminder calls need no consent because they are helpful. Fact: Helpfulness is not consent; automated calls sit under the same TCPA consent and do-not-call discipline as other automated outreach.
Think it through — Programmable Voice — Phone Calls Built by Software (Twilio Essentials)
A dental practice is designing its new phone system. The draft flow offers six menu options, no route to reception ("to encourage online booking"), recordings switched on for all calls without announcement ("our terms cover it"), and reminder calls that display the personal mobile number of the practice manager "because patients answer it more."
Walk it through: (1) Menu design (Part 2): six options bury the common needs; shorten to the three or four callers actually use, ordered by demand. (2) The human path (Parts 2 and 6): removing the route to reception converts a tool into a trap and fails accessibility duties — restore it and say so in the menu. (3) Recording (Part 4): buried terms are not announced consent, and patients may span one-party and all-party states; add a spoken announcement and honour refusals. (4) Caller identity (Part 5): presenting the manager's personal number is exactly the entitlement violation STIR/SHAKEN exists to expose — reminders must present a number the practice is entitled to use, ideally its own verified number. (5) What survives review is smaller and duller than the draft — and lawful, accessible, and trusted, which is the point of every rule in this unit.
Try this — Programmable Voice — Phone Calls Built by Software (Twilio Essentials)
- ☐ Call one IVR you use (a pharmacy, a utility) and grade it: menu length, human path, honest waits, callback offer
- ☐ Sketch a three-option call flow for a small organisation you know, including what happens when nobody answers
- ☐ Look up the FCC's caller-ID authentication page (fcc.gov) and write, in your own words, what a "verified" call does and does not guarantee
- ☐ Draft a recording announcement of two sentences that a caller could actually refuse, and note where in a flow it belongs
- ☐ List three accessibility features a voice system owes its callers, and where each appears in a call flow
Resources to keep — Programmable Voice — Phone Calls Built by Software (Twilio Essentials)
- Federal Communications Commission (fcc.gov) — the official caller-ID authentication (STIR/SHAKEN) page and consumer guidance on robocalls and spoofing.
- Federal Trade Commission (ftc.gov) — consumer advice on phone scams and the National Do Not Call Registry.
- Twilio (twilio.com) — named only as the platform Minister Destiny studied; its public voice documentation illustrates the general call-control concepts in one vendor's dialect.
- CTIA (ctia.org) — the wireless industry association; public materials on verified calling and messaging conduct.
What you earned / what's next — Programmable Voice — Phone Calls Built by Software (Twilio Essentials)
✅ Programmable Voice — Phone Calls Built by Software (Twilio Essentials) complete (quiz score 80% or higher): You can explain VoIP and call flows in plain language, design an honest IVR, state the consent rules for recording and automated calling, and explain how STIR/SHAKEN is rebuilding trust in caller ID.
Your certificate
Minister Destiny Testimony Schools Certificate of Completion — Programmable Voice — Phone Calls Built by Software (Twilio Essentials)
This certificate is presented by Minister Destiny Marie Morgan, Minister
Awarded to: ______________________________ (write your name here after you download — your name is never collected or stored by this school)
Date completed: ______________
Congratulations. You understand how software learned to speak on the telephone — and the consent and honesty that keep its voice welcome. Carry both into whatever you build next. — Minister Destiny Marie Morgan
This is a certificate of educational completion from Minister Destiny Testimony Schools. It is not a state license, a government certification, or the original course credential.
What's next: Return to the Certificate Topics for your next Year 1 Foundations topic.
Sources
- Combating Spoofed Robocalls with Caller ID Authentication — Federal Communications Commission (fcc.gov) — STIR/SHAKEN framework, signing, and verification as officially described.
- FCC and FTC consumer guidance on robocalls, spoofing, and the Do Not Call Registry — fcc.gov and ftc.gov — consent and consumer-protection principles.
- General programmable-voice concepts as documented publicly by platform providers, including Twilio (twilio.com) — call flows, IVR, queues, and call control at orientation level only; no course content reproduced.
- CTIA public materials on verified calling — CTIA (ctia.org) — industry practice for caller identity.
Course Record — Programmable Voice — Phone Calls Built by Software (Twilio Essentials)
- Learning outcomes: On completing this unit, the student can:
- explain VoIP in plain language: voice as labelled packets, set up by signalling standards such as SIP
- describe a call flow and design an IVR menu that is short, honestly ordered, and always offers a path to a human
- list the standard call-control repertoire — gather input, transfer, conference, queue, record, callback — and the stop conditions each needs
- compare one-party and all-party recording consent at general level and state the announce-and-honour practice
- explain caller-ID spoofing and how STIR/SHAKEN signing and attestation rebuild verifiable trust, with its limits stated honestly
- name the accessibility and abuse-prevention duties that come with systems able to call at scale
- Study time: Approximately 1.5 hours — an estimate covering reading, activities, and the test. Students move at their own pace.
- Assessment: A 10-question test drawn only from this unit's lesson. 80% or higher passes and earns the unit certificate. Answers are not shown; your score is saved to your student record, and retakes are allowed.
- Level: Certificate Topics — Year 1 (Foundations) · Adult school · working rank on completion path: Freshman → Sophomore.
- Version: Version 1.0 — October 2026.
Minister Destiny Testimony Schools — Adult. Educational information only. Help lines: 911 for emergencies · 988 Suicide & Crisis Lifeline (call/text 988).