KENYA · GUIDE 0612 · EDITION 4.7
Device setup assistance in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Help customers configure their own devices with agreed accounts, accessibility preferences, updates, recovery details, and privacy choices, leaving ownership and passwords under customer control.
The operating sequence for this offer is:
- Write a short setup checklist with the user covering the devices, settings and practical tasks included in the session.
- Let the user enter passwords and recovery information themselves while you configure only the functions they have explicitly approved.
- Have the user repeat the key tasks and provide simple notes explaining ownership of accounts and the limits of follow-up help.
Put acceptance into the job record
The customer can perform the agreed tasks and controls their own recovery details.
Ask the customer to complete basic daily tasks and locate recovery guidance independently, checking calls or connectivity, updates, essential apps, and accessibility settings they requested.
Inspect at the point where a correction is still possible, then again at handover. Record rejected or incomplete output separately from accepted output. A completed task is not automatically an accepted task, and an invoice does not establish that the customer received the right result.
Measure real capacity
Time preparation, the main operation, transport, cleaning, approvals and correction as applicable. The slowest stage determines how much you can promise. Where two orders need the same person, space or equipment at the same time, resolve the conflict before confirming both deadlines. An additional enquiry should not erase a commitment already made.
| Operating checkpoint | Evidence for this business |
|---|---|
| Before starting | Help customers configure their own devices with agreed accounts, accessibility preferences, updates, recovery details, and privacy choices, leaving ownership and passwords under customer control. |
| During delivery | Let the user enter passwords and recovery information themselves while you configure only the functions they have explicitly approved. |
| At acceptance | Ask the customer to complete basic daily tasks and locate recovery guidance independently, checking calls or connectivity, updates, essential apps, and accessibility settings they requested. |
| At the pilot review | Record customer-selected settings, account ownership, essential app tests, recovery checks, unresolved access issues, and tasks the customer demonstrated successfully before the device setup session ended. |
Keep a correction and escalation rule
When inputs, access, specifications or customer instructions change, pause the affected work and confirm the effect on time and cost. Do not quietly lower the acceptance standard to avoid a delayed delivery. Keep rework caused by your error distinct from a customer-requested change of scope and agree the remedy clearly.
Assistance becomes dependency when the helper creates accounts under their own contact details or leaves the customer unable to recover access without returning for help.
Retain the minimum records needed to investigate a complaint without disclosing unrelated personal information. Use measured delivery and actual acceptance as the basis for expanding capacity, rather than the maximum theoretical output of a tool or production line.
Operating control points for this exact offer
| Sequence | Work method | Release checkpoint |
|---|---|---|
| 1 | Check model, supportedOS and any employer management. | Do not bypass organisational restrictions. |
| 2 | Confirm backup and requested apps before changes. | No reset or deletion under a vague setup instruction. |
| 3 | Owner creates/signs in to accounts and sets recovery/MFA privately. | No recovery codes retained by operator. |
| 4 | Use official sources/licences and agreed updates. | Reject cracked installers and unrelated bundled tools. |
| 5 | Open/save sample document, print test and run approved camera/mic preview. | Owner can recover access and knows unresolved device permissions. |
Do not substitute a tick for an observation: record the count, measurement, approved sample or evidence reference used at each checkpoint. Mark unresolved work as held and identify who can approve the recheck.
Diagnose a failure before repeating it
| Observed symptom to investigate | Check the cause | Proposed response |
|---|---|---|
| App asks for missing licence | Check approved purchase. | Resolve through owner/vendor, never bypass. |
| Camera unavailable | Inspect supported permission/settings. | Test approved app without exposing private calls. |
| Employer policy blocks setup | Confirm management authority. | Refer organisation administrator. |
These are diagnostic prompts, not proof of the cause in a real incident. Separate suspect output, record any correction and repeat the relevant acceptance check. Link rejected units, rework time, replacement materials, customer credits and collection delays to the actual job result.