What counts as a request
Policy
Requests
A request is how you ask for help with a change, update, improvement, or issue related to your site.
Who this is for
live customers
onboarding customers learning the dashboard workflow
customers who are not sure how to submit work clearly
What this article covers
what a request is
what kinds of things can be submitted as requests
how requests relate to Managed Time, Growth Time, and support
What a request includes
A request can cover many kinds of website work.
For example, you might submit a request to:
update content on a live page
ask for a new page or structured site improvement
report an issue that needs support attention
ask a question about migration progress or something you are seeing on the site
You do not need perfect internal language
You do not need to guess the exact internal classification before submitting something.
Your job is to describe what you need clearly. The request is then reviewed and classified based on the scope.
Why requests matter
Requests create a clear workflow.
They make it easier to:
track what has been submitted
review what is being worked on
connect the request to the right service path
reduce confusion about informal or missing asks
FAQ
Is support different from update requests?
Sometimes yes. Support usually relates to issues, questions, or things that need attention, while update requests are often tied to planned changes.
What happens after I submit a request?
The request is reviewed, classified, and then moved into the right next step.
Can I ask more than one thing in a request?
Yes, but requests are easier to manage when they are clear, organized, and not overloaded with unrelated work.
What if I submit something in the wrong category?
That is okay. The request can still be reviewed and placed in the right workflow.
What if a request is bigger than my remaining time?
The request can still be reviewed and classified based on the work involved.