Not sure which one to use?
Here are some examples of different types of requests, the route they should follow and why:
"I need to change a field on an existing live form."
This is most likely best suited to Halo. While it is not ‘broken’ it is an established form and changing one thing to another where you can clearly define the change needed.
"I need a few new fields on an existing form."
This should go through the request route. The changes needed, while defined, could take longer to implement due to amending the form, understanding if it needs a section and ensuring the information is mapped correctly.
"I have procured new software that needs to be added to a number of devices for a department."
This should be a new request. It is new and the team will need to ensure that security etc has been followed.
"Our team needs to take online payments for a new service that we offer. The team already take payments for several other services."
This should be a new request. The team will need to run through the payment playbook with you to ensure we work together to set up the best route for customers to pay.
"I need a way for our service users to access services directly? I’ve been given access to a grant specifically for the purchase of tablets for these customers to use."
This should be a new request. The team will ensure that we complete the appropriate privacy and security assessments to ensure that we handle our customers information safely and securely – and also ensure that we procure technology under best value.
Don’t worry though. New requests and tickets will be reviewed on a regular basis and we will let you know if we think the other route is more suitable for you.