KENYA · GUIDE 0612 · EDITION 4.2
Device setup assistance in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- Credential exposure
- Unbounded support calls
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.
A risk list is useful only when it changes a decision. For each risk, write the observable warning, who checks it and the response before the next commitment. Do not treat a reserve of money as permission to continue unsafe or unauthorized work.
Use a small, measurable pilot
Offer one fixed session covering agreed settings and a short user demonstration.
The pilot scope is: Help customers configure their own devices with agreed accounts, accessibility preferences, updates, recovery details, and privacy choices, leaving ownership and passwords under customer control.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Help customers configure their own devices with agreed accounts, accessibility preferences, updates, recovery details, and privacy choices, leaving ownership and passwords under customer control. |
| Output acceptable | 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. |
| Costs recorded | Include setup time, customer instruction, update downloads, account troubleshooting, data transfer if separately authorized, and additional support when forgotten credentials block otherwise routine configuration work. |
| Buyer response recorded | 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. |
Stage the launch around prerequisites
First confirm the buyer specification and activity requirements. Then compare suppliers, establish suitable facilities and prepare the operating record. Run the bounded trial when those prerequisites are in place. Review actual costs, quality failures and cash collected before increasing the commitment.
This sequence is not a promise that the complete business cycle fits into 30 days. Growing periods, qualifications, approvals, seasonal access and customer buying cycles can require longer. Revise the schedule when a prerequisite changes rather than skipping it to meet a launch date.
Choose continue, revise, pause or stop
Continue only when the scoped result is accepted and direct costs and payment timing are workable. Revise one part of the offer if the problem is identifiable and affordable to test again. Pause when required information, permission, skills or resources are missing. Stop the affected work when safety, consent or lawful authority is uncertain.
Keep a maximum test loss and unpaid-balance limit suited to your actual funds. A successful single delivery is useful evidence, but it does not establish year-round demand or justify committing every available resource.
Tie launch milestones to observable checks
| Risk signal | Evidence to inspect | Response to test |
|---|---|---|
| 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. |
Outstanding go / hold conditions
- Actual device, licence and ownership policies unverified.
Assign an owner, evidence reference and review date to each unresolved condition. Do not give every milestone a fixed calendar date when it depends on a crop, production, approval or competence cycle. Run only a suitable limited trial, reconcile accepted output and actual cash, and record whether the evidence supports holding, revising, proceeding within the limit or stopping.