Since 1.779.0, AB Support has gone from a product you could buy to one you can install in a couple of clicks — and its bot has learned to answer your customers from your own knowledge base, with sources. Along the way every AB product started writing to people in their own language, and became usable without a mouse.
AB Support is in Microsoft Marketplace
AB Support has a store listing of its own now, approved and live: get AB Support for Microsoft Teams. The subscription went on sale in 1.779.0; this is the app itself, so there is nothing to request and nobody to email. It signs you in with the Microsoft 365 account you already have, your first desk is created from the Home tab in seconds, and the included allowance — 500 customer transactions and 50 AI credits a month — needs no payment method.
The bot answers from your knowledge base
This is what AB Support was always for, and until now it only happened on the chat widget. Ask the bot a question in Microsoft Teams and it answers the same way.
- Ask it anything your articles cover. “What time do you close?” gets the answer, not a list of commands. Anything that is not a command is treated as a question for that desk’s knowledge sources.
- It shows its working. Every answer carries the article it came from, as a link you can open and check. You can always see what a customer was told and where it came from.
- It does not guess. When it cannot ground an answer in your own content it says so and points at help, exactly as it routes a customer’s question to your team rather than inventing a reply.
- The knowledge base now works in Japanese. Japanese and Chinese are written without spaces between words, and the search was treating a whole sentence as a single search term — so a Japanese desk answered nothing at all and quietly routed every ticket to a human. It searches properly now. Note that an article answers in the language it is written in: if you serve customers in two languages, write your articles in both.
The queue keeps up with you
- Tickets appear as they arrive. The inbox used to load once and never look again, so a ticket that arrived while you had it open stayed invisible until you reloaded — and inside a Microsoft Teams tab there is no address bar to reload from. New tickets and customer replies are pushed to any open inbox now, and there is a Refresh button beside Dashboard and Tickets for when you will not wait.
- Home is a worklist, not a scoreboard. It used to be three counters and a list of desks. It is now every ticket across every desk you belong to, ranked by who has been waiting longest on you, with the counters turned into filters over that list. The two failures that never showed up in a count — an exhausted allowance and an AI with nothing to answer from — are called out where you will see them.
- Desks tell themselves apart. A desk carries its own name and icon instead of being one of several called “AB Support”, a channel desk is named after its channel, and the desks list shows each one’s open and unassigned counts. Settings has the desk’s id, copyable, for anyone wiring it to the API or MCP.
- Anyone in the channel can open its desk. A channel tab used to admit only whoever added it; every other member of the channel hit a dead end. They join on first open now.
Your customers see their own language
The web chat widget and the hosted contact form were English no matter who was reading them — a Japanese customer got a Japanese answer inside an English window, under an English heading, in a field labelled Name. Both now follow each visitor’s browser language, in English and Japanese, and a site that serves one market can pin one with data-lang.
Everything writes to you in your language
A card, a digest or a bot reply is read by somebody other than whoever triggered it, and all of them used to be written in the sender’s language. Bot replies, Microsoft Teams cards, task reminders, the daily digests and the onboarding emails now resolve against the person receiving them. If your workspace is bilingual, each person gets their own.
Usable without a mouse
Lists, boards, Gantt bars, the Wiki tree and the AB Support inbox can all be driven from the keyboard now, and a screen reader is told what is happening rather than left to infer it from a highlight. Every dialog announces itself as one, toasts are read aloud, and the last two browser confirm() boxes — which do not work inside Microsoft Teams — are gone.
AB Sales
Home reads like a dashboard rather than one long column, so the pipeline, what needs you and what closed recently are visible together instead of in sequence.
One look across the products
AB Green is now the action colour everywhere, replacing the per-product blues that had drifted apart; text sits on one type scale with nothing below a readable floor; one icon means one action across all three products; and definition comes from borders rather than shadows. Nothing moved, but a great deal stopped being slightly different for no reason.
The quiet fixes
- Settings opens in a browser. AB Sales and AB Support settings were reachable only inside Microsoft Teams.
- Subtasks detach inside Microsoft Teams, not only on the web.
- Change history says what changed. Five fields were showing their internal names instead of their labels.
- MCP accepts what clients actually send. A mis-cased argument name used to come back as a confusing “project not found”.
As always, AB Projects, AB Sales and AB Support update automatically — nothing to install. If anything looks off after the new version lands for you, the team is only a message away.