Screen Pop URL - Revision history

Mike Lunn: /* E-Agent */

2015-01-15T22:24:10Z

E-Agent

Mike Lunn at 20:41, 13 May 2014

2014-05-13T20:41:18Z

Mike Lunn at 20:41, 13 May 2014

2014-05-13T20:41:03Z

Mike Lunn at 20:39, 13 May 2014

2014-05-13T20:39:17Z

Mike Lunn at 20:37, 13 May 2014

2014-05-13T20:37:36Z

Mike Lunn at 14:31, 1 November 2013

2013-11-01T14:31:25Z

Mike Lunn at 12:53, 12 July 2013

2013-07-12T12:53:48Z

Mike Lunn at 12:53, 12 July 2013

2013-07-12T12:53:36Z

Mike Lunn at 14:51, 10 July 2013

2013-07-10T14:51:19Z

Mike Lunn at 14:50, 10 July 2013

2013-07-10T14:50:15Z

← Older revision		Revision as of 22:24, 15 January 2015
Line 46:		Line 46:

	Here is a guide from AllState on how to configure their E-Agent CRM to work with our screen-pop. The information matches the general information found above, but has a specific example for E-Agent for further clarification.		Here is a guide from AllState on how to configure their E-Agent CRM to work with our screen-pop. The information matches the general information found above, but has a specific example for E-Agent for further clarification.
		+
		+	A dealer has brought to our attention that there is an updated string for the screenpop:
		+	https://eagent.allstate.com/account/login.aspx?phone={0}

	[[File:EAgent VOIP Integration.doc\|File:EAgent VOIP Integration.doc]]		[[File:EAgent VOIP Integration.doc\|File:EAgent VOIP Integration.doc]]

← Older revision		Revision as of 20:41, 13 May 2014
Line 46:		Line 46:

	Here is a guide from AllState on how to configure their E-Agent CRM to work with our screen-pop. The information matches the general information found above, but has a specific example for E-Agent for further clarification.		Here is a guide from AllState on how to configure their E-Agent CRM to work with our screen-pop. The information matches the general information found above, but has a specific example for E-Agent for further clarification.
−
−

	[[File:EAgent VOIP Integration.doc\|File:EAgent VOIP Integration.doc]]		[[File:EAgent VOIP Integration.doc\|File:EAgent VOIP Integration.doc]]

← Older revision		Revision as of 20:41, 13 May 2014
Line 46:		Line 46:

	Here is a guide from AllState on how to configure their E-Agent CRM to work with our screen-pop. The information matches the general information found above, but has a specific example for E-Agent for further clarification.		Here is a guide from AllState on how to configure their E-Agent CRM to work with our screen-pop. The information matches the general information found above, but has a specific example for E-Agent for further clarification.
		+
		+
		+
		+	[[File:EAgent VOIP Integration.doc\|File:EAgent VOIP Integration.doc]]

@@ Line 1: / Line 1: @@
 {{IP_PBX_Manual|sortkey=Screen Pop URL}}
 The Screen Pop URL feature allows the PBX and QManager to interface with 3rd party products for various reasons.&nbsp; You could have the inbound caller ID number read, and do a search for that in CRM software.&nbsp; You could integrate with Google Maps and get a screen pop showing where the business or residence calling inbound is located.
-Right clicking on the inbound call will give a list of available screenpops, allowing you to choose which to activate on a case to case basis.  If you would like a screenpop to occur automatically, you must check AutoPopInbound and Enable Automatic Popups.  Once enabled, the screenpop will happen automatically when the call is answered.
+Right clicking on the inbound call will give a list of available screenpops, allowing you to choose which to activate on a case to case basis. If you would like a screenpop to occur automatically, you must check AutoPopInbound and Enable Automatic Popups. Once enabled, the screenpop will happen automatically when the call is answered.
+<br/>[[File:PBXSetup-ScreenPop.jpg|File:PBXSetup-ScreenPop.jpg]]
@@ Line 45: / Line 43: @@
 Use this link for specific information pertaining to [[RTI Integration]]
