Skip to main content
APIMCP
Retention offers that pause a membership
  • Reports have a new retention_offers_applied metric. It counts accepted retention offers that your business software confirmed, such as a discount or a lower plan.
  • The new retention_pauses_applied metric counts accepted offers that paused the membership instead of cancelling it. Pauses no longer count in retention_offers_applied or memberships_saved.
  • A call where the membership was cancelled after the offer was applied no longer counts as applied.
  • retention_discounts_applied still works and returns the same number as retention_offers_applied. Use the new name in new requests.
  • AMP offers applied before October 9, 2026 did not record whether they were pauses, so they still count as applied offers and saves.
APIMCP
Text back a caller with no text thread
  • POST /conversations/{conversation_id}/messages and the MCP reply_to_conversation tool can now text a caller on a phone call that has no text thread yet. Before, a call needed text in its channels. The dashboard already allowed this.
  • The text goes to the contact’s current phone number. A customer who opted out by replying STOP still gets no texts, and the dashboard’s other rules still apply.
  • A call that also has an email thread can get a text or an email, so send channel to choose. Before, such a call got an email when you left out channel. Now the reply returns 422 and nothing is sent.
APIMCP
Reply to customers from the API and the MCP server
  • POST /conversations/{conversation_id}/messages sends a text or email reply to the customer on an existing conversation, the same as clicking Send in the dashboard. The customer receives it.
  • The MCP server has a new reply_to_conversation tool that sends the same reply. By default, Claude and ChatGPT ask you before each send.
  • A reply goes only on a channel the conversation already uses, as listed in its channels. A call can get a text when the conversation already has a text thread, including one the AI sent. Website chats, and calls with no text or email thread, can’t get a reply this way. Reply to those from the dashboard.
  • Replies follow the dashboard’s rules, so a customer who opted out by replying STOP gets no texts. Each reply shows in the conversation thread and in Activity under the person’s name.
  • Send an idempotency_key to retry without sending the customer the same reply twice. See Retry without sending twice.
APIMCP
Conversation notes and long threads
  • GET /conversations/{conversation_id} and the MCP get_conversation tool now return the conversation’s internal notes in notes, oldest first, in the same shape POST /tasks/{task_id}/notes returns.
  • A long text, chat, or email thread now returns its newest messages instead of its oldest. To read earlier messages, pass written.earlier_cursor as the new before parameter until it is null. See Read a long thread.
  • Every other field is unchanged, and a short thread returns the same messages as before.
Webhooks
Webhook events and signatures
  • Each webhook now has an Events list in Settings → Webhooks. Check the events you want to receive. See Set up the webhook.
  • The new task.updated event fires when a task’s status or assignee changes, from the dashboard, the API, the MCP server, or the AI. Its changes field holds the old and new values.
  • The new task.note_added event fires when someone adds an internal note to a task. Its note field holds the note.
  • Every request is signed. The Answering-Agent-Signature header carries a timestamp and an HMAC-SHA256 signature of the timestamp and body, and Answering-Agent-Event-Id carries the event’s id. See Verify requests.
  • Existing webhooks keep working as before. They receive only task.created until someone checks more events, the task.created body is unchanged, and the X-Answering-Agent-Secret header still arrives on every request.
APIWebhooksMCP
Customer API, task updates and notes, webhooks, and MCP server
  • The Customer API reads your team’s account, conversations, transcripts, call recordings, tasks, contacts, and reports.
  • PATCH /tasks/{task_id} changes a task’s status or assignee. Send expected_status or expected_assigned_to to avoid overwriting a change someone just made in the dashboard.
  • The webhooks page documents the task.created event, the secret header, and the retry rules.
  • The MCP server lets Claude, ChatGPT, or another MCP app look up your calls, tasks, contacts, and reports.
  • POST /tasks/{task_id}/notes adds an internal note to a conversation task. If your team requires a note before a task is marked done, add the note first, then mark the task done.
  • The MCP server can change a task’s status or assignee and add internal notes with the new update_task and add_task_note tools. Claude and ChatGPT ask you before they run either one.
  • GET /tasks and GET /conversations take updated_since and return only records that changed at or after that time, oldest change first. Every task and conversation now has updated_at. The MCP search_tasks and search_conversations tools take the same updated_since argument. To keep a ticket system up to date with it, see Sync tasks to ClickUp or Zendesk.