Integration is a permission question before it is a technical one.

The access checklist

Before anyone promises an integration, collect these answers from your software vendor and your own team. Missing answers are the most common reason integrations slip.

• Does the vendor publish API documentation, and for which plan?
• Who in your business can approve access and sign the vendor’s terms?
• Is there a test (sandbox) account, or only live data?
• Which records can be read, and which can be created or changed?
• Are there usage limits, IP restrictions or per-call charges?
• What data-protection agreement does the vendor require?

Four levels of integration

Integration is not all or nothing. Each level adds value and risk, so agree which level fits the workflow and the vendor’s rules.

• No connection: staff receive a structured request and enter it themselves
• Read: look up availability, order status or opening hours
• Write pending: create a request that staff approve inside the system
• Write confirmed: create or change a final record — used only where rules are clear and tested

Vendor fees exist — ask early

Some software vendors charge for API access, for a higher plan that includes it, for a partner programme or per request. Others include it. These fees belong to the vendor, not to the WhatsApp workflow, and they should be listed separately in any proposal so you can see the full cost.

Test on real request examples

Use a test account and a set of real (anonymised) requests: normal cases, missing fields, double bookings, cancellations and the vendor being unavailable. Agree what happens when the connection fails — usually the request is saved and passed to staff, and the customer is told a person will confirm.

Standards help, but do not guarantee access

Some clinical systems support interoperability standards such as HL7 FHIR, and many booking and commerce tools publish their own APIs. Support still varies by vendor, version and plan, so each system has to be checked individually. HumAI does not assume a connector exists for any named product; integration is scoped where your system allows it.

What happens without an API

A workflow can still remove most of the back-and-forth. The customer conversation collects and checks the details, and staff receive a complete, consistent request to enter or approve. Avoid workarounds that the vendor does not permit, such as automating its screens; they tend to break silently and can breach the vendor’s terms.