-===E-Agent===
+=== E-Agent ===
-Here is a guide from AllState on how to configure their E-Agent CRM to work with our screen-pop.  The information matches the general information found above, but has a specific example for E-Agent for further clarification.

← Older revision		Revision as of 20:37, 13 May 2014
Line 44:		Line 44:

	Use this link for specific information pertaining to [[RTI Integration]]		Use this link for specific information pertaining to [[RTI Integration]]
		+
		+	===E-Agent===
		+	Here is a guide from AllState on how to configure their E-Agent CRM to work with our screen-pop. The information matches the general information found above, but has a specific example for E-Agent for further clarification.

← Older revision		Revision as of 14:31, 1 November 2013
Line 4:		Line 4:
	The Screen Pop URL feature allows the PBX and QManager to interface with 3rd party products for various reasons.  You could have the inbound caller ID number read, and do a search for that in CRM software.  You could integrate with Google Maps and get a screen pop showing where the business or residence calling inbound is located.		The Screen Pop URL feature allows the PBX and QManager to interface with 3rd party products for various reasons.  You could have the inbound caller ID number read, and do a search for that in CRM software.  You could integrate with Google Maps and get a screen pop showing where the business or residence calling inbound is located.

		+	Right clicking on the inbound call will give a list of available screenpops, allowing you to choose which to activate on a case to case basis. If you would like a screenpop to occur automatically, you must check AutoPopInbound and Enable Automatic Popups. Once enabled, the screenpop will happen automatically when the call is answered.

← Older revision		Revision as of 12:53, 12 July 2013
Line 1:		Line 1:
−	~~__NOTITLE__~~	+
	{{IP_PBX_Manual\|sortkey=Screen Pop URL}}		{{IP_PBX_Manual\|sortkey=Screen Pop URL}}

← Older revision		Revision as of 14:51, 10 July 2013
Line 38:		Line 38:
	*{3} = Logged in Agent (your agent in Q Manager)		*{3} = Logged in Agent (your agent in Q Manager)
	*{4} = Your Extension number.		*{4} = Your Extension number.
		+
		+	Use this link for specific information pertaining to [[RTI Integration]]

← Older revision		Revision as of 14:50, 10 July 2013
Line 4:		Line 4:

	[[File:PBXSetup-ScreenPop.jpg\|File:PBXSetup-ScreenPop.jpg]]		[[File:PBXSetup-ScreenPop.jpg\|File:PBXSetup-ScreenPop.jpg]]
		+
		+
		+
		+	{\| style="width: 500px" border="1" cellpadding="1" cellspacing="1"
		+	\|-
		+	\| Name<br/>
		+	\| This can be set to anything<br/>
		+	\|-
		+	\| URL<br/>
		+	\| The string the 3rd party product needs to call the PBX, this should be given by the 3rd party manufacturer.<br/>
		+	\|-
		+	\| Use Browser<br/>
		+	\| When checked, the screenpop will go to the browser<br/>
		+	\|-
		+	\| Use POST<br/>
		+	\| When checked, the URL uses the HTTP POST method (use caps for POST) to send the URL's query string<br/>
		+	\|-
		+	\| Delete<br/>
		+	\| Deletes the selected URL<br/>
		+	\|-
		+	\| Copy<br/>
		+	\| Copies the selected URL<br/>
		+	\|-
		+	\| Add<br/>
		+	\| Adds a new URL<br/>
		+	\|}
		+
		+	When configuring the URL, you may need to specify variables that correlate to what is passed to the 3rd party software.  They are dynamically configured on the client where:
		+
		+	*{0} = CID Number
		+	*{1} = CID Name
		+	*{2} = Dialed Number (for inbound calls)
		+	*{3} = Logged in Agent (your agent in Q Manager)
		+	*{4} = Your Extension number.