Connecting your systems
There is no fixed list of supported apps. You tell us the systems your business runs on, and the only real question is which of three routes yours takes.
The only question we ask is whether the system has an API. If yes, it is Route A. If no, it comes down to where the system runs — in a browser, or on a computer.
Route A — the system has an API
→ Direct connection.
We connect server to server using credentials you provide. Nothing is installed on anyone's computer, it runs whether or not a person is logged in, and it is the fastest and most reliable of the three.
Typically: WhatsApp, Google Calendar, Google Sheets, Stripe, most modern cloud tools.
Route B — no API, and it runs in a browser
→ Install a browser extension.
A browser extension on the machine of whoever uses that system. It reads and fills the same screens your staff already use, so the system itself needs no changes and its vendor does not need to be involved.
Typically: older web portals, marketplace seller centres, web CRMs with no public API.
Route C — no API, and it runs on a computer
→ Install BobCode on that machine.
For software that only exists on one machine in the office. BobCode is installed there and operates that software the way your staff do.
Typically: desktop accounting packages, on-premise ERP, local databases.
What we need from you
- The name of the system, and who inside your business uses it
- Whether your plan with that vendor includes API access. If you are unsure, we will check with them
- A test account or dev access, so we can confirm the route before anyone commits to a date
- For Route B and C: which machine it runs on, and whether that machine stays switched on
We confirm the route and the cost before you commit. If a system turns out to need Route B or C, that is named in your proposal rather than discovered halfway through the build.
Route B and Route C both need a machine that stays switched on and signed in — usually the one that system already runs on. Route A does not.
Frequently Asked Questions
Do you support [my system]?
Almost certainly, but by one of the three routes above rather than off a supported-apps list. Send us the name and we will tell you which route it takes and what it costs.
How long does an integration take?
Route A is usually days. Route B and C depend on how complex the screens are and how reliably the machine stays online — which is why we confirm the route in writing before you commit to a date.
What if the vendor changes their system?
Route A connections are stable unless the vendor changes their API. Route B connections read the screens, so a redesign can require an update — that maintenance is part of the retainer, not a new charge.
Up next
Taking payment in the conversation
The agent can collect payment in the same thread as the order, so the customer never moves to another channel.
Still need help?
Our team is available Mon–Fri, 10 AM–6 PM MYT (GMT+8).