KENYA · GUIDE 0595 · EDITION 4.2
Email account setup in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Set up business email with client-owned accounts, agreed naming, administrator authority, recovery arrangements, device access, and a migration plan for existing correspondence.
The operating sequence for this offer is:
- Confirm domain ownership, mailbox users and recovery responsibilities, then approve the provider, permissions and any migration scope before changing email settings.
- Configure through authorized provider tools, test send and receive paths and obtain approval before DNS or routing changes that could interrupt existing mail.
- Have the owner verify mailbox and recovery access, provide administration instructions and document recurring subscriptions and support boundaries.
Put acceptance into the job record
Mailboxes work and recovery and permissions are documented.
Ask each user to send and receive test messages, verify identity details, and access recovery guidance, checking shared mailboxes separately from individual accounts.
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 | Set up business email with client-owned accounts, agreed naming, administrator authority, recovery arrangements, device access, and a migration plan for existing correspondence. |
| During delivery | Configure through authorized provider tools, test send and receive paths and obtain approval before DNS or routing changes that could interrupt existing mail. |
| At acceptance | Ask each user to send and receive test messages, verify identity details, and access recovery guidance, checking shared mailboxes separately from individual accounts. |
| At the pilot review | Record account ownership, aliases, delivery tests, migrated material, user-device checks, recovery contacts, and unresolved forwarding or shared-mailbox questions before final handover. |
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.
Email setup fails when messages send successfully but replies disappear into an unmonitored old inbox or the business owner lacks administrator recovery access.
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 | List three users, aliases, existing provider and devices; export current DNS records. | Do not change MX before all required mailboxes exist. |
| 2 | Use tenant/registrar's supported ownership process with owner-controlled accounts. | No invented verification record or shared personal password. |
| 3 | Use tenant-provided MX/Autodiscover/SPF requirements and review existing legitimate senders. | Do not overwrite an SPF policy blindly or add conflicting records. |
| 4 | Use authorised test addresses for internal/external send, receive, reply and alias delivery. | Check destination and headers/status where appropriate; a sent-folder copy is not receipt. |
| 5 | Owner enrols supported MFA/recovery and receives account/device instructions and rollback contacts. | Old mail stays at prior host unless a separate migration is performed; explain this before cutover. |
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 |
|---|---|---|
| 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. |
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.