conduyt_reply_suggestion_decide
Record the outcome of a suggested reply as accepted, sent, or dismissed so agents can track which drafts were taken into a composer, actually delivered, or rejected.
Instructions
Copilot Tier 2 — record what was done with a suggested reply: accepted (the draft was taken into a composer), sent (with the outbound message id, after sending it through conduyt_send_message / the messages API), or dismissed. A suggestion moves once (accepted → sent is allowed).
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": {
"contactId": "<contactId>",
"messageId": "<messageId>",
"decision": "<decision>"
},
"name": "conduyt_reply_suggestion_decide"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| decision | Yes | ||
| contactId | Yes | Contact UUID | |
| messageId | Yes | The inbound message the suggestion answers (suggestion.messageId) | |
| sentMessageId | No | REQUIRED with decision=sent: the OUTBOUND message id that was sent — it must belong to this contact and be provider-confirmed (status sent/delivered, or queued with a provider id); a pending, draft or failed message is refused |