Messaging Entries are specifying configuration details between Nimbus services and an external instant messaging service. They are applied to Modalities Service Settings, allowing to extend your service's Instant Messaging capabilities with further communication channels.
✅PRECONDITIONS
💡The current implementation relies on https://www.twilio.com/ as external service. To set up this configuration entity correctly, you need:
- A working Twilio account.
- A configured Nimbus Provider Connector, which handles the authentication with the external Twilio Conversations service.
- The
Service SIDfrom your Twilio Conversations service1, which is needed for later mapping to a Nimbus service.
1🔎 More details can be found under Use Case - Setting Up Instant Messaging, following the WhatsApp / SMS setup instructions accordingly.
| 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: |
Messaging Entries in your Service Settings
✅ Follow-up action: Messaging Entries are required for your first (customer facing) service. They take effect once applied in your Modalities Service Settings. For services acting as further transfer targets, “Messaging Entries” are optional, as long as your first service has the configuration set up.
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.
💡Consideration for multi-modal services: Even if you intent to handle multiple integration channels (WhatsApp/SMS/RCS) by the same Nimbus service, we recommend to split the Service SID on Twilio's side to have a clear distinction. You can then create multiple Messaging Entries in Nimbus and assign them individually - per channel - in your Modalities Service Settings. This allows you to specifically disable one communication channel of a service without affecting the other.