AI agent handoff
What happens when one AI agent @mentions another in a project room: it answers at once, waits for a person, or is not passed on.
The words that turn up when you start calling a LinkedIn or messaging API and letting the work run without you — and what each one actually means once you are the one handling it.
What happens when one AI agent @mentions another in a project room: it answers at once, waits for a person, or is not passed on.
The lk_ string that decides which organisation you are, and therefore which LinkedIn accounts you may name.
The opaque handle for one connected LinkedIn account — and the one id in this API that is a security boundary.
The specialist AI agents every project room starts with: what each knows, when it answers, and what it cannot do.
The open-source helpdesk a team answers its customers from, on its own server or ChatWoot's cloud, and what connecting it to a room or the API reaches.
LinkedIn pausing a sign-in to ask a question. The five kinds, and which ones you can answer from code.
The ten digits that name a Google Ads account, why every call needs one, and why an account you were not given does not exist.
The one bot that reads and posts in your Discord servers for you: added through Discord's own page, held to your servers, and never pinging anybody.
A campaign that keeps working after you stop calling: what the three kinds do, whose AI key writes the words, and why stalled is not paused.
A shared chat where your team, invited guests and AI agents work in one conversation, on your organization's own AI key.
Doing the same thing twice and getting one result — the property that makes retries and duplicate webhooks harmless.
The checkpoint with no code: LinkedIn asks for a tap in its mobile app, and nothing comes back to the request that asked.
A WhatsApp number connected the way WhatsApp Web is, with a QR code: no Meta app, no approval, and every message sent as the number itself.
An HTTP API that drives a real LinkedIn account: what one call looks like, how an account is connected, and how it differs from LinkedIn's own partner APIs.
The protocol that lets an AI assistant call this API directly, with one address and nothing to install.
What a connector is in ChatGPT, Claude, Gemini, Cursor and Grok, what the address it wants looks like, and why there is nothing to install.
Where a customer writes to you — WhatsApp, Instagram, Facebook, TikTok, Telegram, LINE, email, SMS, a website chat, X or Discord — and which API reaches each.
Software that runs on your own server or in another AI tool and joins one project room through the API with its own token.
Spacing calls out on purpose so an account looks like a person using it, and what that buys you.
A shared chat where your team, invited guests and AI agents work in one conversation, on your organization's own AI key.
A change written down and checked by Google without being made: what a proposal is, who applies one, and what putting it back takes.
Which address LinkedIn sees your sign-in coming from, why it matters, and when to bring your own.
Connecting an account with the cookie from a browser that is already signed in, and why the user agent has to match.
One inbox for every channel your customers write on, where a team answers, assigns, labels and resolves conversations — by hand, from code or with AI agents.
Our 0 to 100 measure of how much a LinkedIn account is actually read, the four parts it is made of, and what it is not.
Being told when something happens instead of asking over and over — and the two things everyone gets wrong about it.
An endpoint a reseller adds to the API it sells under its own name: a few steps over the operations it already has, at an address it chose.
Asana, ClickUp, HubSpot, Jira and Trello — where a team's tasks already live, and what one connection to one of them reaches.