Help & Support
Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.
Working the Ticket Queue
How to scan, filter, and work the AB Support ticket queue: the inbox row signals, quick filters and sort, saved filters, keyboard triage, and bulk actions.
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 (channels, statuses, knowledge, members and roles), reached from inside the desk.
Support Desks: Your Workspace per Channel
A desk is your AB Support workspace for one Teams channel — its own tickets, customers and settings, independent of AB Projects and AB Sales. Here's how one is created.
AB Support: Overview
AB Support is AI-assisted customer service inside Microsoft Teams — customers reach you by web chat, email, forms, WhatsApp and SMS; tickets land in one queue your team works. 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 40 MCP tools ActionBridge gives AI assistants — ab_* for AB Projects (tasks, schedule, Documents) and ab_crm_* for AB Sales (leads, opportunities, activities, email) — plus the slash-command prompts, resource feeds, which tools need a license, and which writes post a Microsoft Teams card.
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.
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.
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.
Adding or Removing Members
How people join and leave an AB Projects project: the linked Teams channel is the roster — auto-sync adds the whole channel, the Team page invite covers stragglers, and removing someone for good means removing them from the channel too.
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.