A.LIFO

B.Standard

C.Quick

D.FIFO

E.Round Robin (All)

F.Round Robin (Logged In)

G.Advanced Routing

A.Advanced routing

B.Syndicated chat

C.Engagement engine

D.Business rules

A.Custom object field

B.Merge field

C.Custom field

D.Variable

A.It helps to identify the root cause of an incident.

B.It can be set to a maximum depth of three in hierarchy levels.

C.It can be linked to categories.

D.It can be made visible on the Customer Portal.

E.It can be linked to products.

A.All incident rules should have an action to transit from the initial state to another state.

B.A catch-all incident rule should be typically at the bottom of the rules listed in the initial state.

C.Incident rules should have one rule state.

D.A catch-all rule has no impact on incident rules.

E.Queues, staff accounts, custom fields, and profiles must be functioning before rules can be built based on them.

F.A catch-all escalation action has no impact on incident rules.

G.Incident rules should have a minimum of two rule states.