KENYA · GUIDE 0594 · EDITION 4.2
Domain renewal support in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Support renewals for domains the client controls, identifying registrar access, registrant contacts, expiry information, billing approval, and website or email dependencies.
The operating sequence for this offer is:
- Confirm the clients registrant ownership, registrar access and authoritative contacts, then inventory expiry dates and payment responsibilities without transferring domain control.
- Agree reminders and renewal authority, verify current records through authorized access and obtain approval before any purchase, transfer or DNS change.
- Hand over the renewal register and recovery-contact checklist, distinguish reminders from completed renewals and keep the owner in control of registrar credentials.
Put acceptance into the job record
Owner retains registrar control and dates match current records.
Have the owner verify registrar access and renewal confirmation, checking contact accuracy and continuity of dependent services without unnecessarily changing domain configuration.
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 | Support renewals for domains the client controls, identifying registrar access, registrant contacts, expiry information, billing approval, and website or email dependencies. |
| During delivery | Agree reminders and renewal authority, verify current records through authorized access and obtain approval before any purchase, transfer or DNS change. |
| At acceptance | Have the owner verify registrar access and renewal confirmation, checking contact accuracy and continuity of dependent services without unnecessarily changing domain configuration. |
| At the pilot review | Keep registrar details, owner access checks, expiry records, approved payments, renewal confirmation, notification recipients, and unresolved dependencies requiring the client's continued attention. |
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.
A business can lose website and email continuity when renewal notices go to an old employee or payment is assumed rather than confirmed.
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 | Compare owner account with independently obtained registrar information. | Do not pay an unsolicited renewal notice merely because it names a real domain. |
| 2 | Have owner verify recovery contact and access using their own authentication. | No password, recovery code or card details are collected. |
| 3 | Read displayed renewal price, period, currency, tax and any redemption status. | First-year promotional price is not assumed to be renewal price. |
| 4 | Read back exact domain/period before owner authorises payment. | No DNS, registrant or nameserver change is bundled into renewal without separate instruction. |
| 5 | Record receipt and new displayed expiry; explain reminders and auto-renew limitations. | A card charge without matching renewal state remains unresolved with registrar. |
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 |
|---|---|---|
| Notice names unfamiliar payee | Compare registrar account and independently verified contact. | Pause payment and verify directly. |
| Paid but expiry unchanged | Check exact domain/period and transaction status. | Ask registrar to resolve with receipt. |
| Recovery email obsolete | Check owner-controlled recovery process. | Update through registrar's authorised verification route, never bypass it. |
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.