Messaging Entries are the binding element between Nimbus services and an external instant messaging service. They are applied within Modalities Service Settings as part of the Use Case - Setting Up a WhatsApp Integration in Twilio.
âś…PRECONDITIONS
đź’ˇTwilio Integration dependency: The current implementation is limited to https://www.twilio.com/ as vendor. To set up this configuration entity correctly, you need:Â
- A working Provider Connector, which handles the authentication with the external messaging service.
- The
Service SIDfrom your Twilio integration service, which is needed for later mapping to a Nimbus service.
🔎Good to know: Configuration of “Messaging Entries” is required for your “initially receiving” front desk service. For other services acting as transfer targets, “Messaging Entries” are optional.Â
For example, there can be an IVR service A which has the Messaging Entry and WhatsApp configured, then transfers to other Nimbus services B and C, which are not supposed to be contacted directly. Service A acts as a “proxy” and therefore, services B and C do not need this integration configuration.
| Field | Description |
|---|---|
| Name | The name of the Messaging Entry. |
| Organization Unit | Organization Unit placement of the Messaging Entry. |
| Provider Connector |
Provider Connectors are the configuration that will connect the Nimbus Chat Integration into other services. The choice depends on the “Organization Unit” picked above, listing available Provider Connectors up to the root based on selected OU. |
| Service SID |
A unique value as defined by the API of the chat integration. Currently supported are the Twilio integration services 🔎From the Twilio API Documentation: Service-Scoped Notification
đź’ˇExample for a valid SID Â |