MENU
How do you prevent a task which has been rejected by an agent from being dynamically assigned to the same agent in the next 24 hours?
Suggested Answer: B
Get Premium CIS-FSM Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
40 comments · newest first
DA
Daron
11 months ago
D? Nah, that won't really solve the problem.
KI
Kiley
11 months ago
C seems like the best option for dynamic scheduling.
VI
Viola
11 months ago
Wait, can we really set a 24-hour rule? Sounds tricky!
LA
Lavonda
12 months ago
I think A could work too, but not as effective.
DE
Deonna
12 months ago
B is the way to go!
JA
Janine
1 year ago
I vaguely recall discussing agent task rejection preferences, but I can't remember if that directly relates to the 24-hour rule.
TR
Trinidad
1 year ago
I’m leaning towards option C because it mentions unassignment constraints, which seems relevant to preventing reassignments.
CH
Charlesetta
1 year ago
I feel like we covered something similar in practice questions. Configuring custom assignment rules could be a way to handle this, but I’m not confident.
GE
Geoffrey
1 year ago
I think option B sounds familiar, but I'm not entirely sure if it's the right one. I remember something about setting a duration for rejected tasks.
LE
Leslie
1 year ago
I feel pretty confident about this one. Based on the question, the "Configure custom assignment rules" option seems like the most straightforward solution to prevent the task from being assigned to the same agent within 24 hours. I'll go with that.
CH
Cheryl
1 year ago
Okay, let me think this through. I'm guessing the "Configure rejected technician duration system property" might be the way to go, as that seems to directly address the 24-hour requirement. But I'll double-check the other options just to be sure.
NA
Nadine
1 year ago
Ah, I see. This is about preventing the same agent from getting a rejected task again in the next 24 hours. I think the "Configure unassignment constraints for dynamic scheduling" option sounds like it could be the right approach to solve this.
SU
Suzi
1 year ago
Hmm, I'm a bit unsure about this one. I know there are different ways to handle task assignments and rejections, but I'm not sure which option would be the best fit here. I'll need to think it through carefully.
GW
Gwen
1 year ago
This seems like a straightforward configuration question. I think the key is to look for options that directly address the requirement of preventing the task from being assigned to the same agent within 24 hours.
MA
Markus
2 years ago
Is there an option to just send the task to the agent's spam folder? That way, they'll never see it coming!
MA
Mabelle
2 years ago
C) Configure unassignment constraints for dynamic scheduling
RO
Rochell
2 years ago
B) Configure the rejected technician duration system property
OL
Olga
2 years ago
A) Configure custom assignment rules
GA
Gail
2 years ago
If I choose Option D, can I also configure 'agent task rejection excuses'? I've got a few good ones up my sleeve.
MA
Matthew
2 years ago
C) Configure unassignment constraints for dynamic scheduling
LE
Leanna
2 years ago
B) Configure the rejected technician duration system property
FR
Freeman
2 years ago
A) Configure custom assignment rules
DO
Dottie
2 years ago
Option A sounds good, but I can't help but wonder if it would be as effective as the other choices. Gotta go with my gut on this one.
TO
Toshia
2 years ago
I'm not sure about option D, it doesn't seem as practical as the others.
AM
Amie
2 years ago
I'm leaning towards option C, it seems like it could work well.
ER
Eric
2 years ago
I agree, option B seems like a solid choice.
CR
Cristy
2 years ago
I think option B might be the way to go here.
AN
Annice
2 years ago
I'm not sure about that. I think the answer might be C) Configure unassignment constraints for dynamic scheduling to prevent reassignment to the same agent.
BE
Beatriz
2 years ago
Option D seems like it would give the agents more control over the task assignments. That could be useful.
CA
Caitlin
2 years ago
Hmm, I'm not sure. Maybe Option B would be a good choice to prevent the same agent from getting the task again.
TA
Tarra
2 years ago
Let's make sure to set that up to avoid assigning the task to the same agent again.
CA
Cathrine
2 years ago
I agree, configuring the rejected technician duration system property should do the trick.
EL
Elly
2 years ago
I think Option B is the way to go.
LO
Louisa
2 years ago
I think Option C is the way to go. Unassignment constraints make the most sense here.
LI
Lilli
2 years ago
I think Option D could be worth considering as well.
PE
Pedro
2 years ago
I'm not sure about Option B, it might not be as effective.
JI
Jillian
2 years ago
I think Option A could also work if set up correctly.
LU
Luis
2 years ago
I agree, Option C seems like the best choice.
TO
Tomas
2 years ago
I agree with Carry. By configuring custom assignment rules, we can prevent the task from being assigned to the same agent again.
CA
Carry
2 years ago
I think the answer is A) Configure custom assignment rules.