Getting started
BK IT sets up BK Replay together with you. Some steps take place in your organisation's Microsoft 365 environment and need an administrator with the right permissions (Global Administrator, or Privileged Role Administrator plus Teams Administrator). This page explains what happens, so you know what you are approving.
1. Consent for two apps
BK Replay consists of two apps that an administrator grants consent to once (admin consent):
| App | Purpose | Permissions |
|---|---|---|
| BK Replay Recorder | Records calls and reads Teams call data | Join and receive audio of calls of employees with a recording policy, read call data (call records and the PSTN call log), read users |
| BK Replay Portal | Sign-in to the portal and the Teams app | Sign in on behalf of the user, read your own profile, and optionally send Teams notifications |
BK IT sends you the consent links. After consent, both apps appear under Enterprise applications in the Microsoft Entra admin center.
2. Your own Azure resources
Recordings and data are stored in your own Azure subscription (see How BK Replay is set up). Your Azure administrator creates, with a guide and scripts from BK IT:
- a storage account with a container for the recordings;
- an Azure SQL database;
- an AI resource with Azure AI Speech and an Azure OpenAI model.
On each of these, the BK Replay Recorder app gets a role, and the firewall only lets BK Replay through. BK IT checks every step, with a test file, a test connection and a test question to the AI.
3. Who is recorded
Who is recorded is decided by a compliance recording policy in Teams. BK IT creates that policy together with your Teams administrator and assigns it to a group in Entra ID, for example "BK Replay recorded employees".
- Adding an employee to or removing them from that group is all it takes. Teams usually processes a change within a few hours.
- Only calls with external numbers (phone calls) are recorded; internal Teams calls are not.
- Employees see in Teams that the call is being recorded.
- To never record certain customers or numbers, use Never record.
4. Assign roles
You control who can see what in the portal yourself, with app roles on the BK Replay Portal app. Without a role nobody gets in, not even employees who are recorded. See Roles and access.
5. The Teams app
Upload the BK Replay app (which you get from BK IT) in the Teams admin center and optionally pin it in employees' app bar. See The Teams app.
6. Settings
As an administrator, go through the Settings: retention periods, languages, tailoring the summary to your organisation, and the word list with names and terms.
7. Inform your employees
Recording, and certainly assessing calls or tracking promises, affects employees. Discuss the use with your works council beforehand if you have one, and record what recordings are used for. Features where this applies carry a warning in the portal and in this documentation.
Optional features
BK IT switches these on on request:
- Meetings: BK Replay records a Teams meeting when you invite it. This needs a shared mailbox, for example
replay@yourdomain.com. See Meetings. - Telephony insight: missed calls, queues and statistics per employee. See Telephony.
- Integration with your CRM or PSA (for example Autotask): callers are recognised as contact and company, and a call can be turned into a ticket.
