The short answer
Compare call recording and retention capabilities by writing your own retention policy first and then checking each vendor against it. The policy answers five questions: which calls are recorded, why each type is kept, how long, who can listen, and how recordings are exported and deleted. The vendor comparison is then a matter of asking whether a system can do what your policy says.
Most businesses do it backward. They turn on recording because the phone system offers it, keep everything forever because nobody decided otherwise, and discover the gaps when a dispute, a subpoena or a departing employee forces the question.
As of October 2026, recording is a standard feature in business phone systems and AI receptionists, and transcription has made recordings searchable in a way they never were before. That makes recordings more useful. It also raises the stakes, because a searchable archive of every customer conversation is a serious thing to be holding, especially for a business in a regulated trade or one that handles payments by phone.
This guide is a retention policy guide. It covers what to keep and why, how to think about duration without pretending there is one right number, who should have access, storage and export, deletion, payment card details, and a checklist for comparing vendors. It is written for owners of service businesses, including those in licensed and regulated trades.
Two cautions. First, this is general information and not legal advice. Recording and retention rules vary by state and by industry, and you should confirm your policy with an attorney. Second, this article makes no claims about specific retention periods or redaction features in Run with Jarvis. On that platform, call recording with playback and AI transcription are Pro plan features, and how long recordings are retained and what controls exist are questions to raise on a demo.
Consent comes before retention
A retention policy governs recordings you were allowed to make. So the first question is whether you are recording lawfully at all.
Recording laws differ by state. Some states allow recording when one party to the call consents. Others require every party to consent. Calls that cross state lines add another layer. Most businesses handle this with a clear disclosure at the start of the call, but the wording and the method matter.
That subject has its own guide: call recording consent and compliance for service businesses covers disclosure, state differences and what to do when a caller objects. Read it alongside this one. Think of the two as a pair: consent decides whether a recording may exist, and call recording and retention policy decides what happens to it afterward.
The Federal Communications Commission publishes consumer-facing information on recording telephone conversations, which is a useful starting point before a conversation with your attorney.
Why keep recordings at all
Every recording you keep should have a reason. There are four good ones for a service business.
Disputes. A customer says they were quoted one price and charged another. A customer says nobody told them about the trip charge, the deposit or the cancellation fee. A customer says they never approved the extra work. The recording of the booking call, or of the call where the technician's office got approval, settles the matter quickly and usually in a way that keeps the customer.
Chargebacks. When a customer disputes a card payment with their bank, you are asked for evidence that the service was agreed to and delivered. A recording in which the customer books the job, hears the price and confirms the address is strong supporting evidence alongside the invoice and job photos. The full evidence package is described in the chargeback defense guide.
Training. New office staff learn fastest from real calls: a good booking call, a well-handled price objection, a complaint that was turned around. A small library of examples is worth more than a manual.
Quality. Reviewing a sample of calls each week tells you how the phone is really being answered, whether by people or by an AI receptionist. This requires recent calls, not old ones. The method is in the phone call quality scorecard.
There are also reasons that apply to some businesses and not others.
Regulatory or licensing requirements. Some trades and some states impose record-keeping duties that may cover communications with customers. If you hold a license, check what your licensing body expects.
Contract and insurer requirements. A commercial contract, a warranty program or your insurer may require you to retain certain records for a stated period.
Safety incidents. A call reporting a gas smell, an injury or property damage is a record you will want preserved, and possibly must preserve.
Notice what is not on the list: "just in case". Keeping everything forever with no stated purpose is not caution. It is an unmanaged liability.
Why not keep everything forever
Storage is cheap, so the instinct is to keep it all. There are real costs to that.
More data is more exposure. Recordings contain names, addresses, phone numbers, descriptions of people's homes and schedules, and sometimes payment or health details mentioned in passing. If an account is compromised, everything in the archive is in play. The less you hold, the less you can lose.
Old recordings can be demanded. In a lawsuit or investigation, records you hold may have to be produced. A business that kept ten years of calls has ten years of calls to search and hand over.
Privacy expectations are rising. A growing number of states have privacy laws that give people rights over data held about them. Whether they apply to your business depends on your size and location, which is another question for your attorney. Holding less makes any such request easier to answer.
Nobody uses old routine calls. A recording of someone booking a drain cleaning three years ago, for a job that was done, paid and never disputed, has no remaining purpose.
The principle is simple and widely accepted in data protection practice: keep what you need, for as long as you need it, and then delete it on a schedule. The Federal Trade Commission publishes plain-language data security guidance for small businesses built around the same idea.
How long: a tiered framework
There is no single correct retention period, and anyone who gives you one without knowing your state, trade, contracts and insurer is guessing. What you can do is build a structure and fill in the durations with your advisers.
The following is an example framework, not a recommendation of specific periods. The tiers are labelled short, medium and long on purpose.
Short tier: routine calls with no ongoing purpose. Wrong numbers, vendor calls, general inquiries that did not lead to a job, calls from people outside your service area. These have training and quality value for a brief window and none after. This tier should have the shortest period you are comfortable with.
Medium tier: calls tied to a booked, completed and paid job. The booking call, calls about scheduling, approval calls for additional work. These matter for as long as the job could plausibly be disputed. Think about how long a customer has to dispute a card charge, how long your warranty runs, and how long a complaint could reasonably take to surface. Set the period to cover those windows with a margin.
Long tier: calls connected to a dispute, complaint, incident or legal matter. Anything involving a chargeback, a refund demand, a damage claim, an injury, a threat of legal action or a regulatory inquiry. These should be flagged and held until the matter is fully resolved and for whatever period your attorney advises afterward.
Legal hold: outside the tiers. If you receive notice of a lawsuit, a demand letter or an investigation, or reasonably expect one, normal deletion must stop for the relevant records. Deleting evidence after you know about a dispute can cause far more trouble than the dispute itself. Your policy should say who can place a hold and how.
Training library: a deliberate exception. A small set of example calls kept for training, selected on purpose, with customer details minimized where possible. Review the library periodically and retire old examples.
How to fill in the durations:
- Ask your attorney what your state and trade require or advise.
- Ask your insurer whether your policy sets record-keeping expectations.
- Ask your payment processor how long card disputes can be raised.
- Check your own warranty terms and commercial contracts.
- Then pick the shortest period in each tier that satisfies all of those.
Write the result down in one page. A policy that exists only as a setting in a phone system is not a policy.
Who can listen
Access is where small businesses are usually loosest.
Define roles, not names. Owner, office manager, the person who handles disputes, the person who trains new staff. Those roles may listen. Everyone else may not, by default.
Limit by purpose. The trainer needs example calls, not the whole archive. The person handling a dispute needs that customer's calls. If your system allows scoping access, use it.
Separate listening from exporting. Playing a call inside the system is one thing. Downloading the audio file to a laptop or phone is another, and it is the point where control is lost. Fewer people should be able to export than to listen.
Log access where you can. A record of who played or downloaded which call discourages misuse and gives you something to check if a recording turns up where it should not.
Remove access when people leave. Add it to the offboarding checklist next to keys and the fuel card.
Be careful with live monitoring. Listening in on calls as they happen is a related capability with its own considerations for both staff and callers. How to use whisper, barge and transfer responsibly is covered in the live call coaching guide.
Tell your staff. Employees should know that calls are recorded, who can listen and why. In some places notice to employees is expected or required. In all places it is fair.
Storage, export and deletion
Three practical questions sit under any retention policy.
Where do recordings live? With the phone or AI receptionist vendor, in most cases. Ask where the data is stored, whether it is encrypted in storage and in transit, and who at the vendor can access it. You do not need to be a security expert to ask, and a vendor who cannot answer plainly has told you something.
Can you get them out? Export matters for two reasons. In a dispute you may need to hand a specific recording to a card processor, an insurer or an attorney, in a common format, with the date and numbers attached. And if you ever change vendors, you need to take the recordings you are obliged to keep with you. Ask whether export is per call, in bulk or both, and whether transcripts and call details come with the audio.
Does deletion really delete? A retention period is only real if recordings are removed at the end of it. Ask whether deletion is automatic on a schedule or manual, whether it covers transcripts and summaries as well as audio, whether backups are also purged and how long that takes, and whether you can delete one specific customer's recordings on request.
Transcripts are records too. AI transcription turns a recording into searchable text. That text carries the same personal details as the audio and should follow the same retention tier. A policy that deletes audio and leaves the transcript has not deleted the call.
Copies escape. The recording emailed to a technician, saved to a desktop or forwarded in a text message is outside any retention schedule. Your policy should say that recordings stay in the system and are shared by link or supervised playback wherever possible.
Payment card details
Card numbers deserve their own section because the consequences of getting this wrong are specific.
The best control is not to take cards by voice. If the customer never reads a card number aloud, there is nothing to redact. Send a payment link by text or email and let the customer enter the card on a secure page. On Run with Jarvis, invoicing with three payment providers is part of Core, so payment by link is available without building anything.
If cards are read aloud, find out what happens to that audio. Card networks set security standards for how card data may be stored, and those standards restrict keeping certain card details at all. Whether a recording that contains a spoken card number creates an obligation for you is a question for your payment processor. Ask them directly.
Common techniques exist, and you should ask about them. Some systems pause recording during payment. Some mask or remove card digits from audio and transcripts. Some route the payment step to a separate secure channel. Ask any vendor which of these, if any, they support, and do not assume. This article makes no claim that any particular technique is available in Run with Jarvis. Raise it on a demo.
Train for the exception. Even with payment links as the rule, a customer will sometimes start reading a card number before anyone can stop them. Decide in advance what staff and the AI receptionist should say, and how that recording is flagged for handling.
The same thinking applies to other sensitive details that come up on calls: gate codes, alarm codes, where the spare key is hidden, health conditions mentioned in passing. Your policy should name them and say how they are treated.
A vendor comparison checklist
Use this table when evaluating any phone system, call tracking tool or AI receptionist. Fill in a column per vendor. The right-hand column explains why each question matters.
| Capability | Question to ask the vendor | Why it matters |
|---|---|---|
| Recording scope | Can I choose which calls are recorded, by line, direction or call type? | Not every call needs recording, and some should not be |
| Consent disclosure | Can the system play or speak a recording disclosure at the start of calls, and can I edit the wording? | Consent rules vary by state and wording matters |
| Retention periods | Can I set different retention periods for different call types, or is there one global setting? | A tiered policy needs tiered controls |
| Default retention | What happens if I set nothing? Kept indefinitely, or deleted after a default period? | Defaults become your policy if you do not choose |
| Legal hold | Can I exempt specific calls from deletion until I release them? | Disputes and litigation require preservation |
| Access roles | Can I restrict who can play recordings, and separately who can download them? | Listening and exporting carry different risks |
| Access logging | Is there a record of who played or exported each recording? | Deters misuse and supports investigations |
| Transcripts | Are transcripts retained and deleted on the same schedule as audio? | Text carries the same personal data |
| Export | Can I export one call or many, with date, numbers and transcript attached? | Needed for disputes and for changing vendors |
| Deletion | Is deletion automatic, and does it include backups? How long until it is complete? | A retention period is only real if deletion is |
| Individual deletion | Can I delete all recordings for one customer on request? | Privacy requests and goodwill |
| Card data | How are spoken card numbers handled in audio and transcripts? | Card network standards restrict storing card details |
| Storage security | Where is data stored, is it encrypted, and who at the vendor can access it? | Your recordings are only as safe as their host |
| Contract end | What happens to my recordings when I cancel? Can I take them, and when are they destroyed? | Obligations to keep or delete outlast the contract |
Score honestly. A vendor does not have to say yes to every row. You need to know which rows are no, so your policy can account for it. For example, if retention is one global setting, your tiers have to be managed by flagging and exporting the long-tier calls before the global period ends.
Get answers in writing. A verbal assurance on a sales call is not something you can rely on later. For a wider set of questions beyond recording, see the AI receptionist vendor evaluation checklist.
Where Run with Jarvis fits
To keep this guide honest about its own reference platform, here is exactly what the published plan list says and nothing more.
Pro and Elite include call recording with playback. Recording is listed as a Pro feature, and Elite includes everything in Pro.
Pro and Elite include AI transcription and lead scoring, along with sentiment and intent analysis. Transcripts make it practical to find the call you need and to review quality without listening to every minute.
Pro includes whisper, barge and transfer, which relate to live monitoring and are covered by the same access thinking as recordings.
Core includes chargeback defense, invoicing with three payment providers, and the CRM. These matter here because a recording is most useful when it sits on the same customer record as the job, the invoice and the payment.
What the plan list does not state. It does not state a retention period, a deletion schedule, access logging or a card redaction method. Those are exactly the checklist rows above, and they are the questions to bring to a demo. Ask them, and write down the answers.
Writing the policy: a one-page outline
A retention policy for a small service business fits on a page. Use these headings.
Purpose. Why you record: disputes, chargebacks, training, quality, and any legal or contractual requirement that applies to you.
Scope. Which lines and call types are recorded. Which are not.
Consent. How callers are told, in what words, and what happens if someone objects.
Tiers and periods. Short, medium, long, with a duration for each and the reasoning in a sentence.
Legal hold. Who can place one, how, and how it is released.
Access. Which roles may listen. Which may export. How access is removed.
Sensitive data. How card numbers and other sensitive details are kept out of recordings or handled when they slip in.
Storage and deletion. Where recordings live, how deletion happens, and how you verify it.
Requests. What you do when a customer asks for a copy of a call or asks you to delete their recordings.
Review. Who owns the policy and when it is next reviewed. Once a year is reasonable, and after any dispute that tested it.
Have your attorney read it. A one-page document takes little of their time and that review is what turns a sensible draft into something you can rely on. The Small Business Administration also has general resources on record-keeping for small businesses that help put call recordings in context with your other records.
Common mistakes
No policy at all. The system's default becomes the policy, and nobody knows what it is.
Keeping everything forever. More exposure, more to produce, no added benefit.
Deleting too eagerly. A blanket short period that wipes the booking call before the chargeback window closes defeats one of the main reasons to record.
Forgetting transcripts. Audio deleted, text retained.
Open access. Every user can play every call, and some can download them.
Card numbers in the archive. Taken by voice out of habit when a payment link was available.
No legal hold process. The auto-delete runs during a dispute.
Treating the vendor's answer as the policy. The vendor provides controls. The decisions are yours.
Where to start
Find out what is happening today. Is recording on? For which lines? What is the current retention setting, and who chose it? Who can listen and who can download? Most owners cannot answer all four, and finding out takes an afternoon.
Then draft the one-page policy from the outline above, with the tiers left as short, medium and long. Take it to your attorney and insurer to fill in the durations. Finally, go through the vendor checklist with your current provider and any you are considering.
Run with Jarvis plans are on the pricing page: Core $500, Pro $750 and Elite $1,200 per month, with zero setup fees, unlimited users and month-to-month terms. Call recording with playback and AI transcription are on Pro. To go through the retention questions in the checklist on a demo, get in touch.
