Help & Support
Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.
Leads from Your Website Form or API
Point your website's download, demo or contact form at AB Sales and every submission becomes a lead — no sign-in, no backend. Covers the intake key, the HTML form snippet, the JSON API, what a repeat submission does, and what your visitor sees.
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.
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.
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.
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.
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.
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.
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.
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.
Research with AI
Research with AI enriches a lead — finds its website, reads the homepage, and fills in a company summary, contact email, and suggested labels. It does not move the lead through the funnel.
How the AB Sales Funnel Works
How a lead moves through the AB Sales funnel — Lead → Contact → Opportunity → Customer — what advances each stage, and why AI research enriches a lead without moving it.
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.
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.
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 created — typed in, imported from CSV, or sent from your own website form or API.
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.
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.
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.
Exporting and Accessing Project Data
AB Projects has no CSV/Excel export of task or project data yet. How your data is preserved (per-task change history, the Teams channel record) and how to get it out today: filtered views, AI assistants over MCP, and asking support.
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.
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.