iCabbi customisation can start with the dispatch screen your controllers already use. Modify how visible vehicle details, booking channels and job statuses appear in Chrome, then review the change on the actual page. A custom iCabbi browser view can focus attention on the details your office reads most.
No card needed. Try 8 standard builds a month on our sample office page with one computer. A paid plan is needed for your own work sites, from £9.99 a month for two computers. Desktop Chrome. Cancel any time. See the office demo first.
Start with information already visible on your page. These examples are possible requests; check the result in the preview before keeping it.
Make an existing dispatch status easier to spot in the current list.
Read the person and vehicle together without changing either value.
Separate phone, app or account channels where those labels already appear.
Make the reference easier to select accurately during a customer query.
These general browser tools use the page elements your software exposes. Read their requirements and preview them on a suitable screen.
The right approach depends on what you want to change. Use iCabbi settings for features the product already provides, and Tweaksy for small changes on an accessible browser page.
A request such as “Give rows marked Unassigned a clearer outline” starts with information already visible. Tweaksy builds the change on that page for you to preview, then you can approve it for matching screens on your account.
If you are exploring iCabbi automations, start with the outcome you need. Tweaksy can help you request browser changes such as clearer Unassigned labels or more readable booking references. Creating bookings, allocating drivers, responding to events when the browser is closed or sending data to another service needs iCabbi's own capabilities or an authorised integration.
An iCabbi developer is useful when a custom project needs to exchange booking data, use webhooks or connect another system. iCabbi publishes API resources and asks customers to discuss planned development with its team before starting. For changes to the presentation of an existing Chrome page, describe the result to Tweaksy and check it on your screen; no API connection is implied.
Open an accessible iCabbi web page in desktop Chrome. Start with a simple change to text, spacing or a visible list.
Describe the change in your Tweaksy account. Build it with the extension and check the preview in the original tab.
Approve the exact version to enable it. Your other logged-in computers receive it when they sync, on matching pages.
Browse ready-made browser changes · See how Tweaksy works · Read how page information is handled
These suggestions concern iCabbi's browser pages in desktop Chrome. They do not extend to driver or passenger apps, dispatch algorithms, live vehicle telemetry or information absent from the loaded page.
For a small change to an accessible browser screen, you can describe what you want in plain English and preview it with Tweaksy. Custom iCabbi integrations, new stored fields and background workflows need the product's own configuration or developer tools. Start with the browser requirements above.
These are ideas for changes to request on a browser page, not prebuilt iCabbi integrations. The result depends on the page layout, information currently visible and your browser permissions. Preview each change on your own screen.
Creating a change uses your request and relevant page details, processed by Tweaksy and its AI service. Automatic filtering reduces sensitive information, but visible personal or business details can still be included. The privacy policy explains who handles your data and your choices. Try a demo or a page without confidential information first.
No. Tweaksy can adjust a page in your browser; it cannot add server-side fields, retrieve records you cannot access or change account permissions. Review any change affecting page behaviour before approving it.
A saved change may need rebuilding after a software update. Check it on the updated page, switch it off if needed and preview a revised version before approving it again.
Each desktop Chrome using Tweaksy needs the extension and a login to your Tweaksy account, within your plan's computer allowance. Approved changes sync to those computers. Managed browsers may require your administrator to allow the extension.
Try a clearer label, a larger reference number or a tidier list. Preview it, then decide what to keep.
No card needed. Try 8 standard builds a month on our sample office page with one computer. A paid plan is needed for your own work sites, from £9.99 a month for two computers. Desktop Chrome. Cancel any time. See the office demo first.
Product names belong to their respective owners. Tweaksy is an independent product made by OptiCab Ltd. Listing a product does not imply a partnership, endorsement or verified compatibility with every screen.