Jump to: navigation, search

Web Engagement Cluster:chat:identifyCreateContact

(Rpfeiffer used the OptionEdit action.)
Line 11: Line 11:
 
|valid=1, 2, or 3
 
|valid=1, 2, or 3
 
|takeseffect=Immediately
 
|takeseffect=Immediately
|shortdesc=Specifies how a contact should be processed in the Contact Server.<br/><strong>Note:</strong> This option is applicable for proactive chat sessions only. For reactive chat sessions, you can specify the related parameter in the chat widget. See the [[Documentation:GWE:API:StartChat#createContact{{!}}createContact API docs]] for details.
+
|shortdesc=Specifies how a contact should be processed in the Contact Server.<br/><strong>Note:</strong> This option is applicable for proactive chat sessions only. For reactive chat sessions, you can specify the related parameter in the chat widget. See the [[Documentation:GWE:API:StartChat:8.5.0#createContact{{!}}createContact API docs]] for details.
 
}}
 
}}
 
{{PubExtended
 
{{PubExtended

Revision as of 20:52, March 20, 2018


View in ref guide.

Edit this option          Publish this option          Clear draft content


Published Option

identifyCreateContact

Default Value: 3
Valid Values: 1, 2, or 3
Changes Take Effect: Immediately


Specifies how a contact should be processed in the Contact Server.
Note: This option is applicable for proactive chat sessions only. For reactive chat sessions, you can specify the related parameter in the chat widget. See the createContact API docs for details.

Note: Web Engagement does not work with Contact Server directly, it only passes a parameter value, which has one of the following meanings:

  • 1— Do not try to identify this contact and do not try to create it.
  • 2—Try to identify this contact, but do not create it if absent.
  • 3—Try to identify this contact and create it if absent.

Draft Option

No draft option

Comments or questions about this documentation? Contact us for support!