ZenotiHelp

AI Scribe Recording β€” Resilient AAC Recorder (iOS)

ZTZenoti Docs Team Updated October 14, 2026 6 min readGuide

When your organization enables the resilient recorder path for iOS, Zenoti Mobile App (ZMA) uses an alternative audio recording engine that provides enhanced disk-write failure detection. This article explains what changes when the resilient recorder is active, how providers experience the feature during a session, and how to confirm everything is working as expected.

Audience: Providers who record AI Scribe sessions on iOS devices, and organization administrators who manage AI Scribe settings.


On this page


Before you begin

  • Your organization must have AI Scribe enabled. Contact your administrator to confirm that AI Scribe access has been granted for your employee profile.
  • The resilient recorder path requires an iOS device with at least 4 GB RAM.
  • The organization-level setting that activates the resilient recorder for iOS must be enabled by your administrator. Until that setting is on, ZMA uses the standard recorder on iOS.
  • This article covers recording on the Zenoti Mobile App (ZMA). For recording on Zenoti Web, see Record with AI Scribe on Zenoti Web.

Permission: You need AI Scribe recording access enabled for your employee profile to start a session. Your administrator manages this at Configuration > AI Scribe.


How the resilient recorder is activated

The recorder ZMA uses is determined once, at the moment you start a new recording. If your organization's resilient recorder setting is on when you tap to begin, ZMA uses the resilient recorder for that entire session. If the setting is off, ZMA uses the standard recorder.

Important: A change to the organization setting while a recording is already in progress does not switch the recorder mid-session. The recorder selected at session start remains active until the recording ends.

This means your organization can enable or disable the setting at any time without affecting sessions that are currently running.

Device requirements

The table below shows platform support for AI Scribe recording.

Feature Android (ZMA) iOS (ZMA) Zenoti Web
Start a recording Yes β€” 4 GB RAM or more Yes β€” 4 GB RAM or more No β€” view only
Resilient AAC recorder Not applicable Yes β€” when the org setting is on Not applicable
View AI Scribe notes and insights Yes Yes Yes

What changes during a recording session

When the resilient recorder path is active, the recording process looks and feels the same as a standard recording session. Providers follow the same steps:

  1. Open the appointment in ZMA.
  2. Select the correct service before starting the recording. For appointments with multiple services, record each service separately.
  3. Tap to start the AI Scribe recording.
  4. Obtain recording consent as required. Consent is collected once per appointment β€” not once per recording.
  5. Conduct the session normally.
  6. Tap to stop the recording when the service is complete.

The resilient recorder uses an ADTS/AAC audio format path internally. This is an implementation detail that does not affect how you interact with the recording controls, how the audio sounds, or how AI Scribe generates insights after the session ends.

Note: Recording caps apply regardless of which recorder is active. A single recording session has a maximum length of 1 hour 35 minutes (95 minutes). ZMA displays alerts at 10 minutes, 5 minutes, and 1 minute remaining. The cumulative recording time across all recordings for the same service is capped at 3 hours.


Disk-write failure warnings

The primary behavioral difference introduced by the resilient recorder is active monitoring for disk-write failures. On iOS, it is possible for a recording to appear active β€” the timer is running β€” while audio is not actually being written to the device. Without the resilient recorder, this condition is silent and can result in an empty file when the session ends.

When the resilient recorder detects 100 consecutive disk-write failures (approximately 2.3 seconds of continuous failure), ZMA displays a visible warning to the provider. This warning surfaces the problem in real time so you can take action rather than discovering an empty recording after the appointment.

What to do when you see a disk-write failure warning:

  1. Note the warning immediately β€” do not dismiss it without reading it.
  2. Check that the device has available storage. A full device is a common cause of write failures.
  3. If possible, stop the current recording and free up storage before restarting.
  4. If the issue persists, escalate to your organization's administrator. The recording file may be empty or incomplete.

Important: A disk-write failure warning means audio may not have been saved. Do not assume the recording is recoverable without confirming with your administrator.

Worked example

A provider is mid-session on an iOS device with low available storage. The resilient recorder detects 100 consecutive disk-write failures β€” roughly 2.3 seconds of uninterrupted failure β€” and displays a warning banner on the ZMA recording screen. The provider sees the banner, stops the recording, and checks available storage. The device has less than 500 MB free. After deleting unneeded files and restarting the recording, the session proceeds without further failures.


Call interruption handling

When a phone call or other audio interruption occurs on an iOS device during a recording, ZMA handles the interruption using the same flow whether the resilient recorder or the standard recorder is active. This means:

  • Providers experience consistent behavior on call interruption regardless of which recorder path is in use.
  • The interruption is processed and surfaced to the provider in the same way across both recorder types.
  • No additional steps are required from the provider to handle an interruption when the resilient recorder is active.

Tips

  • Confirm storage before long sessions. The disk-write failure detection activates after roughly 2.3 seconds of consecutive failures. Checking available storage on the iOS device before beginning a recording reduces the chance of hitting this threshold.
  • One recorder per session. Because the recorder is selected at session start, you do not need to adjust any settings during a session. If the organization setting changes between sessions, the next new recording automatically uses the updated recorder path.
  • Multi-service appointments β€” record services separately. For appointments that include more than one service, select the correct service before starting each recording. AI Scribe ties insights to the service selected at recording start. Recording both services under one recording or under the wrong service produces mismatched insights.
  • Contact your administrator if you see repeated warnings. A single disk-write warning may be a transient storage issue, but repeated warnings across sessions indicate a device configuration problem that an administrator should investigate.

Troubleshooting

The recording timer is running but I saw a disk-write failure warning.

The warning means ZMA detected 100 or more consecutive failures writing audio to the device β€” approximately 2.3 seconds of continuous write failure. The recording may be empty or incomplete. Stop the recording, check available device storage, free space if needed, and attempt a new recording. Notify your administrator if the problem recurs.

I did not see any warning, but the recording file appears empty after the session.

If the standard recorder path is active (the resilient recorder org setting was off when you started), ZMA does not display disk-write failure warnings. An empty file in this situation indicates a storage or device problem that was not surfaced in real time. Ask your administrator to confirm whether the resilient recorder setting is enabled for your organization, and report the empty file so they can investigate.

A phone call interrupted my recording. Did the interruption affect whether the resilient or standard recorder was active?

No. Call interruptions are handled by the same interruption flow regardless of which recorder is active. The recorder that was selected at session start continues to apply after the interruption is resolved.

The organization setting was turned on mid-session. Will my current recording switch to the resilient recorder?

No. The recorder is resolved once at recording start and does not change during an active session. Your in-progress recording continues using whichever recorder was selected when you tapped to begin. The new setting takes effect for the next recording you start after the current one ends.

My device meets the 4 GB RAM requirement but I am not seeing the resilient recorder behavior.

Confirm with your administrator that the organization-level setting for the resilient recorder on iOS is enabled. Without that setting, ZMA always uses the standard recorder on iOS regardless of device capabilities.


Was this article helpful?
Your feedback helps us improve our documentation.