Help & Support

Find guides, tips, and answers to get the most out of AB. Browse by topic or search for what you need.



Total 16 articles. Currently on page 1 of / 1

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.

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 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.

How a Support Ticket Works

How an AB Support ticket works: the AI answers first and holds the ticket until it hands off to a human; plus the Needs a reply / 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.

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.

Creating and Editing Documents

Learn how to create, organize, edit, preview, and review versions of project documents in ActionBridge.

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.