# Production guide — Employee phones and mobile CRM

**Manuscript:** [Put the business line on an employee’s phone](../appmint-mobile-employee-phones-and-crm.md). **State:** setup and native readiness stills exist. No finished companion video, real call, SMS delivery or saved number assignment is available from this review.

## Local review update — 24 September 2026

Use the current manuscript preflight and revocation checkpoints. The roles course now proves accepted colleagues and separate restricted sessions; the mobile welcome course proves ordinary local Android sign-in and Notes/Studio readback with score50 preserved. Do not repeat the old claims that these prerequisite defects are unresolved.

No new phone footage was captured in this pass. Authenticated local reads returned zero company phone records and zero owner-assigned lines. Assignment, From selection, connected calls, background/locked reception, SMS and actual revocation remain missing. Do not reuse generic login or CRM footage as evidence of those phone results. [Review and remaining resources](../../application-fixes/employee-phone-local-review.md).


## The story to film

The business line reaches the right employee, who records the customer’s preference afterwards. Explain the three dependencies with the original [readiness graphic](../assets/appmint-phones/phone-readiness.svg): company service, number assignment, handset registration. SMS is a fourth, separate setup.

Do not imply that installing an app buys a line, that adding a personal number forwards calls, or that a green registration dot proves the phone rings while locked. The finished result needs two-way audio on a controlled call and the expected caller ID on the receiving handset.

## What is available now

| Asset | What it establishes |
| --- | --- |
| [01 Phone Management](../assets/appmint-phones/01-phone-management.png) | Production training organisation before setup: zero numbers and Not set up. |
| [02 Service terms](../assets/appmint-phones/02-phone-service-terms.png) | The actual confirmation dialog was opened. It was cancelled, not accepted. |
| [03 Add Existing Phone](../assets/appmint-phones/03-add-existing-phone.png) | Form fields for an owned number. No number was added. |
| [10 Microphone](../assets/appmint-phones/10-android-microphone.png) | Native Android microphone request. |
| [11 Phone permission](../assets/appmint-phones/11-android-phone-permission.png) | Native make/manage-calls request. |
| [12 No assigned line](../assets/appmint-phones/12-native-no-number.png) | Real native Phone tabs and no-number guidance. |
| [13 Recent](../assets/appmint-phones/13-native-recent.png) | Native Recent screen before any training call. |
| [14 Contacts](../assets/appmint-phones/14-native-contacts.png) | Native Contacts screen, not proof of a dialled call. |
| [15 Explicit offline](../assets/appmint-phones/15-native-offline.png) | The user selected offline; the toast and red status are visible. |
| [16 Offline after restart](../assets/appmint-phones/16-offline-after-restart.png) | Reopened native Phone still exposes Go online, confirming the explicit choice persisted. |

Native images are from the current-source local Android release in an API36 emulator using organisation `learnmu4qn1ha`. Desktop setup images are production Studio0.6.1, organisation `learnmu4zs1td`. They illustrate two environments; they are not one end-to-end registered phone system. Keep that distinction visible until the full capture is made on a single company setup.

The [capture ledger](../assets/appmint-phones/evidence.json) preserves screen text and timestamps. It intentionally excludes the unrelated provider call/message rows that appeared in desktop tabs. Do not recover or republish those rows.

## Prepare the actual call shoot

Use a training company, an authorised company administrator, an active employee account, a provider-owned business line, an Android phone, an iPhone and a second controlled destination phone. Obtain the company’s authorisation for provider terms and number provisioning separately from the act of recording a tutorial. Do not use a fictional555 number, third-party customer, or a made-up email for invitation delivery.

Before recording, verify:

1. The public mobile release downloads and installs. A local source build does not prove the public install path works.
2. The employee can sign in ordinarily with the intended company account and effective access.
3. Company calling reads On after reload.
4. The business number appears in Numbers and the intended assignment persists after reopening the drawer.
5. The employee sees that number in From.
6. The test recipient is expecting the call and agrees to the recording.

Do not seed a fake phone row to obtain an assignment screenshot and then edit in footage of an unrelated working line. A screen-only assignment demonstration must be labelled as such.

## Suggested chapter sequence

