Help & Support
Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.
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.
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.
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.
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.
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.
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.
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.
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.
CRM Settings
Everything on the CRM Settings page — the workspace currency, the mailbox it sends from, the intake key for your website form and API, 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.
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.
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.