Next4biz CSM connects to your core systems such as ERP, CRM and OMS (SAP, Oracle, Logo, etc.) through APIs and web services, and to communication channels and identity systems through configurable integrations added from the settings screen.
Last updated:
Integrations can be built by your own teams, your partners or Next4biz partners.
Native omnichannel connectivity for live chat, WhatsApp, e-mail, call centers, social media, review platforms and marketplaces. Everything is captured into a unified customer conversation.
Enterprise identity support with SSO (SAML 2.0 / OAuth2 / OpenID Connect) and LDAP/Active Directory. Optional SCIM provisioning for automated user and group sync.
Bi-directional integration with core systems such as ERP, CRM and OMS (SAP, Oracle, Logo, etc.) via REST APIs, web services and webhooks. Customers, accounts, transactions, requests, policies and orders are kept in sync, so agents and bots always work with live context.
Embed Next4biz components (self-service, notification views, chat) into your portals and applications with iFrame/JS. Your own applications can also be embedded inside Next4biz and take parameters.
Ready-to-use APIs for Power BI, Tableau and Qlik to feed your enterprise BI layers.
SDKs and ready UI components for in-app self-service and chat; the same experience across web and mobile. An SDK that contains the Next4biz CSM API methods is also provided as a NuGet package.
No code is written. An administrator adds the application from Settings > Integrations > Applications.
On the call center side, Next4biz works with CTI-enabled cloud and traditional switchboards.
For the full channel picture, including marketplaces and review platforms: Omnichannel page →
Your application inside Next4biz
Your web applications are embedded inside Next4biz as an iframe and take parameters: the details of the customer on screen are added to the address, and the application opens for that customer.
Next4biz components in your portal
Self-service, notification views and chat components are embedded into your portals and applications with iFrame/JS.
Your organization's own systems, such as ERP, CRM, OMS or an in-house application (SAP, Oracle, Logo, etc.), connect this way.
Systems such as ERP, CRM and OMS (SAP, Oracle, Logo, etc.) connect to Next4biz through web services. Agents reach the data in your own systems without leaving the Next4biz screen; queries go to your organization's SOAP or REST web services.
Customer lookup
The agent searches for the customer in Next4biz; the search runs on your web service.
Inventory lookup
Records such as orders, subscriptions, policies and accounts are listed from the external source on the case screen. Lookups can be chained: an order is selected first, then the products in that order are listed.
Records looked up
The CSM REST API works with JSON and XML. The Next4biz CSM, CRM and BPM APIs are documented on the developer site.
The most common uses of the API
When an event occurs in Next4biz, the web service registered for that event is called. If no service is defined, nothing happens.
Assignment, escalation, reopening and closing are among the other events that can be selected.
Example uses
An SDK that contains the Next4biz CSM API methods is provided as a NuGet package.
SDKs and ready UI components for in-app self-service and chat.
Ready-to-use APIs for Power BI, Tableau and Qlik.
Support for message brokers such as Apache Kafka and RabbitMQ.
The integration is set up once. Business teams then use this data in workflows, forms and screens without writing code. No-code page →
Yes. Core systems such as ERP, CRM and OMS (SAP, Oracle, Logo, etc.) connect to Next4biz in both directions through REST APIs and web services. Data such as customers, orders, products and policies is used on the case screen and in workflows.
With core systems such as ERP, CRM and OMS through APIs and web services; and with WhatsApp, social media, marketplaces, SMS and e-mail providers, softphone applications, CRM systems and authentication through configurable integrations added from the settings screen.
Configurable integrations are added from the settings screen. Messaging: WhatsApp. Social media: Facebook, Instagram, X (Twitter) and their DMs, Şikayetvar, Somera, Connexease. Marketplaces: Trendyol, Hepsiburada. CRM: Salesforce, Zoho, Zendesk Sunshine. E-mail: Exchange, Euromessage, Mailgun, Related Digital. Softphone: Alotech, Ziwo, Voyce, Tegsoft, Sonitel. Authentication: SAML, OAuth2, LDAP. SMS: Posta Güvercini, Infobip, Mobildev, Message34, Dataport SMS, Turatel SMS, Smart SMS, Jet SMS, İletişim Merkezi, Verimor, TTMesaj, Codec, Mutlucell, NetGSM, Related Digital.
A configurable integration needs no code; an administrator adds the application from Settings > Integrations > Applications. Organization-specific systems such as ERP and CRM are connected with APIs and web services: the REST API, the SDK, event management and lookup services are for this.
Your own teams, your partners or Next4biz partners can build them. The API documentation is public at developers.next4biz.com.
Yes. With LDAP authentication, the user's identity is verified on your organization's LDAP server. LDAP and Active Directory are supported.
Yes. SSO is supported with SAML 2.0, OAuth2 and OpenID Connect. Optional SCIM provisioning is available for automated user and group sync.
Yes; it is called event management. When an event occurs in Next4biz (a case is created, assigned, escalated or closed, for example), the web service registered for that event is called. If no service is defined, nothing happens.
On the developer site at developers.next4biz.com, open to everyone. The Next4biz CSM, CRM and BPM APIs are documented there. The CSM REST API works with JSON and XML.
Yes. An SDK that contains the Next4biz CSM API methods is provided as a NuGet package. There are also mobile and web SDKs for in-app self-service and chat.
Yes. Your web application is embedded inside Next4biz as an iframe and takes parameters. The details of the customer on screen are added to the address, and the application opens for that customer.
From your own systems. In customer lookup, the search runs on your web service. In inventory lookup, records such as orders, subscriptions, policies or accounts are listed from the external source on the case screen. Queries go to your organization's SOAP or REST web services.
In a 30-minute meeting, let's clarify which of your systems connects in which way.