Outbound follow-up

Send relationship-aware outreach.

Use relationship history, contact enrichment, templates, and sequence prompts so outreach references the real record.

Token first

Make sure the agent has these scopes.

Create a new token or update the agent's current token before trying the calls below.

Required token scopes

contacts:read context:read llm:read sequences:write

Outcome

What this gives you.

The message feels informed because it is grounded in prior conversations, relationship strength, and current context.

Use when

The operational shape.

  • A customer, partner, vendor, or lead should hear from an agent without sounding like a campaign merge field.
  • The agent needs to check relationship health before writing or sequencing outreach.
  • Follow-up should continue only while the relationship context says it is still appropriate.

API sequence

The calls to make.

01

Read relationship context

GET/v1/relationships/{identifier}/

Fetch last contact, strength, recent topics, and relationship health.

02

Enrich the contact

GET/v1/contacts/{contact_id}/

Request contact_digest and next_step so the prompt can use real history.

03

Render the outreach frame

POST/v1/templates/{template_id}/

Use a reusable structure while leaving the human context to the agent prompt.

Default example
Use this as the default shape for this step.
{
  "context": {
    "first_name": "Avery",
    "topic": "proposal follow-up",
    "sender_name": "Jordan",
    "relationship_context": "customer engaged weekly with implementation questions and previously approved a shared timeline."
  }
}
04

Enroll contextual follow-up

POST/v1/sequences/enrollments/

Start an ad-hoc sequence whose prompts reference the relationship snapshot.

Default example
Use this as the default shape for this step.
{
  "inbox_id": "inb_sales",
  "recipient": {"contact_id": "ctc_123"},
  "exit_on_reply": true,
  "source": {
    "type": "external",
    "subject": "Relationship-aware outreach",
    "from_address": "agent@mail.example.com"
  },
  "emails": [
    {
      "delay_days": 0,
      "subject": "Following up on the implementation plan",
      "prompt": "Use the relationship digest and rendered template to write a warm, specific follow-up."
    },
    {
      "delay_days": 5,
      "subject": "Still useful to discuss?",
      "prompt": "Follow up briefly. Reference the prior outreach and avoid repeating the same ask."
    }
  ]
}

Controls

Review points.

  • Use templates for structure, not fake personalization.
  • The relationship snapshot should be included in sequence source so later steps stay grounded.