Hello, I’m Nora, your AI guide from Technology Last Stop. This guide covers Planned maintenance and customer reminders. Record a customer maintenance window, release evidence and reminders without deleting company data. Current availability: Scheduling and reminders implemented; provider delivery verification required.

Before you start. TLS owner, validated company timezone, accepted QA evidence, backup reference and rollback plan. A functioning TLS support mailbox and current company billing/user email addresses.

Step 1. Open Companies > company > Planned changes. Schedule at least 60 days ahead. Use a 5–240-minute window contained in 01:00–05:00 in the company timezone. Enter UTC start/end as labeled in the form.

Step 2. Record the exact source commit, artifact SHA-256, QA reference, backup reference and rollback steps. A plan does not execute a deployment or make a backup by itself.

Step 3. The system queues the announcement and reminders 30, 7 and 1 days, then 1 hour before the window. Customers can read their own schedule and in-app notices. Email activity distinguishes accepted, failed and uncertain results.

Step 4. Resolve failed/uncertain notices using provider evidence. Starting work requires the planned window and accepted due announcements. Publish the validated release through the owner workflow; record completion and a result note.

Step 5. Cancel or reschedule explicitly when readiness changes. Existing company data is retained by these plan actions. Test restoration and additive migrations separately; never treat a plan as a no-risk guarantee.

Now verify the result. A short-notice or daytime normal-maintenance window is rejected. A second company cannot read the first company’s plan; reminders do not duplicate on scheduler replay.

If you get stuck. Provider accepted is not a delivery receipt. An uncertain timeout is not automatically resent. Urgent incident handling requires a separate incident process; do not backdate a normal plan to bypass notice rules.

Use the current written guide for exact URLs, permission names, and provider documentation. Pause before entering credentials, and keep them in protected configuration. I’m Nora, your TLS guide.