Help & Support
Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.
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.
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 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.
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.
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.
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.
Why AB Projects Requires Microsoft Graph Permissions
Every permission AB Projects asks for, mapped to the feature it powers: organization-wide Microsoft Graph permissions an administrator consents to in Entra ID (mostly delegated), and the team permissions a team owner accepts per team, including the 2.4.0 one that lets thread replies sync to tasks.
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.
Managing Subscriptions, Billing & Licenses
How AB Projects pricing and licensing work: a free tier (first 10 active users per tenant) and a Basic plan ($3 per active user / month) purchased on Microsoft AppSource — including the activation page, assigning seats in Settings → Manage licenses, subscription status and history, free trials, and exactly what happens when you cancel or reduce seats.
Integration with Microsoft Teams and Adaptive Cards
How AB Projects and Microsoft Teams fit together as one system: the one-to-one channel–project link, the tab, Adaptive Card posts with two-way thread sync, the chip-picker mention model, and Microsoft SSO with channel-driven membership.
Commenting with Mentions in Channels
How task comments and their Microsoft Teams thread stay in sync — every comment posts to the channel, and any reply in the task's thread comes back as a comment once the team is on AB Projects 2.4.0 — and how the Mention in Teams notification picker controls who gets pinged.
Installing the AB Projects Teams App
How to install AB Projects in Microsoft Teams: add the app from the Teams app store or Microsoft Marketplace, then add the channel tab to link a channel to a project — with automatic Microsoft 365 sign-in, project types, the included bot, and licensing basics.
Managing Project Settings
A tour of the AB Projects project settings page: identity, members, Teams channel notification toggles, GitHub integration, task workflow options, the Teams link, ownership transfer, leaving, and the unlink-before-delete rule.
Role-Based Access Control
The four project roles in AB Projects — Owner, Admin, Member, and Viewer — what each can do, how roles are changed, the guardrails around ownership and the last Admin, and how the read-only Viewer role differs from having no license seat.
Understanding Projects and Teams
What a project is in AB Projects: a shared workspace of tasks, wiki, and documents tied one-to-one to a Microsoft Teams channel, with membership synced from the channel and four roles — Owner, Admin, Member, and Viewer.