Open Support Conversation
tt_open_support_conversationOpen a support conversation to escalate to a live Tradetron agent.
USE WHEN: a previous tt_ask_tt call returned escalate=True, OR a
tt_diagnose_strategy call could not pin a cause — AND the user has
confirmed they want to talk to a human agent. Pass the
handoff_payload dict from that earlier result through here
verbatim; both tools return one.
DO NOT USE proactively. Always confirm with the user first — opening a support conversation pings real Tradetron support staff.
The conversation is seeded with two messages visible to the agent: a private note carrying the escalation reason, the user's Tradetron identity when it could be resolved, and — when retrieval ran — a one-line summary of what the bot looked at; plus the user's original query as a normal user-side message. On the tt_ask_tt escalation paths the bot has not composed an answer by the time it escalates, so that note carries none; the tt_diagnose_strategy path hands over what the diagnosis found. Either way the agent works the case themselves — never tell the user an answer is already waiting with them.
Returns a session_id and nothing else — there is NO link to hand the user. This conversation lives only inside the assistant: pass the session_id to tt_check_support_response (poll for agent replies) and tt_reply_to_agent (relay user follow-ups). Say that plainly rather than implying they can open it somewhere.
session_context (optional): identifiers you are already holding, so
the agent does not start cold — any of {deployment_id, strategy_id,
template_id, download_url, request_id}. Pass the SID you diagnosed,
the tt_export_strategy download_url, and the _meta.request_id of
the failing call when there is one. Identifiers only: free-form
blobs are dropped, and each value is truncated.
On status="stub" the support bridge is not connected on this server, so NO conversation was opened and nobody will see the message. Tell the user plainly that you could not reach support from here, give them the Tradetron help centre or the in-app chat, and do not imply anyone has been notified or will reply.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"handoff_payload": "<handoff_payload>"
},
"name": "tt_open_support_conversation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| handoff_payload | Yes | ||
| session_context | No |