Quick answer: Twilio charges $0.0025 a minute to record an AI agent’s call, once, and $0.0005 a minute for every month you store it. Up to 1 million recorded minutes a month, any recording kept longer than five months costs more to store than it did to record. At 20,000 minutes a month kept 24 months, storage settles at $240 a month against $50 of capture.
Those are Twilio’s published US and Australian list prices in US dollars, read on 24 September 2026. The same logic applies to LiveKit Cloud or your own S3 bucket: capture is billed once, storage every month, and retention multiplies it. The workings below let you substitute your own volume and retention period.
How much does it cost to record my AI agent’s calls?
An AI voice agent call can be recorded at the telephony layer (Twilio Programmable Voice recording the call leg), at the media server (LiveKit Egress writing audio to your own bucket), or in the agent platform’s observability tooling (LiveKit Cloud’s Agent Insights). Of the three, only Twilio lists a monthly rent for keeping the file on its own storage.
| Vendor and line item | Published price | How it is billed | Where the file lives |
|---|---|---|---|
| Twilio call recording (US and Australia pages) | $0.0025 / min | Once, per recorded minute | Twilio cloud unless external storage is configured |
| Twilio recording storage, first 5 million minutes | $0.00050 / min per month | Every month the minute is stored | Twilio cloud |
| Twilio recording storage, next 10 million minutes | $0.00025 / min per month | Volume band, applied automatically | Twilio cloud |
| Twilio recording storage, above 15 million minutes | $0.00015 / min per month | Volume band, applied automatically | Twilio cloud |
| Twilio transcription (optional) | $0.0500 / min | Once, per transcribed minute | n/a |
| LiveKit Agent session recordings, Ship plan | 5,000 min included, then $0.005 / min | Per recorded minute | LiveKit Cloud, 30-day retention window |
| LiveKit Agent session recordings, Scale plan | 50,000 min included, then $0.005 / min | Per recorded minute | LiveKit Cloud, 30-day retention window |
| LiveKit RoomComposite or Participant egress, audio-only, Ship plan | 600 transcode min included (shared with stream import), then $0.005 / min | Per minute the egress runs | Your own storage provider |
| LiveKit RoomComposite or Participant egress, audio-only, Scale plan | 8,000 transcode min included (shared with stream import), then $0.004 / min | Per minute the egress runs | Your own storage provider |
| LiveKit Track egress, Ship and Scale plans | 600 / 8,000 min included, then $0.001 / min | Per minute of raw single-stream export | Your own storage provider |
Twilio’s US voice pricing page and Australian voice pricing page carry identical recording figures and are both stamped “Pricing current as of August 2026”. Neither labels its currency; Twilio’s help article on funding currencies says prices display in USD, GBP or JPY “depending on the account’s currency”, with AUD on request, so we treat the figures as US dollars. The storage bands are the only volume pricing Twilio lists for recording; the $0.0025 capture rate is flat.
LiveKit’s figures come from livekit.io/pricing, whose columns are Build ($0/mo), Ship (listed as starting at $50/mo), Scale (starting at $500/mo) and Enterprise (custom). Build includes 1,000 agent session recording minutes, 60 transcode minutes and 60 Track egress minutes, with no overage rate listed. The per-minute rates apply after a plan’s included minutes are used.
Why storage outgrows capture: the five-month rule
Capture is a one-off charge. Storage is a rent. On Twilio, one recorded minute costs $0.0025 to capture and $0.0005 for each month it is stored, so its lifetime cost is:
lifetime cost per recorded minute = $0.0025 + ($0.0005 × months retained)
Set the two halves equal and the answer is five months: $0.0005 × 5 = $0.0025. The five-month rule: on Twilio’s current list prices, which show no free storage allowance, a call recording kept longer than five months has cost more to store than it cost to record, whatever your call volume, until your stored total passes 5 million minutes. Volume does not move the crossover inside the first price band, because both lines scale with the same minutes. Retention is the only lever.
That is why storage is the cost teams forget: a pilot’s storage line is measured in cents, and it only passes the capture line in month six.
How Twilio actually bills a month of recording storage
Twilio’s storage bill is not the month-end balance. Its help article “How Much Does It Cost to Record a Call?” (updated 18 August 2026) says “the daily usage metric for each account is calculated by taking the running total of storage minutes at the end of each day and dividing by the number of days in the billing month”. Its example account adds 1,000 minutes every day of September and ends with “Total September Recordings Storage usage: 15,500 minutes”, billed at $7.75.
We re-derived it: running totals of 1,000, 2,000 … 30,000 minutes sum to 465,000, and 465,000 ÷ 30 = 15,500; at $0.0005 that is $7.75. So recordings are billed for roughly half the month they are made in (15,500 of 30,000 minutes, about 52%), then at the full rate every month after. Subaccount storage is added up and charged to the parent account.
Twilio has not always billed from the first minute. Earlier versions of the same article said “Each project gets 10,000 minutes stored for free” and billed this same example at $2.75 (15,500 minus 10,000 free minutes); the archived October 2025 version shows it. The 18 August 2026 revision drops the allowance and bills all 15,500 minutes. Two Twilio help pages still point the other way: the Japanese edition of the article (updated September 2024) still describes 10,000 free minutes per project, and “How to Identify and Manage Twilio Recording Storage on Subaccounts” says “Only subaccounts with stored recordings beyond the free retention period will incur charges.” This page follows the current English article and the pricing pages, which list no allowance. If your invoice shows the first 10,000 minutes free, the per-minute crossover moves from five months to 5 + 10,000 ÷ (minutes recorded a month): 5.5 months at 20,000 a month, 10 months at 2,000. In the worked example below the allowance would take $5.00 a month off storage ($235.00 at steady state instead of $240.00) and move the cumulative crossover from month 10 to month 11; storage would still first exceed capture in month 6.
Worked example: 20,000 recorded minutes a month, kept for 24 months
The inputs: an AI agent deployment that records 20,000 minutes a month (already rounded to whole minutes, see the next section), spread evenly over 30-day months, with each day’s recordings deleted exactly 24 months after they were made. Rates are Twilio’s list prices above. The model runs day by day and applies Twilio’s daily-averaging method, so month 1 storage is 20,000 × 31 ÷ 60 = 10,333.3 billed minutes, not 20,000.
| Month | Billed storage minutes | Storage bill | Capture bill | Cumulative storage | Cumulative capture |
|---|---|---|---|---|---|
| 1 | 10,333 | $5.17 | $50.00 | $5.17 | $50.00 |
| 2 | 30,333 | $15.17 | $50.00 | $20.33 | $100.00 |
| 3 | 50,333 | $25.17 | $50.00 | $45.50 | $150.00 |
| 4 | 70,333 | $35.17 | $50.00 | $80.67 | $200.00 |
| 5 | 90,333 | $45.17 | $50.00 | $125.83 | $250.00 |
| 6 | 110,333 | $55.17 | $50.00 | $181.00 | $300.00 |
| 7 | 130,333 | $65.17 | $50.00 | $246.17 | $350.00 |
| 8 | 150,333 | $75.17 | $50.00 | $321.33 | $400.00 |
| 9 | 170,333 | $85.17 | $50.00 | $406.50 | $450.00 |
| 10 | 190,333 | $95.17 | $50.00 | $501.67 | $500.00 |
| 11 | 210,333 | $105.17 | $50.00 | $606.83 | $550.00 |
| 12 | 230,333 | $115.17 | $50.00 | $722.00 | $600.00 |
| 13 | 250,333 | $125.17 | $50.00 | $847.17 | $650.00 |
| 14 | 270,333 | $135.17 | $50.00 | $982.33 | $700.00 |
| 15 | 290,333 | $145.17 | $50.00 | $1,127.50 | $750.00 |
| 16 | 310,333 | $155.17 | $50.00 | $1,282.67 | $800.00 |
| 17 | 330,333 | $165.17 | $50.00 | $1,447.83 | $850.00 |
| 18 | 350,333 | $175.17 | $50.00 | $1,623.00 | $900.00 |
| 19 | 370,333 | $185.17 | $50.00 | $1,808.17 | $950.00 |
| 20 | 390,333 | $195.17 | $50.00 | $2,003.33 | $1,000.00 |
| 21 | 410,333 | $205.17 | $50.00 | $2,208.50 | $1,050.00 |
| 22 | 430,333 | $215.17 | $50.00 | $2,423.67 | $1,100.00 |
| 23 | 450,333 | $225.17 | $50.00 | $2,648.83 | $1,150.00 |
| 24 | 470,333 | $235.17 | $50.00 | $2,884.00 | $1,200.00 |
| 25 onward | 480,000 | $240.00 | $50.00 | +$240.00 a month | +$50.00 a month |
Read the table in three places. Month 6 is the first month the storage bill ($55.17) is larger than the capture bill ($50.00). Month 10 is when cumulative storage ($501.67) passes cumulative capture ($500.00). Month 25 is steady state: 24 months of recordings (480,000 minutes) are always on file because the oldest day is deleted as each new day is added, so storage stops growing and holds at $240.00 a month, 4.8 times the $50.00 capture bill.
Across the first 24 months the deployment pays $1,200.00 to record and $2,884.00 to store, $4,084.00 in total, of which storage is 71%. From month 25, storage is $240.00 of every $290.00 recording dollar, or 83%. If you size a voice agent’s running cost from per-minute rates alone, as in a voice AI cost-per-minute comparison of realtime and pipeline stacks, add this line separately: it is the larger of the two recording numbers and it does not scale with this month’s calls.
At what retention period does storage overtake capture?
The five-month crossover holds until your stored total reaches Twilio’s 5 million minute band edge. Above it, the cheaper bands pull the crossover later. The table reads the storage bands as graduated (the first 5 million minutes at $0.00050, the next 10 million at $0.00025, the rest at $0.00015), which is how the page’s “First … Next … Above” wording reads; the pricing page does not print a worked tiered example.
| Recorded minutes per month | Capture per month | Stored minutes at 24-month retention | Storage per month at 24-month retention | Storage ÷ capture | Storage equals capture at |
|---|---|---|---|---|---|
| 20,000 | $50 | 480,000 | $240 | 4.80 | 5 months |
| 100,000 | $250 | 2,400,000 | $1,200 | 4.80 | 5 months |
| 250,000 | $625 | 6,000,000 | $2,750 | 4.40 | 5 months |
| 500,000 | $1,250 | 12,000,000 | $4,250 | 3.40 | 5 months |
| 1,000,000 | $2,500 | 24,000,000 | $6,350 | 2.54 | 5 months |
| 2,000,000 | $5,000 | 48,000,000 | $9,950 | 1.99 | 7.5 months |
| 5,000,000 | $12,500 | 120,000,000 | $20,750 | 1.66 | 13 months |
Up to 1 million recorded minutes a month, storage catches capture at five months regardless of size, because five months of recordings still fits inside the first 5 million minute band. Even at 5 million minutes a month, two years of retention costs 1.66 times as much each month as recording does.
| Months retained | Storage over the recording’s life | Capture | Storage share of lifetime cost | Steady-state storage at 20,000 min/month |
|---|---|---|---|---|
| 1 | $0.0005 | $0.0025 | 17% | $10 / month |
| 3 | $0.0015 | $0.0025 | 38% | $30 / month |
| 5 | $0.0025 | $0.0025 | 50% | $50 / month |
| 6 | $0.0030 | $0.0025 | 55% | $60 / month |
| 12 | $0.0060 | $0.0025 | 71% | $120 / month |
| 24 | $0.0120 | $0.0025 | 83% | $240 / month |
| 36 | $0.0180 | $0.0025 | 88% | $360 / month |
| 84 (7 years) | $0.0420 | $0.0025 | 94% | $840 / month |
A recording kept for seven years costs 17 times its capture price to store ($0.0420 ÷ $0.0025 = 16.8). That is the number to put in front of whoever sets the retention policy, because the policy, not the dialler, decides most of the recording bill.
Twilio rounds every recording up to a whole minute
Twilio’s help article is explicit: “Recording storage costs are calculated by rounding the duration of each recording up to the next minute. For example, three recordings of five seconds each will count together as three minutes, not 15 seconds.” The rounding is per recording, so it bites hardest on the short calls AI outbound agents generate in bulk: voicemail drops, wrong numbers, quick “not interested” replies and callbacks that end in seconds. The article states the rule for storage; this page applies it only to storage.
| Recording length | Billed storage minutes | Billed ÷ actual |
|---|---|---|
| 0:20 | 1 | 3.00 |
| 0:45 | 1 | 1.33 |
| 1:10 | 2 | 1.71 |
| 1:30 | 2 | 1.33 |
| 2:10 | 3 | 1.38 |
| 3:05 | 4 | 1.30 |
| 5:00 | 5 | 1.00 |
So “20,000 minutes a month” should be your count of rounded recording minutes, not your talk time: a campaign of 20-second calls stores three billed minutes per minute of audio. The effect scales with attempts, not conversations. Zian AI, for example, reports 28x more contact attempts, and every recorded attempt is at least one billed storage minute for as long as it is kept. The cheapest fix is not to record calls that never reach a person, or to delete them on the day.
Does exporting recordings to S3 stop Twilio storage charges?
Twilio lets you send recordings to your own AWS S3 bucket, and its cost article says “Recording storage costs only apply to recordings stored in Twilio Cloud.” What happens to Twilio’s own copy at the moment of transfer is where Twilio’s help articles disagree. We are presenting both in Twilio’s words and not choosing between them.
Twilio’s article “Understanding and Managing Call Recording Storage Charges on Twilio” (updated 25 May 2026) says:
“When you enable external storage, new recordings are sent to your external destination (e.g., AWS S3). However, Twilio does not automatically delete the original recording from its own storage after transfer. Unless you set up an automated deletion process, these recordings will remain in Twilio and continue to incur storage charges.”
Twilio’s article “Still Being Charged for Call Recording Storage After Migrating to AWS S3” (updated 5 June 2026) says:
“If external storage is active, Twilio does not retain a copy of the media file in its own cloud.”
and, in the same article, “No temporary storage fees are incurred for recordings that are immediately transferred to S3” and “Once S3 external storage is enabled, Twilio does not retain or charge for temporary copies.”
Both articles agree on what costs the most money: recordings made before external storage was enabled stay in Twilio storage until you delete them, subaccounts can keep holding charged recordings, and the invoice CSV shows which subaccount is responsible. The first article adds that external storage must be enabled for every subaccount, that storage is billed to the parent account, and recommends a Recording Status Callback that deletes the Twilio copy after upload. The second recommends checking each Recording resource’s mediaUrl and deleting completed recordings whose media does not point at your bucket. The two sources also differ on deleted-recording metadata: the second article says it “remains for 30 days”, while Twilio’s Recording resource API reference says “Recordings metadata are kept after deletion for a retention period of 40 days.”
Whichever article describes your account, the test is the same: after a week with S3 enabled, list recordings with status completed and check where each mediaUrl points. If the Twilio storage line on your invoice is still growing, the deletion step is yours to build.
What does it cost to keep the same recordings in your own bucket?
Twilio bills storage by the minute; object storage bills by the gigabyte. To compare them you need a file size, and Twilio’s Recording API reference publishes two: “WAV files have a bitrate of 128kbps” and “MP3 files have a bitrate of 32kbps”. At 128 kbps a minute of audio is 0.96 MB; at 32 kbps it is 0.24 MB (decimal megabytes, 128,000 bits × 60 seconds ÷ 8). The 480,000 minutes held at steady state in the worked example are therefore 460.8 GB as WAV or 115.2 GB as MP3.
| Where stored | Rate | 480,000 min as 128 kbps WAV (460.8 GB) | 480,000 min as 32 kbps MP3 (115.2 GB) |
|---|---|---|---|
| Twilio recording storage | $0.0005 / min per month | $240.00 | $240.00 |
| S3 Standard, US East (N. Virginia), first 50 TB | $0.023 / GB-month | $10.60 | $2.65 |
| S3 Standard, Asia Pacific (Sydney), first 50 TB | $0.025 / GB-month | $11.52 | $2.88 |
Expressed per gigabyte, Twilio’s $0.0005 a minute is about $0.52 per GB-month for 128 kbps WAV, roughly 23 times S3 Standard in US East. This compares the storage line only: S3 request and retrieval charges are not modelled, and we have not verified which format Twilio writes to an external bucket, so both sizes are shown. Twilio’s API reference also says call and conference recordings are stored at Twilio in dual-channel format by default; if a stored WAV carries two 128 kbps channels, double the WAV column ($21.20 on S3 in US East), which is still under a tenth of Twilio’s $240.00. Long retention belongs in storage billed by the gigabyte, with a lifecycle rule that deletes on your policy date.
What does LiveKit charge to record an AI agent call?
“Is it paid to use Egress to record audio and video in the agent?” is issue #3527 on the livekit/agents tracker, and the pricing page answers it: yes, beyond each plan’s included minutes. LiveKit gives you two different recordings, and they solve different problems.
Agent session recordings are collected automatically for each agent session and include both agent and caller audio. LiveKit’s Agent Insights documentation says “All agent observability data is subject to a 30-day retention window on every LiveKit Cloud plan. Data older than 30 days is automatically deleted from LiveKit Cloud.” These are a debugging tool, not an archive; the pricing page lists “Export to cloud storage” for them as “Coming soon”. Egress writes audio to your own storage provider, where it stays until you delete it and you pay your provider’s storage rate.
| Route | Ship plan | Scale plan | Retention | Monthly storage rent from the vendor |
|---|---|---|---|---|
| Twilio call recording (for comparison) | $50.00 (flat $0.0025 / min) | Until you delete | Yes, $0.0005 / min | |
| LiveKit Agent session recordings | $75.00 (15,000 min over the 5,000 included) | $0.00 (inside 50,000 included) | 30 days, then deleted | None listed |
| LiveKit RoomComposite or Participant egress, audio-only | $97.00 (19,400 min at $0.005) | $48.00 (12,000 min at $0.004) | Your bucket, your policy | No; your provider bills |
| LiveKit Track egress, one track per call | $19.40 (19,400 min at $0.001) | $12.00 (12,000 min at $0.001) | Your bucket, your policy | No; your provider bills |
| LiveKit Track egress, caller and agent as two tracks | $39.40 (39,400 min at $0.001) | $32.00 (32,000 min at $0.001) | Your bucket, your policy | No; your provider bills |
These figures assume the included minutes are not already used by other work (RoomComposite transcode minutes are shared with stream import). The two-track row is our reading of “Raw single stream exports”: capturing both sides as separate raw tracks is two exports. On LiveKit the recurring storage cost moves to your cloud bill, but the capture price per minute is higher than Twilio’s on every route except Track egress.
Which recording route fits which retention period?
| If you need recordings for | Suggested route | Why |
|---|---|---|
| Under 30 days, debugging and QA only | LiveKit Agent session recordings, or Twilio with deletion inside the month | LiveKit deletes after 30 days; one month of Twilio storage is $0.0005 / min, 17% of lifetime cost |
| 1 to 5 months | Twilio recording kept in Twilio storage | Storage stays at or below the $0.0025 capture cost; no bucket or lifecycle rule to run |
| More than 5 months | Any capture route, then your own bucket with a lifecycle deletion rule | Twilio storage exceeds capture after month 5 and reaches 4.8 times capture at 24 months |
| Years (regulated retention) | Own bucket, verified deletion of any Twilio copy | Seven years on Twilio storage is 16.8 times the capture price per minute |
How long do I actually have to keep AI call recordings?
This page is about the cost of whatever retention period you choose; the legal minimums and maximums are covered in our guides to call recording laws in Australia for AI agents and to recording, retention and deletion in regulated industries. One point belongs here because it changes the arithmetic. Under Australian Privacy Principle 11.2 (Privacy Act 1988, Schedule 1), as published by the Office of the Australian Information Commissioner, if an APP entity holds personal information about an individual, no longer needs it for any purpose for which it may be used or disclosed by the entity under the Schedule, the information is not in a Commonwealth record, and the entity is not required by or under an Australian law, or a court/tribunal order, to retain it, then “the entity must take such steps as are reasonable in the circumstances to destroy the information or to ensure that the information is de-identified.”
For an organisation that APP 11.2 binds, “keep everything forever” is not a free default that only costs money; the retention period should be a decision with a reason attached. If you keep transcripts as well as audio, the separate question of whether the transcript is a faithful record is covered in our guide to whether an AI call transcript is a record of what was said.
How to cut the recording bill without losing the recordings you need
- Write the retention period down first. The retention-period table above prices it: at 20,000 minutes a month, each extra month on Twilio storage adds $10 a month to the steady-state bill.
- Stop recording calls that never reach a person. Rounding makes a 20-second voicemail drop one full billed storage minute; skipping those recordings removes the whole minute.
- Delete on a schedule, in code. Twilio recommends a Recording Status Callback that deletes the Twilio copy after a successful upload; the same hook can enforce your retention period.
- Audit every subaccount. Twilio’s storage-charges article says to enable external storage for every subaccount that creates recordings, and both articles say older recordings stay in Twilio storage until deleted.
- Check the invoice CSV monthly. Twilio’s articles point to the invoice CSV to see which subaccount is generating storage charges.
- For long retention, move the audio to a bucket with a lifecycle rule. At 480,000 stored minutes the difference is $240.00 a month on Twilio against $10.60 on S3 Standard in US East for 128 kbps WAV.
What this costs to run yourself: a callback handler, a scheduled job that lists and deletes recordings, an S3 bucket with a lifecycle policy, and someone who checks the invoice line each month. The failure mode is quiet: a subaccount created later without external storage, or a deletion job that stops, and the storage line resumes its climb at $0.0005 a minute. If you are evaluating an agent platform, Zian AI included, ask which layer records the call, whose storage the file lands in, and who deletes it on your retention date. Zian AI’s own stack is described on its features and integrations page.
Frequently asked questions
How much does Twilio charge to record a call?
Twilio’s US and Australian voice pricing pages both list call recording at $0.0025 per minute, storage at $0.0005 per minute per month, and optional transcription at $0.0500 per minute, read on 24 September 2026. Storage is banded: $0.00050 per minute for the first 5 million minutes, $0.00025 for the next 10 million and $0.00015 above 15 million.
Is Twilio call recording storage free?
No free storage allowance appears on Twilio’s US or Australian voice pricing pages, and the worked example in Twilio’s current help article bills all 15,500 storage minutes at $7.75 with nothing deducted. Older versions of that article gave each project 10,000 free storage minutes, and some Twilio help pages still mention a free allowance, so check your own invoice. Storage is calculated as a daily average, so recordings made mid-month are billed for roughly half that month. Twilio notes that call recording is included with paid Twilio Flex plans at no additional cost, but that recording storage fees still apply.
Why am I still being charged for Twilio recording storage after moving to S3?
Twilio gives two answers in two help articles. One says Twilio does not automatically delete the original recording after transfer, so you must delete it yourself. The other says Twilio does not retain a copy once external storage is active. Both say recordings made before S3 was enabled stay in Twilio storage until you delete them.
Does Twilio round recording storage up to the nearest minute?
Yes. Twilio’s help article says storage is calculated by rounding the duration of each recording up to the next minute, so three five-second recordings count as three minutes, not 15 seconds. A 20-second call is billed as one full storage minute every month it is kept.
Is it paid to use LiveKit Egress to record an agent call?
Yes, beyond the included minutes. On the Ship plan, audio-only RoomComposite or Participant egress includes 600 minutes and then costs $0.005 per minute; on Scale it includes 8,000 and then costs $0.004. Track egress is $0.001 per minute after 600 or 8,000 included minutes. Storage is billed by your own cloud provider.
How long does LiveKit keep agent session recordings?
LiveKit’s Agent Insights documentation says all agent observability data is subject to a 30-day retention window on every LiveKit Cloud plan and is deleted automatically after 30 days. For longer retention, record with Egress to your own storage.
When does storing call recordings cost more than recording them?
On Twilio list prices, after five months. Storage at $0.0005 per minute per month equals the $0.0025 capture price at month five, whatever your volume, until your stored total passes 5 million minutes. At 2 million recorded minutes a month the crossover moves to 7.5 months, and at 5 million to 13 months.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| Recording $0.0025/min; storage $0.0005/min per month; transcription $0.0500/min; storage bands $0.00050 / $0.00025 / $0.00015 at 5M and 15M minutes (US) | Twilio | twilio.com/en-us/voice/pricing/us | 24 September 2026 (page stamped August 2026) |
| Same recording, storage and band figures (Australia) | Twilio | twilio.com/en-us/voice/pricing/au | 24 September 2026 (page stamped August 2026) |
| Prices displayed in USD, GBP or JPY by account currency; AUD on request | Twilio | Twilio help 223183288 | 24 September 2026 |
| Whole-minute rounding; daily-averaging method; 1,000 min/day example giving 15,500 minutes and $7.75; Flex recording included but storage fees apply | Twilio | Twilio help 223132527 | 24 September 2026 (article updated 18 August 2026) |
| Earlier text: “Each project gets 10,000 minutes stored for free”; same 15,500-minute example billed at $2.75 | Twilio (archived copy of help 223132527) | Internet Archive, 2 October 2025 | 24 September 2026 |
| Japanese edition: 10,000 free storage minutes per project | Twilio | Twilio help 16175046009115 | 24 September 2026 (article updated 16 September 2024) |
| “Only subaccounts with stored recordings beyond the free retention period will incur charges.” | Twilio | Twilio help 51033836302107 | 24 September 2026 (article updated 12 June 2026) |
| Twilio does not automatically delete the original after transfer | Twilio | Twilio help 50491942871707 | 24 September 2026 (article updated 25 May 2026) |
| Twilio does not retain a copy once external storage is active; no temporary storage fees; deleted metadata remains 30 days | Twilio | Twilio help 50492237424411 | 24 September 2026 (article updated 5 June 2026) |
| WAV 128 kbps; MP3 32 kbps; deleted metadata kept 40 days; dual-channel storage by default | Twilio | Twilio Recording resource API reference | 24 September 2026 |
| LiveKit plan prices; agent session recording, RoomComposite and Participant egress (transcode) and Track egress included minutes and overage rates; “Export to cloud storage: Coming soon” | LiveKit | livekit.io/pricing | 24 September 2026 |
| 30-day retention window for agent observability data | LiveKit | LiveKit Agent Insights docs | 24 September 2026 |
| S3 Standard first 50 TB: $0.023/GB-month US East (N. Virginia), $0.025/GB-month Asia Pacific (Sydney) | Amazon Web Services | aws.amazon.com/s3/pricing (read from the USD pricing data file that page loads) | 24 September 2026 |
| APP 11.2 text | Office of the Australian Information Commissioner | Read the Australian Privacy Principles | 24 September 2026 |
| Issue title “Is it paid to use Egress to record audio and video in the agent?” | livekit/agents on GitHub | livekit/agents #3527 | 24 September 2026 |
| 28x more contact attempts | Zian AI (first-party) | zian.ai | 24 September 2026 |
| All worked-example, threshold, rounding and S3 cost figures (derived) | Zian AI calculation from the rows above | This page | 24 September 2026 |
Zian AI builds autonomous phone, SMS, email and WhatsApp sales agents and is in partnership-application beta. If you are planning an agent deployment and want the recording, storage and retention decisions made up front rather than discovered on an invoice, Apply For Partnership.