Did you know that you can customize widget information based on the customer? There is always a need for something dynamic. This is possible only when we pass the context to the widget code. SalesIQ allows you to pass a bunch of contexts to the widgets implementation to make it dynamic and this post will talk all about these contexts.
A widget in Zoho SalesIQ lets you bring all of the apps that you use for your business inside Zoho SalesIQ. The following are the parameters that are being passed to the widget when it is executed to make it dynamic:
Operator
Display visitor information dynamically to each operator. Say, you have an associate and a supervisor assisting the visitors and you want to display subscription details and provide access. You can give operators access to information based on their roles and perform actions with the operator's email.
Environment
Learn about the environment the widget is functioning in. For example,
- If you want to know about the language of the operator who is conversing with the visitor. So, if the operator's language is English, then the widget will be rendered in that language.
- Environment in which the operator has accessed SalesIQ ie, if it was on the web, mobile or on a tablet. So, if you want to display only selected data on your mobile, you can set the client as mobile and the widget will be rendered accordingly.
Context
Find out which context the widget is being invoked for. This can be shown in the conversation window, contact window and visitor window. So, when you view an entity in a conversation, the conversation data will be available in the context parameter.
Action
Analyse the action performed inside the widget and learn about the action type, search query, button name or the list element name. Say, we have a membership upgradation form inside the widget and the upgrade/downgrade button is clicked after all details have been entered. The parameter will contain the action type which is button and the button name which is Upgrade/Downgrade.
Target:
This parameter contains the details of the section & the element from which the action was performed. In the membership upgradation form example, it has details like section name which is Customer level, unique reference ID of the element from which the action is performed, reference ID of the section in which the button action is performed and reference ID of the action performed. This parameter will be available inside the Action Handler.
Regards,
Michelle