Integration

Cordic integration.

Keep the telephony discipline Cordic is good at. Add the web, app and WhatsApp channels it isn't.

Cordic operators rarely have a dispatch problem β€” they have a channel problem. The phone flow works, IVR takes repeat journeys cleanly, and dispatchers know the screens. What is missing is a booking website that converts, a rider app from this decade, and WhatsApp booking for customers who will never install anything. Our Cordic connector adds those without touching the call flow.
  • Booking create, amend and cancel into Cordic
  • Job status feed for passenger tracking and notifications
  • Caller ID, IVR and repeat-journey recognition untouched
  • Account client, cost centre and rate-card mapping
  • Browser-based β€” no additional on-site hardware
  • WhatsApp booking and driver confirmation as extra channels
  • Historical import if you later replace Cordic entirely

What the connector covers

Bookings from the Limozoft website, passenger app, WhatsApp bot and corporate portal are written into Cordic with the correct rate card, vehicle class and account reference. Status events return to Limozoft so passengers get tracking links and driver-assigned messaging regardless of which channel the job came from.

Your telephony stack is deliberately left alone. SIP integration, caller lookup and IVR auto-booking continue exactly as they do today β€” you are adding channels, not replacing the phone.

Pricing and contract notes

Limozoft: flat per-vehicle monthly, connector included, no per-trip fee. Current UK figures are on the pricing page.

Cordic: quoted per fleet with no published list pricing, commonly including licence, telephony/hardware and support lines, on a multi-year agreement. Before planning any integration or migration work, confirm your renewal date, notice window and what a full data export in CSV would include.

If replacement rather than integration is the question, see our Cordic alternative comparison.

Setup timeline

Day 1: access and credentials confirmed. Day 2: rate cards, zones and account clients mapped. Day 3: test bookings across web, app and WhatsApp, including cancellations. Day 4–5: live parallel run with the phone flow unchanged throughout.

Frequently asked questions

Does Limozoft integrate with Cordic?+

Yes. We connect to Cordic through its booking interface and, where telephony is the priority, alongside your existing SIP/IVR stack. Bookings created in Limozoft dispatch through Cordic and job status flows back for passenger tracking and notifications.

Will I keep caller ID and IVR booking?+

Yes. Caller-ID lookup, IVR auto-booking and repeat-journey recognition sit on your telephony layer and are unaffected. Limozoft adds web, app and WhatsApp channels alongside the phone, it does not replace your call flow.

Do I need on-site hardware for the integration?+

No. Limozoft is entirely browser and mobile based. If your Cordic deployment uses an on-site server it keeps running as-is; the connector reaches it over your existing network or VPN.

What are the contract implications?+

Cordic agreements are typically multi-year with a defined notice period. An integration does not change that, but if a full migration is the eventual plan, map your renewal date first so the two do not collide.

Is the Cordic connector charged separately?+

No. It is included in the flat per-vehicle Limozoft monthly price. Any charges on the Cordic or telephony side remain with those suppliers.

Add modern booking channels to your Cordic setup.