System integration
Connect customer requests to the systems your team already uses.
You do not need to replace working software to automate customer requests. HumAI first assesses how your booking, ordering, CRM or management system can be connected: what it allows us to read, which actions it allows, who can authorize access and what happens if the connection fails. Supported actions are agreed and tested before launch. Where no suitable connection exists, the workflow runs with staff approval instead. Integrations are available to scope; we do not claim a ready connector for any named system until it has been validated.
Meta Tech Provider · Official WhatsApp Business Platform
Connection levels
From no connection to approved actions
Staff-approved (no connection)
The workflow collects complete requests and your staff act on them in your system. It works from day one and is often the right start.
Read access
The workflow reads agreed information, such as availability, order status or stock, so answers reflect your system rather than a copy.
Write access for approved actions
The workflow creates or updates records, such as a booking request or an order, only for actions that are agreed, permitted and tested.
Failure handling
If the system is slow or unavailable, the request is kept and moves to staff. It is never lost or confirmed by mistake.
What happens without an API
Some systems offer no suitable connection. We then agree a staff-approved process, an export or a shared queue, and revisit integration later.
Who it’s for
Businesses whose customer requests finish in another system: a booking calendar, a POS, a store platform, a CRM, or a dealer or hospital system. These are the industries we have written journeys for.
Service scope
What is included
Your proposal sets out the scope, term, included usage, support and exit arrangements before launch. This card shows what the solution typically includes; additional channels and operating modules are assessed around your needs.
Included journey
- An assessment of your system’s documented connection options
- A written list of supported read and write actions
- Agreed permissions and who authorizes access
- Testing of each action on real request examples
- A fallback process for when the connection fails
- Monitoring of the connection after launch
Systems we assess
- Booking and appointment systems
- POS and ordering systems
- E-commerce platforms
- CRMs and lead systems
- Shared calendars or spreadsheets as a starting point
Languages
Integration does not change language coverage. Conversation languages are agreed as for any workflow: Arabic and English as standard, others tested before launch.
Your responsibilities
- Authorize access with your system vendor or administrator
- Provide a test environment or safe test records where possible
- Cover any vendor fees for API access or licences
- Tell us before changing the system version or configuration
Not included
- Building a new booking, POS or CRM system
- Actions your system does not support or permit
- Workarounds your vendor has not authorized
- Decisions you keep with staff, such as refunds or exceptions
Walkthrough
One integration assessment
Illustrative workflow; not a live customer record.
- 01 · Goal
A business wants WhatsApp booking requests to reflect real availability.
- 02 · Assess
The booking system’s documentation allows reading free slots, but not creating bookings.
- 03 · Agree
Phase one reads availability; staff create the booking in the system after the customer confirms.
- 04 · Test
Reads are tested on real examples, including a timeout, which sends the request to staff instead.
- 05 · Extend
If the vendor later allows booking creation, it is scoped and tested as a separate step.
How we work
Four stages, from real requests to monthly operation.
- 01
Map the requests
We map which requests end in your system today, what staff do there by hand and where mistakes happen.
- 02
Agree scope and measurement
We review the connection options, agree the read and write actions, permissions, staff approvals and fallback, and how success is measured.
- 03
Build and test on real examples
We build the connection and test every agreed action on real request examples, including failures, before customers depend on it.
- 04
Launch, operate and review monthly
We launch, monitor the connection, react to vendor changes and review it with you every month.
Honest limits
What this does not do
- We can only do what your system and your licence allow.
- Vendor changes can break a connection. Monitoring catches it and the fallback keeps requests safe, but some downtime can happen.
- Some vendors charge for API access or require their own approval.
- A confirmation is sent only after the system action actually succeeds.
FAQ
Do you already have a connector for my system?
We do not claim ready connectors for named systems. We assess your system’s connection options, then agree and test the supported actions. Integrations are available to scope.
What if our system has no API?
The workflow still works with staff approval: requests arrive complete and your team acts on them in the system. We can also look at exports or shared calendars, and revisit integration later.
What is the difference between read and write access?
Read access lets the workflow look up information, such as availability or order status. Write access lets it create or change records. Write actions are agreed one by one and tested before launch.
Is it safe to let the workflow write to our system?
Write actions are limited to what is agreed and permitted, tested before launch and recorded. Where a wrong action would be costly, staff approve before it runs.
Who pays for API access?
Any fees charged by your system vendor are separate from HumAI’s service and are listed in your proposal.
Do we need to integrate before we start?
No. Many businesses start with a staff-approved workflow and add a connection once the first workflow is working and the system’s options are clear.
Related solutions
WhatsApp automation
Our core service. Guided WhatsApp workflows that we design, build and run for you after launch.
Operations analytics
A management view of unanswered topics, ageing approvals and branch workload, scoped to the data you have.
Customer service automation
WhatsApp plus website chat, Instagram, Messenger and Telegram, with case routing, handover and a view of the workload.
How pricing works
Setup, monthly operation, usage and third-party fees, explained without numbers.
Which system do your requests end in?
Tell us what you use today and what staff copy into it by hand. We will assess what can be connected and what should stay with your team.
Talk to a person on our team about your workflow, without going through an assistant.