Phone enquiries

Questions to ask before AI answers your agency's calls

Questions to ask before an AI service answers your agency's calls: data location, recording notices, escalation to staff and testing before go-live.

Ava research teamPublished 6 min read

On this page
  1. Why a checklist matters
  2. 1. Data: where it goes and who sees it
  3. 2. Notices: telling callers
  4. 3. Escalation: when a person takes over
  5. 4. Accuracy and boundaries
  6. 5. Security and breach handling
  7. 6. Testing before go-live
  8. Lettings-specific checks
  9. Who owns it inside your business
  10. 7. Contract and exit
  11. Frequently asked questions
  12. References

Key takeaways

  • Ask where call recordings and transcripts are stored, who can access them and how long they are kept.
  • Tell callers they may be speaking to an AI and that calls are recorded, and update your privacy notice.
  • Insist on clear escalation rules for offers, complaints, vulnerability and emergencies, and test them before go-live.
  • Plan for breaches: a reportable personal data breach must be notified within 72 hours where feasible[1].

Why a checklist matters

An AI service that answers your calls will hear names, addresses, phone numbers, financial positions, repair details and sometimes health information. It speaks in your branch's name, so its mistakes are your mistakes. Most agencies are small and do not have an IT or compliance team to vet suppliers, which is exactly why a written list of questions helps.

Data security is a live concern for the sector. In 2025/26, 83% of businesses in the administration or real estate sector group said cyber security was a high priority[2]. Across all UK businesses, 43% reported a breach or attack in the previous 12 months[3]. Callers are wary too: government research found strong public concern both about data not being held securely and about decisions being made without human input[4].

UK adults concerned about data and AI, 2024
UK adults concerned about data and AI, 2024Bar chart. Data will not be held securely: 92%; Important decisions made by computers without human input: 91%.Data will not be held securelyData will not be held securely: 92%92%Important decisions made by computers without human inputImportant decisions made by computers without human input: 91%91%UK adults concerned about data and AI, 2024Bar chart. Data will not be held securely: 92%; Important decisions made by computers without human input: 91%.Data will not be held securelyData will not be held securely: 92%92%Important decisions made by computerswithout human inputImportant decisions made by computers without human input: 91%91%

Source: Department for Science, Innovation and Technology (GOV.UK), 2024[4]

Show the data
ItemValue
Data will not be held securely92%
Important decisions made by computers without human input91%

1. Data: where it goes and who sees it

Data questions for an AI call answering supplier
QuestionWhy it mattersA good answer
Where are recordings, transcripts and summaries stored?UK GDPR rules on international transfersA named region, with safeguards for any transfer outside the UK
Which sub-processors handle call audio and text?You need to know the full chainA published list and notice of changes
Is call content used to train models for other customers?Confidentiality of your callersNo, or only with your explicit opt-in
How long is data kept, and can we set our own period?Storage limitationConfigurable retention and deletion on request
Who at the supplier can access recordings?Insider riskNamed roles, logged access, staff vetting
Will you sign a data processing agreement?Required where they process data for youYes, with standard terms you can review

2. Notices: telling callers

Callers have a right to know how their information is used. Update your privacy notice to cover AI call handling, recording, transcripts and where data goes. In the greeting, be open about what the caller is speaking to and that the call is recorded. A plain line works: "You're through to [branch name]. I'm the branch's AI assistant and calls are recorded. How can I help?"

  • Say it is AI in the greeting or the moment a caller asks. Never let it claim to be a person.
  • Mention recording and point to your privacy notice on the website.
  • Give a way to reach a person: "Say 'colleague' at any time to be put through or called back."
  • For outbound calls, such as viewing confirmations, present a number the person can call back. Hidden numbers are not allowed for marketing calls[5].

3. Escalation: when a person takes over

Ask the supplier to show, not just describe, how calls reach staff. Then write your own rules and have them configured.

  1. Always hand over

    Offers and negotiation, valuations, referencing decisions, holding deposits, complaints, anyone who asks for a person.

  2. Hand over urgently

    Gas smells, flooding, electrical danger, security breaches at a property, threats to safety. These go to the out-of-hours contact immediately.

  3. Hand over with care

    Callers who sound confused, distressed, bereaved or under pressure. Flag the call for a callback from an experienced colleague.

  4. Warm transfer or message

    When a colleague is free, transfer with a spoken summary; when not, a detailed message to the right person with a callback time.

Ask what happens if a transfer fails: does the caller hear ringing forever, or does the system take a message and tell them when they will be called?

4. Accuracy and boundaries

  • What does it answer from, and who keeps that information current?
  • What does it say when it does not know? The right answer is "I'll ask a colleague to confirm", not a guess.
  • Can it quote only the advertised rent and treat every rental applicant the same way?
  • Is it prevented from giving price opinions, legal advice or referencing outcomes?
  • Can you see and edit the scripts and rules yourself?
  • Can you listen live, guide it or take over a call?

