agoráconversations
Catalog
Tier-1 triage and routing·live·3-turn average·can escalate

Ambiguous message disambiguation

What it does

Detects messages with insufficient signal for confident intent classification and asks a single, targeted clarifying question before routing.

When to use it

Use after the intent classifier when confidence falls below 0.7. It prevents the most common cause of bad routing: classifying on a four-word message.

What it doesn't do

It asks one question and stops. If the customer's reply is still ambiguous, it escalates to human triage rather than guessing twice.

§ live preview
live preview·Ambiguous message disambiguation
harness
  1. intake
  2. classify
  3. collect
  4. handoff
Press play to step through the conversation.
§ connect
mcp url

Provisioning the MCP URL for Ambiguous message disambiguation is part of Pro.

Free accounts can read the YAML, run the Live Preview, and provision one starter URL. Pro provisions URLs for the whole catalog.

§ source

Open YAML. Read it before you subscribe.

source·ambiguous-message-disambiguation.yaml
1# ambiguous-message-disambiguation.yaml
2name: ambiguous-message-disambiguation
3version: 1.0.0
4category: tier-1-triage
5description: One targeted clarifying question, then re-route.
6 
7inputs:
8 - name: message
9 type: string
10 required: true
11 
12harness:
13 - step: intake
14 require: [message]
15 - step: classify
16 model: deterministic
17 confidence_floor: 0.7
18 on_below_floor: continue
19 - step: collect
20 ask_one: clarifying_question
21 max_turns: 1
22 - step: classify
23 model: deterministic
24 on_below_floor: route_to(human-handoff-with-context)
25 - step: handoff
26 
27limits:
28 total_turns: 3
29 
§ personalization

Need ambiguous message disambiguationtuned to one client’s voice, escalation logic, and required fields? That’s a $99 personalization.

One-shot fee. Turnaround stated up front. The result is yours, with the deterministic harness already wired.

Request personalization