Categorize internal IT, HR and facilities requests.

01

Many workflows start the same way

Someone submits information. Then someone else has to figure out what should happen next. It might be:

• An employee IT request
• An HR policy question
• A facilities issue
• An internal procurement request

The first step is often classification.

02

Turn previous decisions into training examples

Use internal requests that your team has already assigned to the right queue. For example:

Those previous routing decisions can become the training data for a StayCharted AMT model.

03

Let your organization define the destinations

Your labels might be IT Access, HR Benefits, Facilities Maintenance, or Procurement. Train on the destinations your organization uses and check whether the request text contains enough information to distinguish them.

04

Use the prediction inside an application

Once trained, the model can sit behind a form, portal, ticketing system or internal application.

1. 1Employee
2. 2Request Form
3. 3Business Application
4. 4StayCharted AMT API
5. 5Predicted Destination
6. 6Workflow / Queue / Team

Your application uses the predicted category to route the request.

05

Automate the obvious. Review the uncertain.

A practical implementation does not have to automate every request. Your application can use prediction confidence to decide whether to:

• Route automatically
• Recommend a destination
• Send the request for manual review

This gives operations teams a controlled way to introduce AI without redesigning the entire process.