GEgetsales
agent_plans

Draft follow-ups

Write the follow-ups that continue the team's last message on a thread (the composer's Make follow-ups): how many, how many days apart, in the sender's words or the AI SDR's; each comes with its time (ten in the morning of the workspace's day, the weekend skipped). Nothing is saved: read them back, edit, then schedule_followups. 503 composer_unavailable when the runner did not answer. The agent's own token is 403 (human_verb_only).

Contract:

  • MCP tool draft_followups, registry package mcp.unibox/agent_plans, mount unibox.agent.
  • Operation action, response envelope action.
  • Flags: read only.
post/api/agent-plans/draft-followups

Request

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.

countinteger

How many follow-ups to write, 1..3; default the agent settings' person_followups_count (2).

guidancestring nullable

What should change, in the person's words, when they read a first draft and ask again (shorter, another angle, a name to mention). Max 1000 chars; omit on the first ask.

Response

action success envelope.

successtrue required
operation'action' required
actionstring required

kebab-case verb; matches the route segment.

itemunknown required

Changes

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