# Make every website request clear and traceable.

> Send website support requests for content updates, maintenance, technical concerns, and scoped improvements on a managed site, with credentials left out.

Source: https://scayverstaging.1wp.site/client-portal/website/

![Laptop on a white desk with a coffee mug and small plant nearby.](https://scayverstaging.1wp.site/wp-content/uploads/2026/07/sg-mainpages-138728-hero.webp)

Send website support requests here for content updates, maintenance needs, technical concerns, and scoped improvements tied to a managed website.

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. [Content change](https://scayverstaging.1wp.site/contact/)
   Include the exact page, approved replacement content, and desired timing.
   Contact
2. [Technical issue](https://scayverstaging.1wp.site/contact/)
   Include the URL, device, browser, impact, and steps that reproduce the problem.
   Contact
3. [New feature](https://scayverstaging.1wp.site/talk-to-a-specialist/)
   Explain the user need and desired outcome before proposing an implementation.
   Talk to a specialist

What we need

## Complete website support requests reduce delay and rework.

The affected page, expected behavior, priority, source content, and verification criteria should travel together through the maintenance workflow.

### What the team needs.

- Page
- Expected result
- Priority

Questions

## Answers before the next step.

**What should a content request include?**

Include the page URL, exact replacement copy, approved media, and where the content should appear.

**How should I report a bug?**

Include the URL, device, browser, steps, actual result, expected result, and business impact.

**Is a new feature a maintenance request?**

A new capability may need discovery and scope before it enters the managed website workflow.