KENYA · GUIDE 0595 · EDITION 4.7
Email account setup in Kenya: Risks and Launch Plan
Set the conditions for a safe commercial test
- Account takeover
- misconfigured DNS
- lost mail
Email setup fails when messages send successfully but replies disappear into an unmonitored old inbox or the business owner lacks administrator recovery access.
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
Trial one mailbox and test sending, receiving and recovery.
The pilot scope is: Set up business email with client-owned accounts, agreed naming, administrator authority, recovery arrangements, device access, and a migration plan for existing correspondence.
| Gate | Evidence before continuing |
|---|---|
| Scope agreed | Set up business email with client-owned accounts, agreed naming, administrator authority, recovery arrangements, device access, and a migration plan for existing correspondence. |
| Output acceptable | Ask each user to send and receive test messages, verify identity details, and access recovery guidance, checking shared mailboxes separately from individual accounts. |
| Costs recorded | Include account creation, domain coordination, device configuration, migration where agreed, security settings, training, and support for legacy addresses used by customers already. |
| Buyer response recorded | Record account ownership, aliases, delivery tests, migrated material, user-device checks, recovery contacts, and unresolved forwarding or shared-mailbox questions before final handover. |
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 |
|---|---|---|
| One user stops receiving | Check mailbox exists, address/alias and routing records. | Resolve with authorised admin and rollback plan if needed. |
| Old mail missing | Check previous host and migration scope. | Explain separation and quote authorised migration. |
| Legitimate system fails authentication | Review sender inventory and DNS policy. | Correct with provider guidance rather than weakening authentication indiscriminately. |
Outstanding go / hold conditions
- Actual tenant, DNS, licences and sender inventory unverified.
- No mailboxes or DNS changed and no credentials handled.
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.