Configure and run an Issue Auto Resolution simulation
- UpdatedAug 3, 2023
- 3 minutes to read
- Vancouver
- Virtual Agent
The Vancouver release is no longer supported. As such, the product documentation and release notes are provided for informational purposes only, and will not be updated.
Use the incident data from your organization to run simulations from the matching intents that the Issue Auto Resolution application based its predictions on from the case descriptions.
Before you begin
Role required: virtual_agent_admin or admin
About this task
- Cancel a simulation: Stop a simulation in progress.
- Refresh simulation status: Check the status of a simulation in progress.
- Delete a simulation: Delete a simulation configuration, but not while a simulation is running.
Procedure
-
Configure and configure an IAR simulation.
- Navigate to All > Issue Auto Resolution > Simulations > ..
- Select New or Create new simulation if you don't have an existing simulation.
-
On the form, fill in the fields.
Table 1. Create new simulation Field Description Name Name of the simulation configuration. Auto Resolution configuration Table that contains the records to be simulated. The default configuration is for incidents. State Simulation status: - Ready: Simulation is ready to run.
- Running: Simulation is in progress.
- Canceled: Simulation stopped.
- Complete: Simulation finished.
- Error: Simulation encountered a processing error, but continues the simulation for the next set of records.
Record set Condition that identifies the records evaluated in the simulation. For example: [Active] [is] [true]. This condition is automatically filled in with the conditions that you specify in your incident configuration, but you can modify the conditions as needed. Note: Record sets that return a large number of records can take longer to simulate. To reduce the simulation time, consider changing the record set to return a smaller number of records. 50,000 is the maximum record limit for each simulation run. - Select Save.
-
After the new simulation is created, select Run.
The simulation may take a bit more time depending on the number of records that you have. After a run is completed, you see the Latest resolution potential and other simulation results.
-
To specify a time and schedule to run the simulation instead of manually running one, select Enable scheduled job.
You can run the simulation on a daily, weekly, or monthly basis at a specific time, in hours, minutes, and seconds. After you set up the schedule, select Save. To cancel your scheduled job, disable Automatically run this simulation. For each simulation run, the following information is displayed:
Table 2. Simulation results Field Description Start time Date and time that the simulation started. Completed time Date and time that the simulation ended. Progress Percentage of the simulation performed. Latest trained version Version number of the machine learning model used for the simulation. State Status of the simulation: - Complete: Simulation completed its run.
- Ready: Simulation is ready to run.
Running: Simulation is in progress.
- Canceled: Simulation stopped.
- Complete: Simulation finished.
- Error: Simulation encountered an error.
Total records Total number of records evaluated in the simulation. Resolution rate (%) Percentage of cases that the simulation has predicted that match active intents with active topics. -
View the simulation details of the individual run by selecting the link within Runs
> Start time.
Table 3. Run details Field Description Resolution potential Percentage of incidents that have active intents and are mapped to active topics. Inactive topics Virtual Agent topics currently mapped to intents that aren’t active and not visible to users. Select an active topic by using the intent to topic map table in the IAR configuration, or go to Virtual Agent Designer to activate the topic. Mapped intents: Active Intent that was successfully predicted from the case description and is active in your intent to topic map table. Mapped intents: Inactive Predicted intents that are available but not active in your intent to topic map table. No intents found Description in the records didn’t match any of the intents available. Unmapped intents Intent that was successfully predicted from the case description, but the intent itself hasn’t been added to the intent to topic map table in the configuration. To increase the coverage for those incidents, add those additional intents to the table.