The traditional way of sending messages within a company involves connecting REST APIs for each system involved in the process, which can be more than 10-20 systems. Additionally, automation must be programmed into the systems or as standalone applications, such as scheduling, reports, conditions, etc. This is a waste of time.
Bosbec presents a different approach. We offer a platform for automating messaging services. Instead of dealing with each system individually, you integrate the messaging service into an external workflow connected to your processes. It’s smooth and easy to do. You save a lot of time, and you can customize delivery times for individual recipients based on relevance, timeliness, and other functionalities.
In a workflow with automation, you can build a sophisticated messaging service tailored to your organization, plugging security holes without worrying about updates, maintenance, and unforeseen costs.
HubSpot, an example
For example, let’s see how this can be applied to one of the world’s most used CRM systems: HubSpot. The platform gathers all the software, integrations, and resources you need for marketing, sales, content management, and customer contact.
Users make selections based on what HubSpot calls Workflows. There is a fairly advanced OAuth process for generating high security when sending SMS to a Gateway from HubSpot. This OAuth 2.0 is implemented as a workflow in the Bosbec platform for high-security requirements. It is also necessary to automate the opt-out function and send the data back to the HubSpot opt-out list. If you buy a “regular” gateway, the advice is to create a project to manage the integration on, for example, Amazon.
To implement a service managing the opt-out and OAuth 2.0 process, someone has to create the project on, for example, Amazon – meaning a responsible person is needed to own and manage this process. If there were a provider who made this process a “ready-made” solution, that would be great – until something changes or another system needs another authorization process for sending messages. Then, you depend on that provider making its changes; otherwise, the process will stop working. On average, 10-20 systems need to send messages, and each process requires 2-5 adjustments that a standard service does not have. This becomes 20-100 small special projects that can be avoided by using Bosbec.
In Bosbec Workflow, the customer can always build this entire process integration and update the opt-out feature and the OAuth process—when anything changes, you change your workflow. Bosbec Workflow is a service where you can simultaneously make all the specifications needed for all systems.
If you want to learn more about integrating and automating your messaging service, don’t hesitate to contact us! To schedule an appointment, email support@bosbec.com.
