Understand customer conversations without losing control of sensitive information
Important business conversations happen over the telephone every day.
A customer reports a problem. A tenant raises a repair. A client gives an instruction. An employee explains a complex decision. A complaint is resolved, or a payment is discussed.
Once the call ends, your organisation may be left relying on handwritten notes, memory or an incomplete customer record.
Call recording can give you a clearer account of what was said.
Call analytics can help you understand what is happening across hundreds or thousands of conversations.
But recording calls also creates responsibilities.
Recordings may contain names, telephone numbers, financial information, health details, complaints, employee information and other sensitive data. They need to be collected for a clear reason, protected properly and retained only for as long as necessary.
Stratiis helps organisations introduce call recording and analytics as part of a controlled communications environment.
Record the conversations that matter. Protect the people involved. Turn call data into practical insight.
Why record business calls?
Organisations record calls for many different reasons.
These may include:
- Improving customer service
- Supporting employee training
- Reviewing complaints
- Resolving disputes
- Confirming customer instructions
- Maintaining accurate case records
- Meeting contractual requirements
- Supporting regulatory obligations
- Protecting employees and customers
- Reviewing call quality
- Investigating incidents
- Understanding customer demand
There is no single reason that applies to every organisation.
Before recording begins, you should be able to explain:
- Why the recording is needed
- Which calls will be recorded
- How the recording will be used
- Who will be allowed to access it
- How long it will be kept
- What happens when it is no longer required
The Information Commissioner's Office states that organisations processing personal information must identify an appropriate lawful basis and explain that basis transparently.
The technology should follow the purpose.
The purpose should not be invented simply because the technology makes recording possible.
Is your current call-recording system creating risk?
Some organisations already record calls but have little control over what happens next.
You may recognise some of these situations:
- Calls are recorded automatically, but nobody knows why
- Recordings are kept indefinitely
- Too many people can access them
- Former employees still have permissions
- Recordings are downloaded to personal computers
- Managers cannot find the call they need
- Customers are not clearly informed
- Employees do not understand how recordings are used
- Payment-card details may be captured
- Retention periods are applied inconsistently
- Recording failures are discovered only when a call is needed
- Nobody reviews whether the service is still necessary
- Different departments follow different policies
- Call analytics are used without clear governance
- AI-generated summaries are accepted without being checked
These problems can undermine the reason the recording system was introduced.
Stratiis can help you review the technical setup, access controls, storage, retention and reporting around the service.
Your organisation should involve its data protection, legal, HR and compliance advisers where appropriate.
What are call recording and call analytics?
Call recording
Call recording captures the audio from an incoming or outgoing telephone conversation.
Depending on the system, recording may be:
- Automatic
- Started manually
- Applied to selected users
- Applied to selected queues
- Applied to particular telephone numbers
- Paused during sensitive parts of a call
- Controlled through business rules
- Stored within a cloud platform
- Linked to a customer or case record
The right approach depends on the purpose of the recording.
Recording every call simply because it is easy may collect more information than the organisation needs.
Call analytics
Call analytics uses information from telephone conversations and call activity to identify patterns.
Basic analytics may include:
- Number of calls
- Call duration
- Answered calls
- Missed calls
- Queue waiting times
- Abandoned calls
- Transfer rates
- Busy periods
- User or department activity
More advanced platforms may also provide:
- Speech-to-text transcription
- Keyword identification
- Topic categorisation
- Sentiment indicators
- Conversation summaries
- Silence or interruption analysis
- Outcome tracking
- Quality scoring
- Compliance alerts
- Searchable call content
Analytics can help managers understand what is happening across a service without listening manually to every recording.
The results still need human interpretation.
A dashboard may reveal a pattern, but it does not automatically explain why that pattern exists.
What can call recording help your organisation achieve?
Improve customer service
Recordings can help managers understand the real customer experience.
They may reveal:
- Unclear explanations
- Unnecessary transfers
- Long periods of silence
- Inconsistent advice
- Difficult call journeys
- Common customer frustrations
- Missed opportunities to resolve an issue
- Processes that employees struggle to explain
This can lead to better training, clearer scripts and improved service design.
Support employee training
Training based only on hypothetical examples may not reflect the conversations employees handle every day.
With appropriate controls, selected recordings can be used to demonstrate:
- Good questioning
- Clear explanations
- Effective complaint handling
- Successful de-escalation
- Strong call control
- Appropriate empathy
- Accurate information
- Difficult situations that need coaching
Employees should understand how recordings are selected and how feedback will be provided.
The purpose should be to support improvement rather than create a culture where every conversation feels like a hidden test.
The ICO warns that worker monitoring can be intrusive and should be handled in a way that respects workers' rights and builds trust.
Resolve disputes
A recording can provide a more reliable account when a customer and employee remember a conversation differently.
It may help establish:
- What information was provided
- What the customer requested
- Whether an instruction was confirmed
- What action was promised
- Whether a warning or explanation was given
- How a complaint was handled
A recording should be considered alongside other relevant records.
It should not automatically replace judgement or investigation.
Improve case records
Employees may struggle to type detailed notes while also listening carefully to a caller.
Recording, transcription and summarisation tools may support more complete records.
They may help with:
- Call notes
- Case summaries
- Follow-up actions
- Customer instructions
- Complaint records
- Appointment information
- Internal handovers
Automatically generated notes should be checked before they are treated as an accurate business record.
Names, numbers, technical terms and context can all be misunderstood by transcription or AI systems.
Identify recurring customer issues
Call analytics may show that many customers are contacting the organisation about the same problem.
For example:
- Confusing invoices
- Appointment delays
- Login difficulties
- Repeated service outages
- Unclear application forms
- Repair-status questions
- Product problems
- Website information that is difficult to find
This insight can help the organisation fix the underlying issue rather than simply handling the same calls repeatedly.
Support quality assurance
Managers can review selected conversations against agreed service standards.
A quality review may consider:
- Accuracy
- Clarity
- Security checks
- Customer understanding
- Empathy
- Call ownership
- Complaint handling
- Required statements
- Follow-up actions
- Record keeping
The assessment should reflect the organisation's real service priorities.
A call should not be judged only on how quickly it ended.
Support compliance requirements
Some regulated or contractual environments require particular conversations or instructions to be recorded and retained.
The exact requirements depend on the organisation, sector, service and type of conversation.
Stratiis can help implement the recording technology and technical controls.
Your organisation remains responsible for confirming:
- Which rules apply
- Which calls must be recorded
- The required retention period
- Who may access the recordings
- What evidence must be available
- How requests and investigations are handled
Legal or regulatory requirements should be confirmed with qualified advisers or the appropriate regulator.
Automatic or selective call recording?
Automatic recording
Automatic recording captures every call covered by a defined rule.
It may be useful where:
- Recording is required consistently
- Employees should not decide whether to record
- The organisation needs a complete audit trail
- Calls enter through a regulated team
- Quality reviews require a reliable sample
- Disputes may arise across many call types
Automatic recording can also capture large amounts of unnecessary or sensitive information.
Storage, access, retention and payment handling need careful consideration.
Selective recording
Selective recording applies only to particular:
- Employees
- Departments
- Queues
- Telephone numbers
- Campaigns
- Call types
- Customer journeys
This can reduce the volume of information collected.
It requires clear rules so that the organisation understands what is and is not being captured.
User-controlled recording
Some platforms allow an employee to start, stop or pause recording.
This may be useful when:
- Only part of a call needs to be retained
- Sensitive information is discussed
- Recording depends on the call type
- A customer makes a specific request
User-controlled recording introduces a risk that employees may forget to activate or pause it.
Training, testing and reporting are important.
Informing callers
People should not discover unexpectedly that a conversation has been recorded.
The ICO's worker-monitoring guidance says organisations must tell callers and workers when calls are being recorded and explain why; it describes a recorded announcement as good practice.
A notification might explain that a call is recorded for purposes such as:
- Training
- Quality assurance
- Confirming instructions
- Security
- Meeting regulatory requirements
- Resolving disputes
The message should reflect what the organisation genuinely does.
A generic statement should not be used to justify unrelated future purposes.
Information may also need to be included in:
- Privacy notices
- Employee policies
- Customer terms
- Website information
- Contact-centre scripts
- Internal training
- Data-protection records
The UK GDPR's transparency requirements mean information about processing should be clear and understandable.
Do callers need to give consent?
Consent is one possible lawful basis for processing personal data, but it is not the only one.
The appropriate lawful basis depends on the reason for recording and the circumstances of the organisation. The ICO explains that no lawful basis is automatically stronger than another and that the selected basis must fit the actual processing.
Your organisation should identify and document its lawful basis before recording begins.
It should not assume that simply playing a recorded announcement creates valid consent.
Where calls may contain special-category information, such as health information, an additional condition may also be required.
Stratiis does not provide legal advice.
We can help implement the technical controls once your purpose, lawful basis and policy requirements have been established.
Recording employee calls
Recording customer calls also records the employees handling them.
This means worker privacy and employment considerations should be addressed as part of the project.
Employees should understand:
- Which calls are recorded
- Why they are recorded
- Who can listen
- How recordings are selected
- Whether recordings affect performance reviews
- How long they are retained
- How they can raise concerns
- Whether live monitoring takes place
- How analytics or AI will be used
- What happens during personal or sensitive calls
Monitoring should be necessary, proportionate and transparent.
A contact-centre platform should not be used to collect every available employee metric simply because it appears on a dashboard.
Call recording and payment-card information
Telephone payments can create additional security risks.
A recording may capture:
- Card numbers
- Expiry dates
- Security codes
- Customer names
- Billing details
PCI DSS provides security requirements for environments where payment account data is stored, processed or transmitted.
The PCI Security Standards Council has also published guidance specifically addressing telephone-based payment-card data and call-recording environments.
Depending on the payment process, possible controls may include:
- Pausing and resuming recording
- Suppressing keypad tones
- Using a secure payment platform
- Preventing employees from seeing card details
- Removing payment data from the contact centre
- Restricting recording downloads
- Applying strong access controls
- Monitoring access
- Avoiding unnecessary retention
Card verification codes must not be retained after the relevant transaction has been authorised.
The correct solution should be designed with your payment provider, acquiring bank, PCI adviser and compliance team.
Advanced analytics features
Call transcription
Call transcription converts spoken conversation into searchable text.
It may help with:
- Finding specific calls
- Producing case notes
- Identifying common topics
- Supporting accessibility
- Reviewing complaints
- Creating follow-up actions
- Reducing manual note-taking
- Quality assurance
Transcription is not always accurate.
Accuracy may be affected by:
- Scottish and regional accents
- Background noise
- Poor call quality
- Several people speaking
- Specialist terminology
- Names
- Reference numbers
- Interrupted speech
- Different languages
The transcript should not automatically be treated as a perfect record of the conversation.
The audio may remain the primary source where accuracy matters.
AI-generated call summaries
Some platforms can produce a short summary after a call.
A summary might include:
- Reason for contact
- Main points discussed
- Agreed actions
- Customer sentiment
- Follow-up requirements
- Case category
This may reduce after-call administration.
However, an AI-generated summary can:
- Miss important context
- Attribute a statement to the wrong person
- Invent an action that was not agreed
- Misunderstand a name or number
- Oversimplify a sensitive conversation
- Remove uncertainty that was present in the call
Employees should review and correct summaries before they are saved as official records or used to make decisions.
Sensitive or high-impact decisions should not rely solely on automated analysis.
Sentiment analysis
Sentiment analysis attempts to identify whether a conversation appears positive, neutral or negative.
It may help locate calls that deserve further review.
It should be treated cautiously.
Tone can be affected by:
- Accent
- Culture
- Disability
- Stress
- Communication style
- The subject of the call
- Background noise
- Sarcasm
- Language differences
A customer discussing a serious problem may sound negative even when the employee provides excellent service.
Sentiment should be used as an indicator, not a final judgement of the customer or employee.
Keyword and phrase monitoring
Analytics platforms may identify selected words or phrases.
This can support:
- Complaint identification
- Vulnerability indicators
- Cancellation requests
- Competitor mentions
- Payment discussions
- Required statements
- Escalation language
- Product issues
- Security concerns
Keyword alerts should be tested carefully.
Words can have different meanings depending on context.
An alert should prompt appropriate review rather than trigger an automatic conclusion.
Call-quality analytics
A recording and analytics service may also help investigate technical call quality.
This can include information about:
- Packet loss
- Delay
- Jitter
- Disconnected calls
- Poor audio
- Device performance
- Network conditions
- Location
- Service-provider routes
Technical analytics may help distinguish between:
- An employee-device issue
- Poor Wi-Fi
- Internet congestion
- A provider fault
- A platform problem
- A remote-worker connection
This is particularly useful when call recording is integrated with Hosted Voice, Microsoft Teams Phone or a cloud contact centre.
Call-recording storage
Recordings may be stored:
- Within the telephone platform
- In a specialist recording service
- In a contact-centre platform
- In approved cloud storage
- In an integrated customer system
- In an archive platform
Before choosing a service, you should understand:
- Where the recordings are stored
- Which country or region holds the data
- Which suppliers can access it
- Whether the data is encrypted
- How backups work
- Whether recordings are duplicated
- How deletion is applied
- How data is recovered
- Whether recordings can be downloaded
- What happens when the contract ends
Where a supplier processes recordings on your behalf, appropriate contractual and security arrangements are required. The ICO notes that UK GDPR Article 28 imposes requirements on controller–processor relationships, including written terms and processing on documented instructions.
Encryption and security
Call recordings may contain enough information to support identity fraud, social engineering, reputational harm or unauthorised disclosure.
Security controls may include:
- Encryption in transit
- Encryption at rest
- Multi-factor authentication
- Role-based access
- Separate administrator accounts
- Restricted downloads
- Access logging
- Regular permission reviews
- Secure sharing
- Retention controls
- Alerting for unusual activity
- Device security
- Data-loss prevention
- Supplier security reviews
- Tested incident-response procedures
The organisation should know when a recording is played, downloaded, shared, deleted, exported or used in a quality review.
Access should be limited to people who have a genuine business need.
Role-based access
Not everyone needs the same permissions.
A practical access model might include:
Employees
Employees may access only their own recent calls where required for case work.
Team leaders
Team leaders may access recordings for their assigned team and approved quality reviews.
Compliance teams
Compliance employees may access defined recordings for investigation or regulatory work.
System administrators
Administrators may manage the platform without routinely listening to call content.
Senior managers
Senior managers may receive reports and trends without unrestricted access to every recording.
Access should be reviewed when an employee joins, changes role, moves department, takes extended leave or leaves the organisation.
Permissions should not remain in place simply because they were granted years ago.
Recording retention
Keeping recordings forever may feel safer, but it creates more cost and risk.
Retention should reflect:
- The purpose of recording
- Legal or regulatory requirements
- Contractual requirements
- Complaint timescales
- Customer expectations
- Employment considerations
- Storage costs
- Security risk
- Data-subject rights
- Ongoing business need
Different call types may require different retention periods.
For example, a regulated instruction may need to be kept longer than a routine customer-service enquiry.
The system should support:
- Automatic deletion
- Different policies by team or call type
- Legal or investigation holds
- Documented exceptions
- Deletion reporting
- Regular policy reviews
The retention period should be defined before implementation rather than left at the platform's default setting.
Call recording and platform integrations
Call recording and Microsoft Teams Phone
Microsoft Teams Phone can support recording through different Microsoft and third-party approaches.
The correct option depends on whether you require:
- User-initiated recording
- Automatic policy-based recording
- Regulatory recording
- Contact-centre recording
- Centralised storage
- Searchable transcripts
- Long-term retention
- Quality assurance
- Restricted employee controls
- CRM integration
A basic Teams recording feature may not meet the needs of an organisation requiring automatic or regulated capture.
Stratiis can help review the licensing, technical architecture and third-party options.
Call recording and Hosted Voice
Hosted Voice platforms may offer built-in recording or integration with a specialist recording service.
Important questions include:
- Is recording included in the licence?
- Is it automatic or manual?
- Can selected users be excluded?
- Where is the recording stored?
- How much storage is included?
- Can calls be paused?
- Who can download recordings?
- What search tools are available?
- Can retention be automated?
- Are access logs available?
- Can recordings be linked to customer records?
The recording feature should be assessed before the Hosted Voice platform is selected.
Call recording and contact centres
Contact-centre platforms commonly combine recording with:
- Call queues
- Agent activity
- Supervisor dashboards
- Quality management
- CRM integration
- Transcription
- Analytics
- Call outcomes
- Customer journeys
This creates a richer view of the conversation.
It also means the platform may hold more customer and employee data.
Access, retention, monitoring and reporting controls should be included in the contact-centre design from the beginning.
Call recording for different sectors
Housing associations
Housing associations may record calls relating to:
- Repairs
- Rent
- Complaints
- Antisocial behaviour
- Housing applications
- Support needs
- Contractor appointments
- Emergency services
Recordings may help confirm reports and improve service.
They may also capture information about health, vulnerability, family circumstances and financial difficulty.
Access and retention should reflect the sensitivity of these conversations.
Accountancy firms
Accountancy practices may use recording for:
- Client instructions
- Service reviews
- Complaint handling
- Quality assurance
- Telephone support
- Appointment information
- Training
Calls may contain confidential financial, tax, payroll or business information.
Strong access control and clear recording rules are essential.
Charities
Charities may handle calls involving:
- Support needs
- Safeguarding
- Donations
- Service access
- Vulnerable callers
- Volunteer enquiries
- Complaints
- Helplines
Recording may support service quality but can also capture extremely sensitive information.
The organisation should consider whether recording is necessary for each type of call and whether some calls should be excluded.
Professional services firms
Professional services organisations may record:
- Client instructions
- Project discussions
- Support calls
- Complaints
- Appointment arrangements
- Service confirmations
Confidentiality, professional obligations and client expectations should form part of the design.
Contact centres
Contact centres may use recording for:
- Quality monitoring
- Complaint investigation
- Employee development
- Customer protection
- Regulatory purposes
- Analytics
- Process improvement
The recording system should be integrated with employee policies, quality processes and customer-data controls.
What should you look for in a call-recording provider?
A provider that asks why you need recording
The provider should understand the purpose before recommending the technology.
Secure storage
You should know where recordings are held and how they are protected.
Flexible retention
The system should support different retention rules and automatic deletion.
Role-based access
Permissions should reflect job responsibilities.
Reliable search
Authorised users should be able to locate calls without having unrestricted access.
Access auditing
The platform should record important access, download and deletion activity.
Recording controls
You may need automatic, selective, manual or pause-and-resume recording.
Payment-security options
The provider should understand the risks of capturing card data.
Analytics that fit the purpose
Do not pay for AI and analytics features that nobody has a clear reason to use.
Integration capability
The platform may need to connect with Teams Phone, Hosted Voice, your contact centre or customer systems.
Ongoing support
You need a clear route when recordings fail, permissions need changing or a call cannot be found.
Our call-recording and analytics process
1
Discovery
We begin by understanding:
- Why calls may be recorded
- Which teams are involved
- Which calls are in scope
- Current telephone platforms
- Customer journeys
- Employee roles
- Payment processes
- Existing policies
- Retention expectations
- Reporting requirements
- Customer-system integrations
- Regulatory or contractual needs
2
Recording audit
Where recording already exists, we review:
- Recording rules
- Users and queues
- Storage
- Access permissions
- Administrator accounts
- Downloads
- Retention settings
- Recording failures
- Payment handling
- Search and retrieval
- Integrations
- Existing contracts
This can reveal uncontrolled access, inconsistent retention or recording gaps.
3
Requirements and governance design
Working with your internal advisers, we help translate the agreed policy into technical requirements.
This may include:
- Automatic or selective recording
- Caller announcements
- Employee notifications
- Access roles
- Retention periods
- Download restrictions
- Audit logging
- Payment-data handling
- Legal holds
- Deletion processes
- Quality-review workflows
- Analytics controls
4
Platform design
We recommend an appropriate solution that may include:
- Built-in Hosted Voice recording
- Microsoft Teams recording
- Contact-centre recording
- A specialist compliance platform
- Secure cloud storage
- Transcription
- Call analytics
- Quality management
- CRM integration
- Payment-protection controls
We explain the benefits, limitations and costs.
5
Configuration and security
We configure:
- Recording policies
- User groups
- Role-based permissions
- Multi-factor authentication
- Retention
- Search
- Alerts
- Access logging
- Recording announcements
- Pause-and-resume rules
- Integrations
- Reporting
6
Testing
Testing may include:
- Incoming calls
- Outgoing calls
- Internal transfers
- Queue calls
- Remote employees
- Mobile applications
- Paused recording
- Payment journeys
- Recording playback
- Permissions
- Search
- Automatic deletion
- Transcription
- Failover arrangements
7
Training
User and manager training may cover:
- When recording applies
- How callers are informed
- Pausing and resuming
- Finding recordings
- Permitted use
- Secure sharing
- Quality reviews
- Data requests
- Reporting problems
- Escalating recording failures
8
Ongoing support and review
Stratiis can continue to support:
- User changes
- Permission reviews
- Retention updates
- Recording failures
- Platform changes
- Licence reviews
- Reporting
- Analytics configuration
- Security reviews
- Supplier coordination
- Compliance-led technical changes
The business purpose and configuration should be reviewed regularly.
Frequently asked questions
Is it legal to record business calls?
Call recording can be lawful, but the organisation needs a valid purpose, an appropriate lawful basis, transparency and suitable controls.
Additional rules may apply depending on the sector, information recorded, use of employee monitoring and payment handling.
Your organisation should obtain appropriate legal or data-protection advice.
Do we need consent to record calls?
Consent is one possible lawful basis, but it is not the only one.
The correct basis depends on the purpose and circumstances.
The organisation should identify and document its lawful basis before recording begins.
Do we have to tell customers calls are recorded?
Organisations should provide clear information about recording and its purpose.
This is often done through a recorded announcement and supporting privacy information.
Do employees need to know their calls are recorded?
Yes.
Employees should understand which calls are recorded, why, who can access them and how recordings or analytics may be used.
How long should call recordings be kept?
There is no single retention period for every organisation.
The period should reflect the purpose, legal or regulatory requirements, complaint timescales and ongoing business need.
Recordings should not be kept indefinitely without justification.
Can recordings be deleted automatically?
Yes.
Many platforms can apply automatic retention and deletion policies.
Different rules may be configured for different teams or call types.
Can we record only selected calls?
Yes.
Recording may be applied to specific users, queues, telephone numbers or call types, depending on the platform.
Can employees pause a recording?
Some platforms support pause-and-resume recording.
This may be useful when sensitive or payment information is discussed.
It needs careful configuration and training.
Can payment-card details be recorded?
Capturing payment-card data can create PCI DSS obligations and significant risk.
The payment process should be designed to prevent unnecessary card information from entering recordings.
Specialist advice may be required.
Can call recordings be transcribed?
Yes.
Many modern platforms provide speech-to-text transcription.
Transcripts should be checked where accuracy matters.
Can AI summarise calls?
Some platforms can generate call summaries and suggested actions.
Employees should review the output before it is stored or used as an official record.
Can recordings integrate with our CRM?
Many platforms can link recordings, transcripts or call details to customer records.
The exact capability depends on the telephone and CRM systems.
Can Stratiis record Microsoft Teams Phone calls?
Stratiis can help assess Microsoft and third-party recording options for Teams Phone.
The correct approach depends on whether recording is user-controlled, automatic, compliance-led or contact-centre based.
Can Hosted Voice calls be recorded?
Yes, many Hosted Voice systems include recording or integrate with specialist platforms.
The available storage, search, retention and security features vary.
Who should be able to listen to recordings?
Access should be limited to authorised people with a clear business reason.
Permissions may differ for employees, managers, quality teams, compliance teams and administrators.
Can a customer request a copy of a recording?
Call recordings containing identifiable information may fall within data-protection rights.
Your organisation should have a process for locating, reviewing and responding to relevant requests.
What happens if the recording system fails?
The platform should alert appropriate people when calls are not being recorded.
Your organisation should decide whether calls can continue and what alternative process employees should follow.
Can Stratiis provide the phone system as well?
Yes.
Stratiis can support Hosted Voice, Microsoft Teams Phone, contact-centre platforms, call recording, analytics and business connectivity as one joined-up communications environment.
Record calls for the right reasons and manage them responsibly
Call recording can help your organisation improve customer service, resolve disputes, support employees and create more accurate records.
It can also expose sensitive customer and employee information when it is introduced without clear rules.
The right approach brings together technology, security, people and governance.
Stratiis can help you choose and configure a recording platform that fits your Hosted Voice, Microsoft Teams Phone or contact-centre environment.
We can help control who has access, automate retention, introduce useful analytics and provide ongoing technical support.
Let's review why you record calls, what information is being captured and whether your current controls are strong enough.
This page provides general information about call-recording technology and implementation considerations. It is not legal, regulatory, employment or data-protection advice.
```
