Make every website request clear and traceable.
Use this route for content updates, maintenance needs, technical concerns, and scoped improvements tied to a managed website.
Routes
Start with the task that matches the situation.
- Content changeContact
Include the exact page, approved replacement content, and desired timing.
- Technical issueContact
Include the URL, device, browser, impact, and steps that reproduce the problem.
- New featureTalk to a specialist
Explain the user need and desired outcome before proposing an implementation.
What we need
A complete request reduces 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.