From Bright Pattern Documentation
< 3.11:Scenario-builder-reference-guide
Revision as of 04:55, 28 July 2016 by Sasha (talk | contribs) (Set Agent State)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
• 3.10 • 3.11 • 3.12 • 3.13 • 3.14 • 3.15 • 3.16 • 3.17 • 3.18

Set Agent State

This block supports agent authentication via phone (i.e., using extension and PIN) when agents select the Dial-in and keep line open option as their phone device option. Also known as nailed connection, this option allows agents to establish a phone connection with the system from any phone and use this established physical connection for handling of subsequent calls within their login sessions.

A scenario that supports authentication via phone will usually begin with a Collect Digits block, which prompts the caller to enter their extension number and PIN and stores them in variables. The Set Agent State block then verifies the supplied extension number and PIN against the user configuration to authenticate the caller. If the agent is successfully authenticated, the block returns his current state and stores it in variable $(agentState). If the state is Not Ready, the Not Ready reason will be stored in variable $(notReadyReason). ServicePattern provides a scenario template to support the above process. The template is called External Agent Dial In.

Note that instead of reporting the agent’s current state, the block can be used to switch the agent to another desired state.


Conditional Exits

  • Authentication Failed – The supplied extension number and PIN combination does not match credentials of any configured user.


Settings

  • Agent’s digital ID (extension) - Agent’s extension number or the name of the variable which holds the extension number, e.g., $(varPhone).

  • Over the phone agent PIN – Agent’s PIN or the name of the variable which holds the agent’s PIN, e.g., $(varPIN).

  • Action – The desired action; either get the current agent’s state or set it to one of the listed state. Note that for the agent authentication scenario described above the action must be set to GET_STATE.

      < Previous | Next >
      < Previous | Next >