VibeBack is the layer between your product and the people using it. Drop a single script tag on your site and you get one small widget that quietly does a lot: it collects feedback, answers questions with an AI chatbot trained on your own knowledge base, hands off to a human when the answer isn't there, catches JavaScript errors before anyone reports them, and — with Anybody Here — actually performs tasks on your site when a visitor asks. Behind that widget sits the whole back office: a full helpdesk with SLAs and automations, a live chat inbox, browser-to-browser voice calls, error triage that turns crashes into developer tasks, a knowledge base, and an API for anything we haven't thought of yet. Everything below is running today. Every screenshot is the real product with real data — nothing staged.
Catch what people actually think, while they are still on the page
Most feedback never reaches you — someone hits a problem, shrugs, and leaves. The widget puts a way to tell you right there on the page, and everything that arrives is sorted for you automatically: bugs separated from feature requests, duplicates grouped, and a category and sentiment attached before anyone on your team reads it.
- Bugs, feature requests, questions and praise are classified on arrival — no manual triage queue
- Repeat reports of the same issue are grouped so you see how many people hit it, not fifty copies
- Every submission carries the page, browser and a replay of what the person did beforehand
A chatbot that answers from your knowledge, not from guesswork
Point it at your knowledge base and it answers questions using what you have actually written, citing the article it used. When it does not know, it says so and offers a human instead of inventing an answer. You control its name, its greeting, its tone, and how far it is allowed to go before handing over.
- Answers are grounded in your own articles, with the source shown to the customer
- Replies in 48 languages, matching the script the customer wrote in
- Hands off to a live agent the moment it is unsure — no dead ends
Anybody Here — the widget does the task, not just describes it
Answering "how do I add a domain?" with instructions is fine. Actually adding it is better. Anybody Here lets a visitor ask for something in plain language and then performs it on your site, in their browser, in front of them — filling the form, picking the options, and pausing for confirmation before anything that matters.
- Map your site once and VibeBack works out what can be done on each page
- Matching is deterministic first — an AI key is optional, not required
- Anything risky asks for confirmation, and you set the ceiling on what it may do unattended
One inbox for every conversation, with the AI helping your agents too
When the bot hands over, the conversation lands in a shared inbox with everything the agent needs already attached — the page the person was on, their history, and the bot exchange so far. The same AI that talks to customers also drafts replies, suggests knowledge base articles, and translates in both directions while the agent types.
- Suggested replies and relevant articles appear alongside every conversation
- Real-time translation both ways, so your team answers in the language they know
- Conversations route to the right team automatically, with collision detection so two agents never reply at once
A proper helpdesk, not a list of unanswered emails
Anything that needs following up becomes a ticket — from the widget, from chat, from email, or raised by your team. Response and resolution deadlines are tracked against the business hours you set, work is assigned by the rules you choose, and the statuses and priorities are yours to name rather than ours.
- SLA policies with escalation that actually fires — reassign, raise priority, or notify a manager
- Assignment by round-robin, least-busy or skill, and an option to claim on first open
- Your own statuses, priorities and ticket types, plus custom fields on the forms
Find the crash before a customer bothers to report it
The same widget quietly watches for JavaScript errors, failed requests, broken assets and outages, and captures each one with the stack trace and the trail of clicks that led there. Upload your source maps and minified builds turn back into readable code. Most of what you see here, nobody ever filed a ticket about.
- Full stack traces, breadcrumbs and browser context on every capture
- Errors grouped by cause, with a count of how many people hit each one
- Source map support so a minified bundle points at your real file and line
From a customer complaint to a developer task, without the retyping
A bug report or a captured crash becomes a task a developer can claim and start, with the reproduction details, the affected pages and the original report already attached. Push it on to the tools your engineers already live in, so nobody is copying context between two systems by hand.
- A queue developers can claim from, prioritised by severity and how many users are affected
- The original submission, stack trace and session replay travel with the task
- Forward automatically to your existing engineering tracker
Talk to customers in the browser — no phone number needed
Some things are faster said than typed. A visitor can call your team straight from the widget and an available agent picks up in their browser — no dial-in, no app, no telephony account required to start. If you do run a call centre, connect your existing provider and the same workspace handles queues, recordings and campaigns.
- Browser-to-browser voice, with the conversation and customer already on screen when the agent answers
- Every call logged with duration, outcome and who handled it
- Bring your own telephony provider when you need real phone numbers, IVR and queues
Make it look like your product, not like ours
The widget is the part your customers actually see, so almost all of it is yours to change — theme, colours, logo, position, size, the launcher button, even the greeting. Start from a preset, watch a live preview update as you type, then copy one line of code. Every site you run can look and behave completely differently.
- Six starting themes, then full control of colours, shape, logo and placement
- A live preview beside the settings, so you see the real widget as you edit
- Per-site configuration — different look, bot, routing and team for each domain
Connect it to whatever you already use
Customers do not only talk to you on your website. Connect WhatsApp, Slack, Telegram, Teams, Messenger or email and those conversations land in the same inbox as everything else. For anything we have not built, there is a documented API and outbound webhooks so your own systems can read and write the same data.
- Messaging channels feed into the same shared inbox as widget chat
- A full API with scoped keys for reading and creating anything you can see in the app
- Webhooks so your systems hear about new feedback, tickets and conversations as they happen
One place to see how all of it is going
Feedback, conversations, tickets, errors and calls all land in the same workspace, so the dashboard is a real picture rather than a slice. Invite your team, give people roles that match what they actually do, and add as many sites as you need — each with its own settings, but all visible from here.
- Live counts across every connected site, with trends over time
- Fourteen ready-made roles, scoped so people only see what they should
- Add unlimited domains, each with its own widget, bot and team
Also in this release
More that ships with 1.0, grouped by area.
Paste a single line before your closing body tag and the widget appears. No SDK, no build step, no framework requirements.
Your feedback, conversations and customer records stay in your workspace. Bring your own AI keys if you prefer; nothing is shared between companies.
Fourteen ready-made roles from Agent to Finance Manager, each scoped so people only see the customers, tickets and conversations they should.
The chatbot detects and replies in 48 languages, including romanised ones like Hinglish, and mirrors the script the customer wrote in.
Run VibeBack across as many domains as you like, each with its own widget look, bot behaviour, routing and team.