We integrate.
We do not replace.
Your phone system stays your phone system. Your core banking, ERP and CRM stay the systems of record. The engine reads from them at the moment of the conversation and writes the outcome back before it ends, which is the whole difference between an answer that is true and an answer that merely sounds true.
Grounded answers need
a real connection.
An assistant with no integration can only generate. An assistant wired to your system of record can state a balance, a premium or a delivery date and be right. Everything below is something we would actually wire, not a logo wall.
Telephony & contact centre
The engine answers calls on the number and the platform you already publish. Your routing, your queues, your reporting and your agents stay exactly where they are.
SIP trunking or a SIP connection into your existing PBX, with the engine reached from your current IVR as one more destination. Where you use a hosted contact centre, we connect at the platform's own integration layer instead.
Asterisk / FreePBX
SIP connection into your existing dial plan
Avaya
SIP trunk or session manager integration
Cisco Unified CM
SIP trunk integration
Genesys
Connected at the platform's integration layer
3CX
SIP connection
Local IP telephony and SIP providers
Standard SIP, BTRC-licensed carriers
Twilio / Plivo
Where an international number or cloud trunk is in use
Messaging & social channels
The same brain that answers the phone answers the message channels, so a customer gets one answer wherever they ask, and a conversation can move channel without restarting.
Official platform APIs throughout. WhatsApp runs on the Business Platform through a BSP, Facebook and Instagram on the Messenger and Instagram Graph APIs. We do not use unofficial automation of personal accounts, because it breaks and it gets numbers banned.
WhatsApp Business Platform
Through a BSP, template and session messaging
Facebook Messenger
Messenger Platform API, including comment-to-DM
Instagram Direct
Instagram Graph API
Website chat widget
Embedded on your own domain
In-app chat
Through our API, into your existing mobile or web app
SMS
Local aggregators for OTP, confirmations and reminders
Viber / Telegram
Where you already run an official business presence
Core systems & ERP
This is what separates a grounded answer from a generated one. Every figure the engine states, a balance, a premium, a stock level, a delivery date, is read from one of these at the moment of the conversation.
Through whatever the system exposes: REST, SOAP, a middleware or ESB layer you already operate, a read replica, or a database view scoped to exactly the fields needed. For core banking we almost always connect through your existing integration layer rather than the core directly.
Core banking platforms
Through your middleware or ESB, read-scoped
Policy administration systems
Premium, status, nominee, maturity lookups
SAP
REST, OData or an integration layer
Oracle ERP
REST or integration layer
Microsoft Dynamics 365
Dataverse and Web API
Odoo
XML-RPC and REST
Tally
Via connector or export, depending on deployment
Custom and in-house ERP
REST, SOAP, database view or file exchange
CRM & ticketing
Every conversation ends somewhere. Outcomes, cases, complaints and promises-to-pay are written back before the call ends, so your team works from one record rather than a separate AI log.
Native APIs with webhooks both ways. The engine creates and updates records, attaches the transcript, and reads existing context so a returning customer is not treated as new.
Salesforce
REST API, case and activity creation
Microsoft Dynamics 365
Web API
Zoho CRM / Desk
REST API
HubSpot
REST API
Freshdesk / Freshservice
REST API
Zendesk
REST API
Close
REST API
Custom CRM
REST, webhook or database integration
Payments
The engine confirms what is owed and sends a payment link. It never asks a caller to speak a card number, a PIN or an account credential, and it never captures one.
Official merchant APIs. The engine generates a payment link or reference against your merchant account and sends it over SMS or the message channel the customer is on. Settlement and reconciliation stay in your existing flow.
bKash
Merchant API, payment link generation
Nagad
Merchant API
Rocket
Merchant integration
SSLCommerz
Full gateway, cards and MFS
aamarPay
Gateway integration
Bank payment gateways
Through your acquiring bank's gateway
Courier & logistics
Delivery status does not live in your ERP, it lives with the courier. Without this layer, every 'where is my order' answer is a guess or a callback.
Courier APIs for both directions: live status lookup so the answer is current, and order booking so a confirmed order becomes a consignment without a human re-entering it.
Pathao Courier
Booking and live status
RedX
Booking and live status
Steadfast
Booking and live status
Paperfly
Booking and status
eCourier
Booking and status
Your own fleet
Through your dispatch system or a webhook feed
Data, identity & operations
The parts that make a deployment approvable: where it runs, who can see what, and how an auditor reconstructs a call six months later.
Deployment into your cloud tenancy or your own data centre, authentication against your existing identity provider, and logs and recordings written to storage you control with retention you set.
On-premise deployment
Your data centre, your hardware
AWS / Azure / GCP
Your tenancy, your region
Local Dhaka-based hosting
Where data residency requires it
Active Directory / LDAP
Staff authentication and role mapping
SAML / OIDC single sign-on
For the supervisor console
Object storage you control
Append-only recordings and transcripts
SIEM and log forwarding
Syslog or API, into your existing stack
The honest part of this page.
Integration decks usually imply every connection is clean. In Bangladesh many are not. These are the cases we expect to hit, and what we do about them.
Legacy systems with no API
A good share of core systems in Bangladesh expose nothing to integrate against. The honest options are a scoped read replica, a database view limited to the fields needed, a scheduled export, or a thin service built in front of the system. We will tell you which one applies before the scope is written, not after.
Couriers without public APIs
Not every courier publishes one, and a few that do are unreliable. Where live status cannot be read, the engine says the status is not yet available rather than inventing a delivery window.
Core banking access
We almost never connect to a core banking system directly, and would be concerned by a vendor who offered to. The route is your existing middleware or integration layer, read-scoped to the specific fields a call needs.
WhatsApp through official channels only
We use the WhatsApp Business Platform through a BSP. We do not automate personal or unofficial WhatsApp accounts. Those solutions break on every platform update and get business numbers banned.
Send us the system. We will tell you if it connects.
Anything with an API can be wired, and most things without one can be reached another way. If yours genuinely cannot, that is a better thing to learn in a diagnostic than three months into a build.