Clock and Timezone Checks for Internet Billing

WayaDesk / Installation and migration

Time is part of a billing rule. It affects expiry, renewal boundaries, event ordering and support evidence. An operator can misunderstand an otherwise correct record if the displayed timezone is unclear or the components disagree about time.

Agree the customer-facing convention

Use an explicit local date and time when explaining service boundaries. LinkDesk’s documented calendar-month policy uses Africa/Nairobi anniversaries. Staff should recognise that convention and avoid translating it informally in a way that changes the customer’s expectation.

Compare the relevant components

Check the host and router observations during setup. When investigating a payment or reconnect, note which component produced each timestamp. The time a customer sent a message may differ from the payment or access event being investigated.

• Record the intended timezone in the operator handover.
• Check a renewal and expiry near a date boundary.
• Include month-end cases when calendar-month plans are used.

Use dates in support messages

“It expires tomorrow” becomes ambiguous when forwarded later. A specific date, time and timezone is more durable. This is especially helpful for early renewal and scheduled package changes, where several periods may appear in the account history.

Recheck after host changes

Migration, restoration or a replacement computer can introduce different settings. Repeat the time-related acceptance checks before trusting future schedules. Correcting the display should not involve rewriting old payment evidence simply to make unrelated timestamps appear identical.