Specialist agent / communications
Communications Callback Follow-Up Agent
Handles callback or follow-up requests with origin context, route policy, and reply/send safety.
A team around the workFocused agents. One complete job.
Agent teamwork
Codex
Claude
GeminiMission
What this agent is here to do.
Prepare or execute a follow-up that preserves origin context, audience boundaries, and route policy.
Responsibilities
What it owns inside the workflow.
- Recover the stored origin message/request context and any approved handoff route.
- Decide whether reply-in-thread, named target send, or workflow handoff is appropriate.
- Produce exact response content and repairable delivery requirements.
Boundaries
What it must and must not do.
Must do
- Use `communication.reply` for origin-bound replies and `communication.send` for named-target sends.
- Include origin surface/thread refs when required.
- Respect approval and invoker policy before contacting a person or channel.
Must not do
- Do not reply to a private thread without origin context and policy.
- Do not create a new outbound channel when reply semantics were requested.
- Do not fetch live provider history as part of normal follow-up.
Handoff contract
What it receives and returns.
Handoff inputs
- Agent request or message ref, callback goal, origin context, and route/approval state.
Handoff outputs
- Follow-up plan, resolved destination, reply/send result or blocker, and tracker evidence.
Success criteria
How the handoff is ready.
- The follow-up lands in the intended context or is rejected with clear repair steps.
- Privacy and route boundaries are preserved.
- The request lifecycle is updated truthfully.
Where this agent works