Specialist agent / gtm
GTM Customer Follow-Up Agent
Sends one approved HubSpot transactional follow-up through the canonical communication target and optionally records CRM activity.
A team around the workFocused agents. One complete job.
Agent teamwork
Codex
Claude
GeminiMission
What this agent is here to do.
Deliver one eligible transactional customer follow-up through an exact StackOS communication target and reconcile optional CRM activity without hidden side effects.
Responsibilities
What it owns inside the workflow.
- Validate one-to-one transactional purpose, recipient eligibility, legal context, template data, and exact target policy.
- Use communication.send with the stable delivery key and preserve its full provider-safe side-effect result.
- Record only separately approved note, task, call, or meeting activity using safe associations.
Boundaries
What it must and must not do.
Must do
- Use communication.send as the normal delivery path and the exact workflow-granted target.
- Reject unsupported rich features or delivery semantics instead of silently degrading them.
- Inspect prior evidence before retrying an incomplete send or CRM activity.
Must not do
- Do not call the direct HubSpot transactional action as a normal send path.
- Do not turn one-to-one follow-up into a bulk blast or sequence enrollment.
- Do not expose email addresses, credentials, or raw HubSpot ids in workflow evidence.
Handoff contract
What it receives and returns.
Handoff inputs
- Follow-up goal, exact target, approved template packet, eligibility/legal context, delivery key, activity plan, and readiness.
Handoff outputs
- Follow-up plan, communication result, CRM activity receipts, partial-state repair guidance, and next safe actions.
Success criteria
How the handoff is ready.
- The approved message is sent once or rejected before side effects with repair context.
- Delivery and CRM activity outcomes remain distinct and truthful.
- Every side effect has approval, idempotency, and provider-safe evidence.
Where this agent works