AI Scribe Recording β Crash Recovery and New-Recording Sequencing
When a recording session ends unexpectedly, or a provider starts a new recording while the previous session is still wrapping up, Zenoti Mobile App (ZMA) applies specific recovery and sequencing behaviors to prevent data loss and ensure the new recording starts cleanly. This article explains what happens in each scenario and what providers can expect to see.
Audience: Providers who use AI Scribe to record appointment sessions on ZMA.
On this page
- Before you begin
- How crash recovery works
- How new-recording sequencing works
- Steps
- Tips
- Troubleshooting
- Related articles
Before you begin
- This article covers recording on the Zenoti Mobile App (ZMA). For recording on Zenoti Web, see Record with AI Scribe on Zenoti Web.
- Your device must meet the minimum hardware requirements:
| Platform | Minimum requirement |
|---|---|
| Android (ZMA) | 4 GB RAM or more |
| iOS (ZMA) | 4 GB RAM or more |
| Zenoti Web | View-only β recording not available |
- You must have AI Scribe access enabled for your user account. Contact your administrator if recording is unavailable.
- Crash recovery is tied to the employee who originally started the recording. If a different employee logs in to the same shared device after a crash, the recovery prompt does not appear for that employee.
Permission: You need AI Scribe access to start, recover, and manage recordings. Admin path: Configuration > AI Scribe > AI Scribe - user access
How crash recovery works
If a recording session ends abnormally β for example, the app crashes, the device restarts, or the session is terminated unexpectedly β ZMA detects the incomplete recording the next time the original provider opens the app.
The recovery flow is gated to the employee who originally started the recording. This means:
- If the same provider reopens ZMA on the same device, a recovery prompt appears so they can take action on the interrupted session.
- If a different employee opens ZMA on the same shared device, the recovery prompt does not appear. Only the original provider sees the option to recover.
This behavior protects multi-provider environments where staff share tablets: a different provider's session never interferes with another provider's incomplete recording.
How new-recording sequencing works
When a provider starts a new recording while the previous recording's post-upload cleanup is still in progress, ZMA clears the floating recording widget state before displaying the new recording card.
This clearing step β sometimes called clearing for a new recording β ensures the new recording card does not inherit any visual state from the previous session, such as a disabled or completed UI state left over from the upload that finished.
Without this step, a provider could see a recording card that appears frozen, disabled, or already complete even though they have started a new session. The clearing step prevents that.
After the floating recording widget is fully dismissed following a successful upload, the screen that hosted the widget is notified so it can clear any flags that were gating the record button. This means the record button becomes available again for the next recording without requiring the provider to navigate away and return.
Steps
Recover from a crashed recording session
- Open ZMA on the same device and with the same employee account that was active when the recording crashed.
- ZMA detects the incomplete session and displays a recovery prompt on screen.
- Review the prompt and select the appropriate option to continue or discard the incomplete recording.
Note: The recovery prompt only appears for the employee who originally started the recording. Logging in with a different employee account on the same device does not trigger the recovery flow.
Start a new recording after a recent upload
- Complete your current recording and allow ZMA to upload the session.
- Wait for the upload confirmation. The floating recording widget dismisses itself automatically after a successful upload, and the host screen clears the record button gate.
- When the record button becomes active again, select it to start a new recording for the next appointment or service.
Note: If you tap the record button before the previous session's cleanup has fully completed, ZMA clears the prior widget state automatically before opening the new recording card. You do not need to navigate away or restart the app.
Verify the record button is available after an upload
- After a successful upload, observe the floating recording widget β it dismisses on its own.
- Confirm that the record button on the host screen is no longer grayed out or disabled.
- If the button remains inactive after the widget has dismissed, navigate away from the screen and return, then attempt to start a new recording.
Worked example: A provider finishes recording a 45-minute facial service. ZMA uploads the session and the floating widget closes. The record button re-activates on the appointment screen. The provider immediately begins a second recording for the next guest without restarting the app. ZMA clears the previous widget state in the background so the second recording card opens in a clean initial state.
Tips
- Always use the same employee account on a shared device for a given appointment. Switching accounts mid-appointment prevents the crash recovery prompt from appearing for the original provider.
- If you see a recording card that looks frozen or completed when you expected a fresh session, force-close ZMA and reopen it. The sequencing cleanup runs on app restart if it did not complete in the background.
- After a crash, recover or discard the incomplete session before starting a new recording for a different appointment. Leaving an unresolved crashed session can affect how the record button behaves on that device.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Recovery prompt does not appear after a crash | A different employee account is logged in to ZMA on the shared device | Log in with the original provider's account to see the recovery prompt |
| New recording card appears disabled or shows a completed state | The previous session's upload cleanup had not finished when the new recording was started | Close and reopen ZMA; the sequencing cleanup runs on restart and the new recording card will open in a clean state |
| Record button remains grayed out after the floating widget dismisses | The host screen did not receive the cleanup callback, possibly due to a brief connectivity interruption | Navigate away from the current screen and return; the record button should re-activate |