Quickstart

Connect one platform and read your first result. Ten minutes, one path, no choices.

This is the shortest path from nothing to a scored conversation. It connects one platform, sends one real conversation through it, and ends on the screen where the first result appears. Nothing about your agent changes.

What you need first

An invitation. Workspaces are invite only, so somebody with an owner seat mails you one.
Rights to change a setting on the platform your agent runs on. Step 2 pastes an address into it.
One agent you can hold a real conversation with, on voice or on chat.

Step 1. Connect the platform

Pick your platform from the list. The form asks for that platform's own fields, in that platform's own words, and for nothing else. Copy each value out of the platform's settings. We store them encrypted and never show them again.

Then choose which of your customers this platform carries conversations for, or leave it on Every client, which is the right answer when one platform serves them all. Press Connect.

Step 2. Give the platform the address

The connection screen opens on a delivery address that carries a token of its own. Copy it, open the webhook setting on the platform, paste it there, and save. That is the whole integration: you write no code.

If the platform signs what it sends, put its signing secret into the connection as well. A delivery whose signature does not match is turned away, and the connection screen counts every refusal it made.

Some platforms deliver nothing. For those we ask the platform for finished conversations on a schedule, so there is no address to paste and this step is already done. The connection screen says which of the two you have.

Step 3. Have one conversation

Call the agent, or chat with it, and finish. We read finished conversations, so nothing arrives while one is still open. A call ends when the caller hangs up. A chat ends when the platform says so, or after it has been quiet long enough for us to close it ourselves.

Step 4. Confirm it arrived

Go back to the connection. Four counts sit across the top of it: deliveries, deliveries we could not read, the first one, and the most recent one. First delivery stops reading never within seconds of the conversation ending.

Silence and refusal are different answers, and the screen keeps them apart. The last failure and the last refusal each get a line of their own, with the reason the platform was given.

Step 5. Read the first result

Open Overview. Once the conversation is scored it counts toward the numbers there, and the conversation list has a row for it. Open the row to see every rule that ran, what each one found, and the turn it found it on.

Overview after the first conversations have arrived and been scored: the three numbers across the top, and the things that need somebody beneath them.

Note: Your first conversation may not be scored in full straight away. Rules that need no AI run on all of it at once. Rules that need a judge run on a share of traffic as it lands, and a nightly pass covers the rest, so the full result can arrive by the next morning. What gets scored explains the split.

If nothing arrives

Deliveries stays at zero	The platform has not posted anything yet. Confirm you saved the address in it, and that the conversation really finished.
Refusals climb	The signature did not match the secret held in the connection. Copy the secret out of the platform again.
Every delivery gets a not-found answer	The connection is switched off, or its address has been replaced and the platform still holds the old one.
Deliveries land but no conversation appears	We could read the delivery and not the conversation inside it. The last failure line names what we could not read.

Where to go next

How it works, for the six stages between arriving and being scored.
What gets scored, for which rules run on everything and which do not.
Webhooks, for every answer the delivery address gives back and what each one means.

This page as markdown