Five9 LabA student's open lab: learning and sharing, free for everyone.

Blended

Not Ready is a real state

How agents move between inbound, autodial, and outbound without lying to the dialer.

Learn it in 5 minutes

Blended operations and autodial ยท practice ยท 12 min full read

Agents are not always available. TCPA manual touch forces Not Ready when preview time runs out, and it does not dial. A blend that assumes every login is a dialer resource will over-predict.

Reason codes and Not Ready are how you explain the gap. They are not a carrier outage. Reports in the agent category are where you see the pattern before you add lines.

TimeoutReadThe TCPA record sits onscreen.AgentStallThe preview timer ends.AgentStateThe agent becomes NotReady.DialerNoThe external number isnot auto-dialed.DialerSeeAgent reports show thestate.ReportStaffDo not count that loginas a predictiveAdmin

The dialer must not count these people.

Worked example

Count the floor

From a sample of 20 logins, subtract Not Ready before you pick a mode.

  1. Count Ready
  2. Count Not Ready
  3. Pick the mode from Ready

The mode uses the Ready number.

TCPA preview timeout sets
Not Ready during a blend
Agent reports are a standard category. True or false?
A reason code explains
Adding lines because people are Not Ready

Sources and go deeper

Ecosystem

Glossary. RFC 3261: The SIP specification. It does not choose your dial plan. RFC 3261

Sister technologies. Studio digital IVA. A ChatBot task key from the matching regional Studio portal into VCC. Studio digital IVA with VCC

Config. From a sample of 20 logins, subtract Not Ready before you pick a mode.

Troubleshooting. Half the logins are in a meeting. Use the Ready count.

Cross-platform bridge. A mapping to another PBX or contact center is a teaching bridge. It is not an import button.

Future hook. The guide's cloud endpoint stays unset. Confirm before relying on a dated catalog or a case-study number.

Back to Blended operations and autodial