Help & Support
Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.
The AB Support Bot
The AB Support bot is for your team, not your customers — ask it a question and it answers from your desk's knowledge base with sources, check open tickets, see what is assigned to you, and pick the channel escalations land in.
Your Monthly Allowance: Transactions and AI Credits
AB Support meters two things each month — customer transactions and AI credits. What each one counts, where to watch what is left, the warning Home shows you at 80%, what happens when either runs out, and how Usage Packs add capacity.
Where an Escalated Ticket Goes
When the AI can't answer, it routes the ticket to CS, Tech or Product with a one-line reason and a draft reply. What routing is, what it isn't, and why a routed ticket still needs someone to claim it.
Filtering Tasks and Saved Filters
How task filters work in AB Projects: every condition the filter panel offers, saving a filter set you reuse, sharing a filtered view as a link, and why filters stick between visits.
Task Dependencies: Blocked By and Blocks
How task dependencies work in AB Projects: add predecessors from the task that is waiting, read the automatic Blocks mirror, understand why an unmet predecessor warns rather than blocks, and how an AI assistant can set dependencies over MCP.
Campaigns: Multi-Step Email Sequences
A campaign is an ordered sequence of emails the Agent sends a lead over time, stopping the moment they reply. Covers entry filters, steps and wait days, priority, what ends a sequence, and why nothing sends until a campaign exists.
Plans, Pricing, and Your Lead Allowance
AB Sales is priced by how many new leads you add, not by how many people use it. Your first 100 leads are free, a plan adds 1,000 new leads a month, and the allowance is shared across every workspace in your organization.
The AB Sales Bot: Chat Commands
Ask the AB Sales bot for your leads, pipeline, or customers — or create a lead — right from a Teams chat. All commands work in English and Japanese.
Importing and Exporting Leads (CSV)
Bring leads into AB Sales from a CSV file or export your whole lead list — including labels, funnel stage, and AI research. Covers the template, duplicate detection, and which columns import.
Your Personal Settings
Your personal AB Support settings — profile, language, timezone, and the opt-in ticket digest email — how they differ from a desk's admin-only settings, and why the digest has its own Save button.
Working the Ticket Queue
How to scan, filter, and work the AB Support ticket queue: new tickets appearing on their own, the inbox row signals, compact rows, long queues, quick filters and sort, saved filters, keyboard triage, Next ticket after resolving, and bulk actions.
Who Can See Your Tickets and Customers
Who has access to an AB Support desk's tickets and customers — desk membership is the rule, how you join depends on whether the desk is channel-linked or standalone, and one desk (or another AB product) can never see another's data.
AB Support Troubleshooting
Fixes for the most common AB Support snags — replies stopping altogether, no inquiry cards, email not syncing, the AI answering wrong, the web-chat widget not appearing, WhatsApp and SMS not arriving, and signing in on the web.
Installing AB Support
How to install AB Support from the Microsoft Teams store and create your first support desk — from the Home tab in seconds, or as a channel tab — then work that same desk in Teams, Outlook or a browser. Your customers never install anything.
Assigning Tickets to Your Team
How to assign a support ticket to a teammate so a real team can divide the work, plus how assignment differs from AI-vs-human handling.
Rating the AI's Answers
Customers can rate the AI's answers with a thumbs up or down; the score rolls up to a helpfulness percentage on your dashboard so you can track and improve answer quality.
Your Customer Store
Everyone who contacts your AB Support desk becomes a customer record, matched by email or phone number depending on the channel, so returning people bring their history. When one person arrives as two records, an agent can merge them. It's AB Support's own store, separate from the AB Sales CRM.
The AB Support Dashboard
A desk opens on an interactive dashboard — in Teams or the web app. Its metric tiles are clickable and open the ticket list filtered to exactly those tickets. Which tiles click through, which don't, and how to read the numbers.
Web Forms: Turning "Contact Us" into Tickets
A Contact us web form becomes a ticket; the reply is emailed to the visitor. Use the hosted form or POST your own to the endpoint — and note the mailbox it needs to reply.
Turning Support Email into Tickets
Connect your support mailbox so email becomes tickets and replies go back by email. Needs a one-time Microsoft 365 admin consent — here's the setup, and why mail takes a few minutes to appear.
The Web Chat Widget
The AB Support web chat widget — a chat bubble you embed with one script tag. How to add it, preview it, its options, the 11 languages it speaks, how to brand it with your own colour and launcher icon, and what visitors see.
AB Support Settings
Two things are called settings in AB Support: your personal settings (language, timezone, ticket digest) and a desk's admin-only settings (its name and icon, members, channels, statuses, knowledge sources, and its desk ID), reached from the gear inside the desk.
Knowledge Sources: How the AI Answers
The AI answers customers directly from the knowledge sources you point it at — this desk's own knowledge base, another workspace's wiki, or public help content — and cites them. It finds articles by meaning, so customers can ask in any language and still be answered from what you wrote.
Support Desks: Your AB Support Workspace
A desk is your AB Support workspace — its own tickets, customers and settings, independent of AB Projects and AB Sales. The two ways to create one, how to choose, and how to open it from Teams, Outlook or the web.
How a Support Ticket Works
How an AB Support ticket works: the AI answers first, then hands off to a human; plus the Needs us / Waiting on customer / Finished status categories, the suggested reply (including drafts from AI assistants), internal notes, the activity timeline, resolve reasons and Next ticket, and undelivered replies.
AB Support: Overview
AB Support is AI-assisted customer service your team works from Microsoft Teams, Outlook or a web browser — customers reach you by web chat, email, forms, WhatsApp and SMS; tickets land in one queue. The hub for every AB Support help page.
Who Can See What? (AB Sales)
Visibility in AB Sales is workspace-based: every workspace member sees that workspace's whole pipeline, each workspace's data is isolated, and roles (Owner/Admin/Member) control management, not visibility.
AB Sales Troubleshooting
Answers to the most common AB Sales questions — an empty Contacts tab, being unable to add leads, missing workspaces, email that won't send, sample data, and sign-in issues.
Labels: Tagging and Segmenting Leads
Labels are colored tags you attach to leads to segment your pipeline by temperature, size, or industry. Every workspace ships with a default set, the AI can auto-apply them, and you can filter and group by label.
My Pipeline and the Workspace Dashboard
AB Sales has two overview screens — My Pipeline (your personal cross-workspace cockpit in the Home tab) and the per-workspace Dashboard. What each shows.
The Channel Tab and Notifications
The AB Sales channel tab gives your whole team one shared pipeline, and posts notifications to the channel when leads and customers are created. What everyone sees, and why it's the same for all members.
Sending Email from AB Sales
How AB Sales sends email — in plain terms. It sends from your own company mailbox through Microsoft 365, set up once by your admin. Covers the sending identity, choosing a mailbox, templates, campaigns, AI-drafted replies, and deliverability.
Sales Workspaces: Channel-Linked vs Standalone
A workspace is one self-contained CRM. AB Sales has two kinds — channel-linked (shared with a Teams channel) and standalone (yours in the personal app). How to create and switch between them.
Installing the AB Sales Teams App
How to install AB Sales in Microsoft Teams — as a personal app for your own pipeline and as a channel tab for a pipeline your whole team shares.
Agents: CRM Automation
The Agent is the automation engine that finds missing websites, extracts contact emails, sends your campaign emails, and drafts AI replies when leads respond — on a 5-minute timer, with strict verification, human review, and daily caps. This article covers each stage, how to pause, and how to opt out a single lead.
CRM Settings
Everything on the CRM Settings page — the workspace currency, the mailbox it sends from, the material the AI writes with, and your labels. Automation, the daily email cap, the notification channel and templates now live on the Agents page. Everyone can see settings; only Owners and Admins can change them.
Contacts
A Contact is a person attached to a Lead or Customer in AB Sales. Adding a contact to a lead advances it to the Contact stage. One parent can carry many contacts — the buyer, the technical reviewer, the decision-maker.
Opportunities
An Opportunity is a specific deal in AB Sales — an amount, a close date, and a stage. Win it to convert a lead to a customer, or to auto-create an order if it's already on one.
Customers
A Customer is an established account in AB Sales — usually converted from a won lead. Customers carry multiple Contacts and Opportunities and can be archived without losing history.
Leads: Capturing and Qualifying Prospects
A Lead is a prospect you haven't yet established a relationship with. This article covers the status pipeline (New, Information filled, Contacted, Qualified, Disqualified), how the AI Get URL button works, and how leads get filled in manually or by the Agent.
Linking Documents to Tasks and Finding Pages
Learn how to find project documents and create bidirectional links between documents and tasks in ActionBridge.
Document Comments and Teams Notifications
Learn how to discuss project documents and how document creation and edits notify your linked Teams channel.
Project Documents (Wiki): Overview
Learn how to find, create, organize, and collaborate on project documents in ActionBridge.
Creating and Editing Documents
Learn how to create, organize, edit, preview, and review versions of project documents in ActionBridge.
Connecting AI Assistants via MCP
Connect Claude, ChatGPT, Cursor, Windsurf, Codex CLI, or Antigravity to ActionBridge via MCP at https://mcp.actionbridge.io/mcp — the /mcp path is the step everyone misses. Per-client OAuth setup, what you get (tools, slash-command prompts, resources), licensing, and troubleshooting.
MCP Tools Reference
All 55 MCP tools ActionBridge gives AI assistants — ab_* for AB Projects (tasks, schedule, Documents, project statuses and types), ab_crm_* for AB Sales (leads, labels, opportunities, activities, email), and ab_support_* for AB Support (tickets, triage, draft replies) — plus the slash-command prompts, resource feeds, which tools need a license, and which writes post a Microsoft Teams card.
Teams Channel and Project Linking in AB Projects
How AB Projects links each Microsoft Teams channel one-to-one with a project: the link is made when the tab is added, membership syncs from the channel roster automatically, and comments flow between task and channel thread.
Why AB Projects Requires Microsoft Graph Permissions
Every Microsoft Graph permission AB Projects requests, mapped to the feature it powers: Teams channel linking and roster sync, task cards and comment sync in channels, Outlook calendar scheduling, and Microsoft SSO. Most access is delegated (limited to what you can already do); the Entra ID consent screen is the authoritative list.
I Can't See My Tasks
Tasks not showing in AB Projects? It's almost always a remembered filter, the wrong project or view (Gantt needs dates), or Teams-channel membership that hasn't synced — and if you can see tasks but not create them, it's a license seat, not a bug.
Who Can See What?
Visibility in AB Projects is decided by project membership: every member sees all of the project's tasks, comments, subtasks, and history. Roles (Owner/Admin/Member/Viewer) control what you can change, not what you can see — there are no private tasks. To hide work, use a separate channel and project.