5. Security and breach handling

Phishing was the most common attack on UK businesses in 2025/26, experienced by 38%[6]. Ask how the supplier protects accounts and recordings, and how it would tell you about a breach. Under UK GDPR, a personal data breach that is likely to result in a risk to people must be reported to the regulator without undue delay and, where feasible, within 72 hours of becoming aware of it[1]. If the supplier takes a week to tell you, you cannot meet that deadline.

  • Two-factor sign-in for every user of the dashboard.
  • Role-based access so a negotiator sees their branch only.
  • Encryption of recordings and transcripts at rest and in transit.
  • A written commitment to notify you of any breach within a short, stated time.
  • Audit logs you can review.

6. Testing before go-live

  1. Script your test calls

    Write 15 to 20 scenarios from your real call mix, including awkward ones: a strong accent, a bad line, a caller with two questions, an angry tenant, a gas smell.

  2. Call as different people

    Have several colleagues call. For lettings, check that each applicant hears the same rent and next step.

  3. Check every output

    Read each summary against the recording. Look for wrong numbers, misspelled names and missed urgency.

  4. Test failures

    Switch off a colleague's phone and call for them. What does the caller hear?

  5. Go live in stages

    Start with overflow and out-of-hours calls, review summaries daily for two weeks, then widen.

Lettings-specific checks

Letting agents carry extra legal duties on the phone. Test them explicitly rather than assuming the general set-up covers them.

  • Every rental applicant hears the advertised rent and nothing else, and no hint that a higher offer would help.
  • No question or answer that could put off families with children or people receiving benefits.
  • Messages from tenants about ending a tenancy, deposits or disrepair are flagged to the property manager the same day.
  • Repair calls capture access details and whether anyone vulnerable lives at the property.
  • Landlord calls about new instructions go to a person, with the property details captured.

Ask the supplier how these rules are set, who can change them and how changes are logged. If a council or the redress scheme ever asks how an applicant was treated, you will want the transcript and the rule that applied on that date.

Who owns it inside your business

Tell your team before the service goes live, too. Negotiators should know what it will say, what it will pass to them and how to listen to a call or take one over. Staff who understand the system spot its errors quickly; staff who were not told about it tend to work around it.

Name one person who owns the service: they keep the property information current, review a sample of summaries every week, handle supplier changes and decide when rules need updating. Without an owner, small errors pile up quietly. Give them an hour a week for it in the first two months, and a regular slot after that. They should also be the person staff tell when a caller complains about the phone experience.

7. Contract and exit

Read the exit terms before you start. You should be able to export your recordings, transcripts and contact records in a usable format, and have the supplier delete your data within a stated time after you leave. Check notice periods, what happens to your phone number routing if you switch, and whether there are minimum terms. Barriers such as cost and lack of expertise are among the most common reasons UK firms hold back from AI[7]; a clean exit route lowers the risk of trying.

Example (fictional): a two-branch agency trials a service on out-of-hours calls only. In week one, test calls show it reads back flat numbers wrongly ("Flat 1, 4 Station Road" becomes "14 Station Road"). The supplier changes the read-back rule, the next round passes, and the agency widens use to lunchtime overflow. The checklist did its job: it caught a small error before a real tenant's repair went to the wrong door.

For background on what these services do, see AI phone answering for estate agents and AI receptionist vs AI employee. If you are not yet registered with the regulator, read ICO registration and the data protection fee first.

Frequently asked questions

Do we need to tell callers they are speaking to AI?

Be open about it. Say so in the greeting or as soon as a caller asks, and always offer a route to a person.

Do we need a data processing agreement with the supplier?

Yes, where the supplier processes personal data on your behalf. Check retention, sub-processors and breach notification terms.

How quickly must a data breach be reported?

A reportable breach must be notified without undue delay and, where feasible, within 72 hours[1]. Your supplier must tell you fast enough for you to meet that.

What is the minimum testing before go-live?

Run scripted test calls covering your real call mix and edge cases, check every summary against the recording and start with overflow and out-of-hours calls.

References

  1. legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 33: notification of a personal data breach (opens in a new tab) ↑

  2. Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑

  3. Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑

  4. Department for Science, Innovation and Technology (GOV.UK) (2024). Public attitudes to data and AI: Tracker survey (Wave 4) report (opens in a new tab) ↑

  5. legislation.gov.uk (The National Archives) (2016). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 21 (opens in a new tab) ↑

  6. Department for Science, Innovation and Technology (GOV.UK) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑

  7. Office for National Statistics (2026). Artificial intelligence in UK businesses: 2023 to 2026 (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo