# Route an issue to the team that owns it.

> Check service status routes for an active project, a managed website, a billing question, or an urgent issue. A live public status feed is not connected yet.

Source: https://scayverstaging.1wp.site/status/

![One warm-lit fiber strand in a bundle of dark strands](https://scayverstaging.1wp.site/wp-content/uploads/2026/08/sg-support-fiber-line.webp)

Service status starts with the correct support path for an active project, managed website, billing question, or urgent service issue.

Choose a route [Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/?form=book)

Routes

## Start with the task that matches the situation.

1. [Active project](https://scayverstaging.1wp.site/client-portal/dashboard/)
   Use the assigned project route for current milestones, approvals, and delivery questions.
   Project dashboard
2. [Managed website](https://scayverstaging.1wp.site/client-portal/website/)
   Send a maintenance, content, or website support request.
   Manage my website
3. [Urgent issue](https://scayverstaging.1wp.site/contact/)
   Contact the team with the affected URL, business impact, and time first noticed.
   Contact

What we need

## Service status is useful only when it helps someone act.

This route does not publish an unverified automated uptime claim. It helps a visitor identify the affected system, communicate the impact, and reach the responsible workflow.

### What the team needs.

- Impact
- Context
- Owner

Questions

## Answers before the next step.

**Where should an active client start?**

Use the project dashboard or managed website route attached to the account.

**What makes an issue urgent?**

Describe the actual customer or business impact so the team can evaluate priority.

**Should I send credentials?**

No. Do not place passwords, payment details, or private credentials in a general support message.