Live Chat, Telegram Bot & AI Support Assistant

Request chat

One conversation per file, nothing lost in WhatsApp

Customer and tuner talk directly on the request, questions, photos, clarifications, and the whole thread stays attached to the job forever. Deliver the tuned file right in the conversation: a chat attachment becomes a versioned revision, logged and downloadable from the customer’s file page, never lost in a thread.

• Live thread on every file request, customer ↔ your team
• Attach a file in chat → delivered as a versioned revision
• Unanswered messages pulse a chat badge on the request queue
• Live conversation counter next to the bell, on every page

Telegram bot

Your portal, in your team’s pocket

The built-in Telegram bot puts the queue where your tuners already live. New-request alerts land in the team chat, sensitive alerts go to per-tuner DMs, and staff can act without opening the portal. Customers can link their own Telegram too and get their updates there.

• New-request & status alerts in your team chat
• Staff commands, including vehicle lookup by number plate
• Per-tuner DM channel for sensitive alerts
• Customers link their account and receive updates on Telegram
• One-click webhook diagnose & re-register from the admin

AI support

An assistant that knows your answers

Switch on the AI support assistant and customers get instant answers around the clock, grounded in the knowledge base you curate: your procedures, your prices, your policies, your tone. It’s off by default; you enable it when your knowledge base is ready, and your team keeps full visibility of the conversations.

• Chat assistant for customers and staff alike
• Answers from your knowledge base, not generic AI
• Off by default, one toggle in the Settings Hub when ready
• Uses your own AI key, so you control cost and usage

Messages

Every conversation in one place, and unread means unread by you

Job chats, support tickets, sales enquiries and conversations coming in from your sub-dealers all arrive in one inbox. You answer from the row you are looking at, the conversation opens where you clicked, with the message you are replying to still above the box, so you are never answering something you cannot see.

Read is per person. What one member of staff has read stays read for them and nobody else, so a shop with three people on the desk does not have one of them quietly marking everyone else’s work as seen.

• One inbox: job chats, support, enquiries, sub-dealer conversations
• Reply inline from the row, no second page, no lost context
• Unread is counted per person, not per shop
• Newest first, and what needs a person still says so on the row
• One search box: job number, plate, VIN, customer, or something that was said
• Finish a conversation and it files itself; a new message brings it straight back

Delivery

You can see what happened to what you sent

One tick when the message leaves, two when it reaches the other side, two in blue when it is read, small, in the corner, with the exact times when you hover. It only ever says what it knows: a message with no delivery yet shows one tick and never two.

You can answer with a file without leaving the list, a datalog, a photo, a screenshot, with or without a covering sentence. Handing over a finished tuned file still happens on the request itself, where the delivery and the billing live.

• Sent, delivered and read, with exact times
• Attach a file straight from the row
• Every lane behaves the same way, including the archive

Floating chats

The conversations that follow you around the portal

A floating panel sits beside every page with the conversations that need a person, newest first. It holds still while your pointer is over it, so on a busy day a row cannot slide out from under your click and land you in the wrong customer’s conversation.

Each member of staff decides for themselves whether the floating chats follow them, a tuner who wants a quiet screen turns them off without affecting anyone else.

• Follows you across the portal, on every page
• Stays still while you are pointing at it
• On or off per person, not per shop
• Sub-dealer conversations reach it too, labelled with whose customer they are

Waiting on you

A number in the header that agrees with the list underneath it

The chat button in the top bar carries a count of the conversations waiting for a reply, and opening it shows those conversations. Header, badge, floating panel and reminders all answer the same question, so the number you glance at is the work that is actually there.

A row where a customer is waiting carries an amber ring you cannot miss, with the car, the reference and what was said already on it, enough to decide whether to answer now without opening anything.

• One definition of “waiting on us”, everywhere in the portal
• The car, the job reference and the last thing said, on the row
• The ring alone carries the signal when animation is switched off

When nobody is at the desk

The assistant answers, and hands over when it should

Out of hours the support assistant answers from the knowledge you curate, and your team can take the conversation over mid-sentence at any point. If anything goes wrong while it is working out a reply, the conversation is handed to a person and flagged for you, a customer’s question is never met with silence.

• Take over mid-conversation, any time
• A failure hands over to a person instead of going quiet
• Photos from a phone are resized and read, not refused
• A refusal says which refusal it is, on screen

Fault codes

It understands a code a customer types

A library of more than twelve thousand fault codes sits behind the assistant, so a customer who writes a code in a message gets an answer about that code rather than a request to rephrase. Codes a customer gives when they raise a job are captured against your own code list at the moment the request is made, including on jobs that finish automatically, where nobody reads the notes.

• 12,000+ fault codes behind the assistant
• Codes captured from the request itself, not only from notes a person reads
• A list an engineer has chosen by hand is never overwritten

On your own website

Live chat on your website, answered from the same inbox

The chat button can sit on your own website as well as inside the portal, and every conversation from it arrives in the same Messages inbox as everything else. The button is a moving orb in your portal's own accent colour, with a text-size control for anyone who needs it bigger and one click to close all chats.

• Live chat on your own website, into the same inbox
• The chat button in your own colours
• Translation where conversations are read
• Mark a message as important; see a job's fault codes beside the conversation

An assistant that knows your shop

It knows what you sell, and what customers can do themselves

The support assistant is given the services your shop actually sells, so it confirms and explains them instead of passing every question to a person. It tells customers what they can do on their own, upload a file, top up, download a finished file, book a slot where your diary is on, and answers "how long on my file?" from the live status of their own orders.

• Answers from your own list of services
• Live order status by request number or registration
• Books appointments where the diary is on, confirming first
• The same knowledge on Telegram as on the website