Taxi and private hire

Autocab customisation: what you can change.

A controller may move between booking references, pickup details and account names dozens of times an hour. On Autocab pages that open in Chrome, small layout changes can make those details easier to pick out.

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.

Ideas to try

Small requests for a clearer working day

Start with information already visible on your page. These examples are possible requests; check the result in the preview before keeping it.

  • 01

    Make the pickup time and address larger in the booking list

    Put the journey details the controller reads first in clearer type.

  • 02

    Add alternating row shading to the bookings table

    Follow a single booking across a wide list more easily.

  • 03

    Use a stronger border around the account name when one is displayed

    Distinguish account details without changing how the fare is processed.

  • 04

    Keep the booking list's column headings visible when I scroll

    Retain context when working through a long shift's bookings.

Ready-made changes related to these ideas

These general browser tools use the page elements your software exposes. Read their requirements and preview them on a suitable screen.

Custom Autocab screens, automations or a developer?

The right approach depends on what you want to change. Use Autocab settings for features the product already provides, and Tweaksy for small changes on an accessible browser page.

Browser customisation

Modify the screen you work with

A request such as “Make the pickup time and address larger in the booking list” 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.

Workflow automation

Know what needs the platform

Autocab automations such as booking consolidation and driver allocation belong to the dispatch platform. Tweaksy focuses on the browser view: for example, making an existing booking status easier to notice. A clearer status label does not create, allocate or update a booking.

Developer work

Connect systems or add new capabilities

For custom Autocab software that exchanges booking or account data with another system, discuss the integration with Autocab and a developer. For a change to text size, spacing or a visible table in Chrome, a browser customisation may be enough. First check whether the screen is a web page or an installed client.

Explore Autocab's official options ↗

A small change, ready for your team

  1. Choose one screen

    Open an accessible Autocab web page in desktop Chrome. Start with a simple change to text, spacing or a visible list.

  2. Describe and preview

    Describe the change in your Tweaksy account. Build it with the extension and check the preview in the original tab.

  3. Approve and share

    Approve the exact version to enable it. Your other logged-in computers receive it when they sync, on matching pages.

Questions about Tweaksy and Autocab

Which Autocab screens can I use?

Applies only to Autocab pages opened directly in desktop Chrome. Installed dispatch clients, driver and passenger apps, map internals and automatic job allocation are outside this page's examples.

Can I modify Autocab without a developer?

For a small change to an accessible browser screen, you can describe what you want in plain English and preview it with Tweaksy. Custom Autocab integrations, new stored fields and background workflows need the product's own configuration or developer tools. Start with the browser requirements above.

Are these ready-made integrations?

These are ideas for changes to request on a browser page, not prebuilt Autocab integrations. The result depends on the page layout, information currently visible and your browser permissions. Preview each change on your own screen.

What information is used to build a change?

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.

Does this replace Autocab settings or permissions?

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.

What happens when Autocab changes its layout?

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.

Can I use it with colleagues?

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.

Start with one screen and one useful change.

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.