ambacti
Explore workflows

WEBSITE AVAILABILITY WATCH · Workflow idea

Know when a site needs attention—and when service returns.

Check a selected list of public sites on a regular schedule and keep a dated record of availability changes. When a site appears unavailable, prepare an incident summary with the first observation and duration; when it responds again, record the recovery. Route urgent notices to a designated owner, with approval of the exact recipients and wording before an email or phone call is placed.

Make it yours See how it works ↓
A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A scheduled availability check is due
Produces
A dated availability record with outage start, recovery time, duration, and incident-notification review status.
Category
Reviews & approvals

01 / The starting point

A clear request.
A useful direction.

A list of public site addresses and approved monitoring expectations from a service owner

“Record site outages and recoveries and prepare incident notices for an authorized person to review before contact.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps service owners notice public-site interruptions, understand how long they lasted, and keep a clear incident history.

  1. Choose sites and check intervals

    Select public site addresses the team is responsible for and a review frequency that fits their service needs.

  2. Check current availability

    Record whether each site responds and preserve the observation time and any useful status detail.

  3. Open or update an incident record

    Record the first unavailable observation, avoid duplicate incidents, and add recovery time and duration when service returns.

  4. Verify the incident and prepare a notice

    Have the responsible owner confirm a likely outage and review the proposed urgency, recipient, and message.

  5. Approve before email or phone notification

    Require an authorized person to approve the exact recipient and wording before an incident email or phone call is made.

03 / The result

Something useful.
Something to build on.

A dated availability record with outage start, recovery time, duration, and incident-notification review status.

AmbactiWorkflow folio · 5 steps

Review website availability incidents

Reviews & approvals · Example outcome

The handoff

A dated availability record with outage start, recovery time, duration, and incident-notification review status.

Keep in mind

A failed check may reflect a temporary network issue, maintenance, or a restricted page rather than a confirmed outage. Verify important incidents from an independent perspective, record the observation time, and require an authorized person to approve the exact email recipients and message or phone-call recipient and message before an alert is delivered.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Maintain the approved site list

Name each site owner, its public address, expected availability, and any planned maintenance periods.

Choose check frequency and incident rules

Set how often to check, how repeated failures are confirmed, and when an incident is considered recovered.

Set alert recipients and privacy limits

Limit incident details to appropriate responders and require owner approval for recipient or contact changes.

Assign incident and notification approvers

Name who verifies outages and who approves every email recipient, phone recipient, and message.

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