Voice AI security.
Your calls, your rules.

• Set temporary or longer blocks for supported caller and visitor identities. Operators can review and remove blocks. Checks can alert Live Operations. In Enforce mode, they can offer the staff phone line you have set up.
• Check what answers an outbound call. Optional detection can identify voicemail, phone menus, silence, network errors and fax tones. Set supported actions to end an attempt, record the result, stop calls to certain unreachable numbers or leave a voicemail message.

These automatic actions mainly apply to outbound calls. Detected inbound line states are recorded and alerted without ending the call. Detection can be wrong, so review important decisions.

• Review decisions in time order. Mark them correct or wrong. Check confidence settings and changes in decision patterns. Check record integrity or restore earlier protection settings.
• Check samples of AI replies. Reviews can flag missing required notices or promises the agent should not make. Live indicators, alerts and saved decisions help your team investigate.
• Review caller behaviour in context. Enabled checks can adjust to conversation risk. They assess samples, not every sentence or reply.

Protection and quality checks help your team review calls. They do not guarantee correct answers or regulatory compliance.

• Set access by organisation account, workspace, role and assignment. Invite staff and use multi-factor authentication, which adds an extra sign-in check. Recovery codes and controlled account changes support account access.
• Choose recording and data-retention settings. Retention means how long data is kept. Review available privacy exports, deletion controls and record checks. Optional bot checks for sign-in and account recovery need administrator setup and verification.
• Use the Audit log to track setting changes. See who changed a value, when, and what it was before and after. Approved administrators can filter records, export CSV and check the record chain for changes. New records are added without rewriting earlier ones. Secret values stay hidden.
• Review Help Angel sharing separately. Help questions and allowed screen content go to the platform’s chosen AI answer provider. Screen sharing is on by default and can be turned off. Visible names and notes may be included. These controls are separate from High Privacy phone-call mode.

These controls need setup and review. They are not a claim of regulatory certification.

• High Privacy is an optional mode for prepared inbound phone setups. Enable it per agent. Saloma avoids storing individual call records, transcripts, recordings and caller memory in the application. It keeps anonymous total counts instead.
• Keeping less data removes some features. Per-call reports, Smart Protection, supervision, workflows, callbacks and notifications are disabled. Knowledge lookup and supported live transfer remain available. Web Talk and browser voice tests are not available in this mode.

An administrator must enable this mode. Phone and hosting preparation must be verified first. Review provider data-retention terms. Carriers and AI providers still process audio and may keep their own records. This is not complete anonymity or zero data retention across every system. Ask our team whether this mode fits your needs.