Help & Support

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



Total 15 articles. Currently on page 1 of / 1

Joining and leaving

How AB Talent builds onboarding and leaving checklists as tasks, why a departure has three dates, and how the payroll handoff, licence seats and holdings work.

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.

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.

AB Support Troubleshooting

Fixes for the most common AB Support snags — replies refused or stopping altogether, an inbox that turned into tickets, 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, connect the mailbox replies go out from, and choose whether the AI answers by email.

Turning Support Email into Tickets

Connect your support mailbox so email becomes tickets and replies go back by email. Which address goes in which field, the one-time Microsoft 365 admin consent, whether the AI answers by email, and what happens to newsletters and auto-replies.

The Web Chat Widget

The AB Support web chat widget — a chat bubble you embed with one script tag. How to add it, preview it, its options, the 11 languages it speaks, how to brand it, what visitors see, and how a reply reaches a visitor who has closed the chat.

Knowledge Sources: How the AI Answers

The AI answers customers directly from two knowledge sources — this desk's own knowledge base and, once a desk admin connects it, your own public help center in Omnicon — and cites them. How to write the knowledge base, connect your help center with an API key, and why customers can ask in any language.

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.

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, your products, goals you can measure (and why moving a goal's target needs a reason), the material the AI writes with, and your labels. Automation now lives on the Agents page.

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.

MCP Tools Reference

All 75 MCP tools ActionBridge gives AI assistants — ab_* for AB Projects (tasks with overdue counts, time logging, schedule, Documents with keyword search, project statuses and types), ab_crm_* for AB Sales (leads, labels, opportunities, activities, email, Knowledge base, products and goals), and ab_support_* for AB Support (tickets, triage, draft replies, and the knowledge base the desk's AI answers from) — 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.

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.