Sending feedback in

Every way feedback can arrive, including the one web request that lets almost any tool post in.

Inside the product

Paste on the Add feedback page, with an optional person, company and source link. One text can be up to 200,000 bytes.
Recordings: upload a call or interview; it is transcribed with speakers and timing, and highlights are suggested. (Paid plans.)
Website form and chat: in Settings, switch on the feedback form or the chat inbox, add the sites allowed to use them, and copy the embed code.
Email: Settings, Inbox gives an address to route customer email to.
Slack: connect a workspace and choose one channel; its messages become feedback.
Surveys: free-text answers go to the review queue.

From other tools: one web request

Help desks, form tools, automation services and call tools can all post in with a key that has the "add notes to the review queue" permission (Settings, API keys).

curl -X POST "$API/v1/ext/feedback" \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{"source":"Help desk","title":"Ticket 1042","externalId":"1042",
       "url":"https://desk.example.com/tickets/1042","email":"dana@acme.com",
       "text":"Customer: we keep asking for SSO.\n\nAgent: noted."}'

text (required, up to 20,000 characters): put the whole thread in and label who is speaking.
source, title, url: where it came from, shown on the review queue.
externalId: the other tool's id. Sending the same one again from the same source stores it once, even if the text was edited. The answer says duplicate: true.
email: if a person with this email exists, the note is theirs, so their account's value counts. Nobody is created from it.

Call transcripts

POST /v1/ext/transcripts takes a transcript as WebVTT, SRT, JSON speaker turns or plain text (the format is guessed), or a list of turns. Timing is dropped, speakers are kept, neighbouring turns by one speaker are joined, and the result is read like any pasted conversation.

curl -X POST "$API/v1/ext/transcripts" \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{"source":"Call tool","title":"Acme QBR","externalId":"call-77",
       "transcript":"WEBVTT\n\n00:00:01.000 --> 00:00:04.000\n<v Dana>We keep asking for single sign-on.</v>"}'

Limits and safety

A key may add 500 notes a day and make 120 requests a minute; a workspace also has a daily allowance of new text (about 5 MB). Over a limit you get a 429; try again later.
Card numbers, keys and passwords are hidden before anything is stored.
Use a key made only for this, with only that permission, so you can revoke it on its own.

Inside the product

Paste on the Add feedback page, with an optional person, company and source link. One text can be up to 200,000 bytes.

Recordings: upload a call or interview; it is transcribed with speakers and timing, and highlights are suggested. (Paid plans.)

Website form and chat: in Settings, switch on the feedback form or the chat inbox, add the sites allowed to use them, and copy the embed code.

Email: Settings, Inbox gives an address to route customer email to.

Slack: connect a workspace and choose one channel; its messages become feedback.

Surveys: free-text answers go to the review queue.

From other tools: one web request

Help desks, form tools, automation services and call tools can all post in with a key that has the "add notes to the review queue" permission (Settings, API keys).

curl -X POST "$API/v1/ext/feedback" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{"source":"Help desk","title":"Ticket 1042","externalId":"1042", "url":"https://desk.example.com/tickets/1042","email":"dana@acme.com", "text":"Customer: we keep asking for SSO.\n\nAgent: noted."}'

text (required, up to 20,000 characters): put the whole thread in and label who is speaking.

source, title, url: where it came from, shown on the review queue.

externalId: the other tool's id. Sending the same one again from the same source stores it once, even if the text was edited. The answer says duplicate: true.

email: if a person with this email exists, the note is theirs, so their account's value counts. Nobody is created from it.

Call transcripts

curl -X POST "$API/v1/ext/transcripts" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \ -d '{"source":"Call tool","title":"Acme QBR","externalId":"call-77", "transcript":"WEBVTT\n\n00:00:01.000 --> 00:00:04.000\n<v Dana>We keep asking for single sign-on.</v>"}'

Limits and safety

A key may add 500 notes a day and make 120 requests a minute; a workspace also has a daily allowance of new text (about 5 MB). Over a limit you get a 429; try again later.

Card numbers, keys and passwords are hidden before anything is stored.

Use a key made only for this, with only that permission, so you can revoke it on its own.