Unity 5.X Callers enter bad DNs in one AA end up at wrong operator

Answered Question

I've got an IPT/Unity 5.X install with four remote sites; each has their own AutoAttendant. When users are in LA AutoAttendant and enter a bogus extension, they always end up in Operator defined for the first site Roll out. I have seperate Operator CHs set for each city but the when callers error out on a DN, they always end up at my Memphis AA operator. Suggestions on how to keep errored callers to the dialed offices' operator?

THANKS.

I have this problem too.
0 votes
Correct Answer by mciarfello about 8 years 8 months ago

Hi Mike,

Found it for you.

Tools depot, advanced options, turn on the ERROR greeting. I didn't have to reboot--just refreshed the saweb page.

Go back to your call handlers. On the greetings page, under ERROR greeting, define the "after greeting" for "send caller to--call handler" then specify the call handler you want to go to.

So you will have two greeting actions. Standard and error. The standard after greeting action will be to go to that site's operator. The ERROR after greeting action will probably loop back to your city call handler.

um, don't give me points, we are from the same company. Lunch sounds great :)

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
mciarfello Mon, 03/17/2008 - 18:00

Hi Mike,

Found it for you.

Tools depot, advanced options, turn on the ERROR greeting. I didn't have to reboot--just refreshed the saweb page.

Go back to your call handlers. On the greetings page, under ERROR greeting, define the "after greeting" for "send caller to--call handler" then specify the call handler you want to go to.

So you will have two greeting actions. Standard and error. The standard after greeting action will be to go to that site's operator. The ERROR after greeting action will probably loop back to your city call handler.

um, don't give me points, we are from the same company. Lunch sounds great :)

Actions

This Discussion