| Chapter | Capture sequence | Narration purpose |
| --- | --- | --- |
| 1 · The result | Actual answered call, matching business caller ID and two-way audio | “The customer calls the business. The colleague answers in Appmint Mobile.” Record this only after the full test succeeds. |
| 2 · Three jobs | Readiness graphic → Numbers screen | Distinguish company, line and handset. |
| 3 · Company setup | Set up calling → authorised confirmation → persisted On | Explain the organisational action. Do not use the current cancelled dialog as a completed setup. |
| 4 · Add and assign | Owned number → friendly name → Numbers → Assign to User/Group → Users → Save Assignments → reopen | Show the email identity and persisted selection. |
| 5 · Native readiness | Normal employee login → centre Phone button → Android prompts → From | Say why each permission matters. Record iPhone separately with its real prompts. |
| 6 · Outbound | Select From → type controlled destination → ring → answer → audio → end → Recent | Show both phones; preserve the actual timing. |
| 7 · Inbound | Call the business line with app foreground, background and locked | Three distinct acceptance checks; do not reuse one ringing clip for all three states. |
| 8 · Customer context | Open training lead → Notes → Save → reopen → desktop readback | A call log is not a lead note or an assigned task. Keep the known metadata-save warning. |
| 9 · End shift | Go offline → restart → Phone still offline → deliberate Go online | Explain the persistent choice. Existing15/16 support the offline part, not renewed successful registration. |
| 10 · Team and SMS | Group assignment, membership check, SMS requirements and sender choice | Keep these branches separate from the first individual voice call. |

Use chapter timings after a rehearsal with the actual provider/device setup. The aim is a clear12–15minute core lesson, with SMS and offboarding as optional chapters; this is an editorial target, not the duration of existing footage.

## Call acceptance sheet

Record a row for each physical device and app build:

| Check | Evidence to retain |
| --- | --- |
| Outbound caller ID | Destination handset displays the intended business number. |
| Audio | Each participant says and hears a short agreed test sentence. |
| Mute and speaker | Actual state change and audible result, without playing confidential audio. |
| Foreground incoming | Incoming call on the employee’s phone while app is open. |
| Background incoming | Incoming call after leaving the app. |
| Locked incoming | Incoming call with the screen locked, then answer. |
| Recent | The specific call time/direction/destination appears on the employee’s phone. |
| Desktop Call Logs | The matching call appears and company scoping is verified. The review found a scoping concern, so this check is not optional. |
| Offline | The deliberate choice survives restart; the controlled incoming test does not ring that handset. |
| Re-enabled | Go online restores a tested incoming path. |
| Removal | After direct and group access are removed, the colleague no longer receives or selects the line as expected. |

A missing result remains an open result. Do not turn an unanswered call into a connected call through editing, put a timer over a screenshot, or use stock phone footage as evidence of Appmint behaviour.

## SMS capture branch

Record the form only with company-approved real details. Explain Business information, address, authorised representative, campaign and keyword sections. Do not submit placeholder legal identifiers or say a form’s sample opt-in text is the company’s actual process.

Capture submission and approval as separate events if the provider processes them asynchronously. Record capability, registration state, selected SMS sender and an agreed test message delivery before adding customer-reminder claims. A voice-call success cannot fill the missing SMS demonstration.

## Editing and privacy

Retain original stills and raw captures. Add explanatory arrows and numbered callouts in a separate overlay. On portrait native screens, enlarge the relevant area without hiding the app state or error. On the call shoot, use numbers expressly set aside for the recording, or consistently mask them while leaving enough matching digits to demonstrate identity.

Hide passwords, one-time codes, provider secrets, access tokens, private notifications and unrelated contacts. Keep the older provider records observed in desktop logs completely out of public assets. Do not submit support tickets or publish these materials as part of capture preparation.

## Remaining publication gates

Public Android installation; iPhone native screens; accepted employee invitation; configured company service; real owned number; saved direct/group assignment; Android calling-account state; full inbound/outbound/background/locked audio tests; log scoping; SMS registration/delivery; offboarding; metadata-preserving lead edit. The current manuscript deliberately states these limits. Replace them with completed instructions only after the corresponding result is captured and read back.

## Offboarding evidence boundary

Eight source-method contract checks passed for direct/group assignment, deduplication, membership removal and preservation of another employee’s group access. They also prove that legacy user `phones` and group `sharedPhones` are independent grants. These are synthetic repository tests, not handset footage. Film the actual removed employee’s From list and controlled incoming call only after all relevant access routes are removed; retain another colleague’s access as the comparison. Nineteen account lock/customer-token regressions also pass, but do not substitute those for provider registration revocation.