Skip to content

Hassan

My feedback

1 result found

  1. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Hassan commented  · 

    Good suggestion — the renewal and expiry side of this is where I'd get the most use out of it too.

    One thing worth adding to the scope, since a lot of Cloudways agencies manage servers for Gulf-based clients: those timelines often live on two calendars at once. Commercial registration renewals, Iqama and work permit expiries, ZATCA filing windows and contract end dates are usually tracked in Hijri, while billing cycles, SSL expiries and backup retention sit on Gregorian dates. If Copilot only counts calendar days in one system, an agency still has to do the conversion by hand before the day count means anything useful.

    So alongside the day counter, calendar-aware input would help — accept a Hijri date, show the Gregorian equivalent, then run the deadline maths from there. I use https://dateconvertersa.com/ for exactly that when I need to line up a client's Hijri renewal date against their Gregorian billing cycle.

    Weekend handling is worth flagging too. Saudi weekends are Friday–Saturday, not Saturday–Sunday, so an "exclude weekends" option needs a region setting or the project timeline comes out wrong.

    The reminder suggestion is the part I'd prioritise, though. Even a rough "this expires in 14 days" nudge would catch more missed renewals than a perfect calculator nobody remembers to use.