Tag Ringover calls by outcome with AI

1. An admin turns on the Tag calls permission for each user and can switch on Tags required, which keeps the dialer open after a call until a tag is chosen. The free tagging feature has to be activated in the Marketplace first.
2. After a call, the after-call window opens with a countdown. The rep selects the call tag, types the notes and clicks End call.
3. A call that was missed or left untagged is fixed later: in the Dashboard, open Call logs, select the call, click Add a tag and choose a tag or a group of tags.
4. In the web app, the same fix is the tag icon on the call in the call logs. In the Conversations tab, it is the three dots next to the call, then Add tag.
5. To judge the outcome, the admin opens the call details, plays the recording or reads the Transcript tab, then tags it by hand.

Go through yesterday's answered Ringover calls longer than a minute. Read each transcript and tag it with one of my call tags: Demo booked, Price question, Support, or No fit. Leave a call untagged if none fits.

1. 01

   Collect the calls to judge

   list_calls runs with from and to set to yesterday and status answered. The agent drops calls under a minute by duration and skips calls that already carry a tag, which get_call shows in its tags field. Pages come with a cursor; the agent follows it until the day is covered.

2. 02

   Load your tag list

   list_call_tags returns the tags your team created, with their group. The agent only uses tags from this list. A name from your prompt that Ringover does not have is reported back, and the agent never creates tags of its own.

3. 03

   Read the conversation

   get_call_transcript returns the text of each call. It works only for calls with a recording, and transcription must be enabled for the team; a call without a transcript is listed for you instead of guessed at.

4. 04

   Tag only clear outcomes

   add_call_tag runs once per call when the transcript matches exactly one of your definitions, for example a date agreed for a demo for Demo booked. Mixed or unclear calls stay untagged with a one-line reason.

5. 05

   Report what changed

   The agent lists the tags it set and the calls it left. A wrong tag is undone with remove_call_tag, so add_call_tag does not wait for your OK.

Answered calls over 1 minute yesterday: 23
Tagged 19:
- Demo booked 6 (e.g. call with Dana Whitfield: "Thursday at 10 works")
- Price question 7
- Support 4
- No fit 2
Left untagged 4:
- Call c_91e04a77: two topics, price and a refund
- Call c_91e04b02: no transcript, recording was off

curl -X POST https://cotlet.dev/api/v1/ringover/calls/c_91e04a77/tag \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tag":"Demo booked"}'

{
  "call_id": "c_91e04a77",
  "tags": [
    "Demo booked"
  ]
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is ringover_write → add_call_tag. Example data.

• Text back missed Ringover callers with AI
• Ringover API and MCP server: every tool
• All use cases