As well as using Answers to build out-of-the-box chatbots, you can also integrate with other solutions to create more complex chatbots to meet extended use cases.
Connect to the Infobip customer data platform so that you can retrieve, use and update information about your customers. Information captured during your customers' interaction with your chatbots stored against people profiles with optional custom mapping, and in turn, information required is retrieved from profiles.
People is enabled by default when you start using any Infobip solutions. Make sure to keep an eye on attribute value types when setting up custom mapping as some may be incompatible with each other, for example, the system will not know how to match a text field to a boolean. See the section on Attribute Mapping for guidelines.
Create a People chatbot
Follow the steps below to set up a simple People enabled chatbot.
- To start using People in chatbots, drag the People element into a dialog in the chatbot builder.
- Once added, select it and define the required action to perform when end users get to this stage. The chatbot can either get information from People or post information (create/update) to People.
- Next, define your contact information attribute that you are launching your search query against. This can be a standard channel-specific attribute already stored in People, or a custom Answers attribute. By default, this is set
- For custom attributes, you will need to set up field mapping between Answers and People so the system knows how to handle them. Use the +ADD ATTRIBUTE MAPPING option to start mapping cross-solution attributes to each other.
NER attribute types and MO attribute types can only be mapped to corresponding text type People attributes.
- The next step is to add a condition to tell the chatbot what to do next with the response. To do so, pull the Conditions element into the dialog and set the attribute to lastPeopleStatusCode.
- Set the operator as required and provide the status value below. Status can either be SUCCESS, FAIL, VALIDATION_ERROR. For example, if a provided email does not match that person's email stored in People, you can send them to a signup dialog using People.
If you are using List attributes, this will by default update lists with new values. You can change this behavior by using the overwrite option in mapping settings. Use this option to replace lists completely with the newly provided values. List attribute overwrite is only available when creating or updating profiles.
The following logic applies when you are using the Get information action type (People to Answers):
Text and Gender types in People can be mapped to Text type in Answers
Decimal number and Whole number types in People can be mapped to Number type in Answers
True/False type in People can be mapped to Boolean type in Answers
Date and Date Time types in People in People can be mapped to Date type in Answers
List of objects type in People can be mapped to List type in Answers
The following logic applies when you are using the Create or update person profile action type (Answers to People):
Text, Phone number, Location, URL, and Email types in Answers can be mapped to Text type in People
NER and MO attributes in Answers can be mapped to Text type in People
Boolean type in Answers can be mapped to True/False type in People
List type in Answers can be mapped to List of objects type in People