Send us your conversations. Read back what we find.
Every way conversations reach us and everything we send back, each as a contract with a worked example. No helpdesk needed: if your support runs in an inbox, a widget or something you built yourself, the signals API is the whole integration.
Sending us signals
Every way conversations and events reach us: the API, files, buckets, receivers, an inbox and the widget.
Post conversations and context events from anything: an in-house helper, a custom AI, a script over an export. The one contract everything else here is built on.
Upload a CSV, JSON Lines in our format, or JSON in your own shape. Check how it was read, confirm the mapping, and import: redacted before the first write, the same as everything else.
Post a file’s worth of conversations from a script with an import key: a check that stores nothing, then the same body with its fingerprint. Gzip allowed, redacted before the first write.
Point us at a folder in an S3 or Google Cloud Storage bucket you own and the objects that are new there are read every night like an upload. Read-only, with the exact policies to paste.
Point a PostHog, Sentry or status page webhook at a key of its own, and product events, errors and incidents arrive as signals with no code of yours in between.
Forward the inbox your customers already write to, and every thread becomes a conversation, redacted on the way in.
One script tag, installed once. Show nothing and carry feedback from your own agent, or the whole help corner: surveys, messages, search, the assistant and a person. Everything is set in FunctioningHQ.
Thumbs, “this didn’t help” and “talk to a person” from your own AI’s chat, by a selector set in FunctioningHQ, one line of JavaScript, the signals API or OpenTelemetry — joined to the conversation and its traces.
What we send you
What we post to your systems when something happens, and how to verify it came from us.
We POST to an address you own when a play reaches a verdict, a decision is taken, or an approval is waiting. Signed, replay-proof, ids and counts only.
Agents and platforms
Connecting an AI agent or a platform to read and act through us.
Point Claude, Cursor or your own agent at your patterns and evidence. It reads; what it proposes comes back for a person to approve.
Vercel integration and template
Coming soonComing soon: add FunctioningHQ from your Vercel dashboard, with the signal key and widget in your project’s environment and every deploy recorded as a release. What to do meanwhile is on the page.
Access
How much of your helpdesk we read, and what we may change.
How much of your helpdesk we read, and why rung 1 reads nothing at all on Help Scout and Gorgias. A boundary in the application, not only in the token.