Each service under BiP Discover serves national brands, TV shows, celebrities, public and private organizations, SMEs, and small user groups. Through services you can send bulk:
and receive messages from BiP users or communicate 1:1. TES is the environment that exposes these BiP capabilities through an API. Using this API, service owners can listen to all events/messages sent to the service and send any message to users based on their flows. For those who prefer a GUI instead of an API to send/receive messages to users/followers, the BiPUssu Panel is provided. The Panel is built on TES API and opens BiP capabilities to services via GUI.
Beyond sending/receiving messages, BiPUssu Panel leverages REX to return predefined static or dynamic data for commands when users message the service. Dynamic data requires programmatic integration with the source system; REX provides APIs for this. In the Panel, definitions are made under Commands, Content & Tag Management, Bot Management, or System Messages. REX uses these definitions to respond to users messaging the service. A service owner may both use REX’s response ability and integrate TES API. If a rule/content/bot exists for an incoming message, REX returns the mapped answer; otherwise it forwards the message to the service owner’s external WS URL. That WS must be TES API–integrated. This is partial REX usage.
In the Panel, bots can be written in AIML. Bots create dialogues based on the user’s input. REX manages bot execution and sends the resulting reply back to the user.
In the Panel, REX manages sending defined content to the user who messages the service. If “External Link” is selected as the response, REX forwards the user message to the External Link URL using the defined interface and returns the synchronous reply to the user.
REX manages sending system messages defined in the Panel to users interacting with the service.
REX manages sending tagged static content defined in the Panel to users messaging the service.