--000000000000a36dc80620953ed8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Good morning everyone! Just following up on my previous email regarding Micah and the change in operation of the Midwest-Great Lakes call routing. Again, based on Tim's note to his staff that call center activity would be changing on 9/3, I did not make the routing changes without further confirmation. Ring group membership changes were completed over the weekend. Thanks! On Sat, Aug 24, 2024 at 3:55=E2=80=AFPM Mark Warner wrote: > Hello! > > All ring group adjustments are completed. *Micah Jakoblich* does not > have an 8x8 account. Please provide the desired area code for his 8x8 > phone number and the office/location to which he will be associated. > > Assuming I understood Tim's update to his staff, the changes to REMOVE th= e > call center from the Open Hours forward path will not occur until > 9/3/2024. Please let me know if I have misunderstood that. Also, I woul= d > like to confirm one last time how the configuration should end up in the > end. Please see below: > > *Open Hours* > Option 1 (New Clients / Intakes): Routes directly to InContact Intake > Manager > Option 2 (Existing Clients): Routes to local ring group and goes to ring > group voicemail > Option 3 (Caregivers): Routes to local ring group and goes to ring group > voicemail > Option 4 (Employment verification): Remains the same (routes to Payroll > dept) > Option 5 (All Others): Routes to local ring group and goes to ring group > voicemail > Option 9 (Repeat Menu): Remains the same > > *Closed Hours* > Routing remains the same - All Options (except option 4) route to > InContact / Call Center > > Thanks! > > On Fri, Aug 23, 2024 at 11:26=E2=80=AFAM Mark Warner > wrote: > >> I neglected to list our options. >> >> The "standard" for TheKey's ring groups is to present the ring group nam= e >> and caller number. Unfortunately, the options do not allow us to displa= y >> customer number and then ring group name. The ring group name is presen= ted >> first as it is possible for users to be members of multiple ring groups = and >> having the ring group name presented first might be of value in how the >> user answers the call by knowing what ring group (area/region) with whic= h >> the call is associated. If caller ID info is what's most important and = the >> ring group names are of relatively little value, we can display the >> caller's name and number instead. Do keep in mind, we can only pass on = the >> callerID info provided to us by the caller's carrier service. >> >> Please let me know if you have any other questions. Thanks! >> >> On Fri, Aug 23, 2024 at 10:49=E2=80=AFAM Mark Warner >> wrote: >> >>> Hi everyone! Below are all the ring group labels associated with the >>> Midwest-Great Lakes On-Call groups to which Kendra is referring. Pleas= e >>> review and propose a labeling scheme that might work better for you. I= f we >>> can accommodate those changes, we