GEgetsales
agent_plans

Schedule follow-ups

Schedule the follow-ups a person made (the composer's Make follow-ups): a plan of the followup_after_person behavior, active at once and approved by the caller, a reply wait before each follow-up (its text the person's), the last wait, then the end the settings name (a task for the person, or the AI SDR carries on). Each goes at its time unless the lead answers first, which supersedes the plan. 409 agent_disabled_on_thread when the AI SDR does not work the thread; the agent's own token is 403.

Contract:

  • MCP tool schedule_followups, registry package mcp.unibox/agent_plans, mount unibox.agent.
  • Operation create, response envelope create.
  • Flags: none.
post/api/agent-plans/schedule-followups

Request

  • Base URL
    https://beta.getsales.io/unibox/v1
  • Auth
    HTTP bearer and API key in header Team-SID

Request body

conversation_sidstring required

The thread the follow-ups continue (ub_cv_…): its last message of ours is what they follow; when the lead wrote last, they count from now.

every_daysinteger

Days between the follow-ups, 1..30; default the agent settings' person_followups_every_days (3).

voice'sender' | 'agent'

sender: written as the sender profile (the person) would write them, continuing their own message; agent: in the AI SDR's own voice. Default: the last message's author.

then'task' | 'agent_continues'

What ends them when none is answered: task opens a task for the person; agent_continues lets the AI SDR follow up on its own. Default the agent settings' person_followups_then.

Response

create success envelope.

successtrue required
operation'create' required
already_existsboolean required

Changes

No recorded changes to this operation across all 1 revision of this API.