Before
Support staff likely had to read each Teams request, extract the requester’s email, and search separate sources for the user’s identity, requested application, and target device. They then had to copy the results into a new ServiceNow incident and summarize the work for the next stage of provisioning.
How it works
- Capture the application provisioning request and extract the requester’s email address.
- Verify the requester and enrich the request with application catalog and device information.
- Create a structured ServiceNow incident and return a plain-text summary of the information and actions completed.
Workflow details
- Request intake: The workflow receives a Microsoft Teams message requesting application provisioning and extracts the requester’s email address from the message.
- Requester verification: It uses the email address to retrieve the requester’s full name from the organization’s directory, helping ensure the incident is associated with the correct person.
- Request enrichment: The workflow looks up the requested application in the application catalog and retrieves the target device details from the configuration management database.
- Incident creation: It creates a new ServiceNow incident and automatically populates the short description and full description with the requester, application, device, and other gathered context.
- Operational summary: After the incident is created, the workflow returns a plain-text report describing the collected information and actions completed, giving support teams a consistent handoff for the provisioning request.
What changed
Each incoming provisioning request is automatically enriched and documented in a consistently structured ServiceNow incident instead of requiring separate lookups and manual data entry. The completed context and action summary are available immediately after the automated triage sequence finishes.
Work removed
Reading each request to extract the requester’s email, manually looking up the requester’s name, searching for the requested application, retrieving target device details, creating the ServiceNow incident, copying the gathered information into its fields, and writing the action summary.
Expected outcome
The workflow can remove at least four recurring lookup and documentation actions per request while producing a more complete and consistently structured provisioning incident.
