> ## Documentation Index
> Fetch the complete documentation index at: https://developers.heymarket.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lists, templates, and scheduled sends

> Understand the reusable Heymarket objects that support broadcasts, personalized messages, scheduled delivery, tags, and surveys.

Lists, templates, scheduled sends, tags, and surveys help you build repeatable messaging workflows without hardcoding every recipient or message body.

## Lists

A list groups recipients for broadcast messaging. When you send to a `list_id`, each recipient receives an individual message and can reply privately.

Lists can contain lightweight targets with phone numbers and optional name values. Those values can be used for personalization when no full Heymarket contact exists for the phone number.

## Templates

A template is saved message content that can include text, media, and merge tokens. Use templates when teams need consistent wording or when your integration sends the same type of message repeatedly.

Templates can use contact values as merge tokens, such as first name, last name, or custom field values.

## Scheduled sends

Scheduled sends queue a message for future delivery. Use scheduled sends for reminders, follow-ups, appointment messages, or campaigns that should go out at a specific time.

You can retrieve, update, or delete scheduled messages before delivery.

When creating a scheduled send, provide `inbox_id`, `execute_at`, `content`, and one target family such as `phone_number`, `conversation_id`, `list_id`, or `targets`. `execute_at` must use RFC 3339 format, be at least 15 minutes in the future, and align to a 15-minute interval. Provide `user_id` when the scheduled message should be sent as a specific inbox member.

## Tags

Tags categorize contacts. They can support segmentation, filtering, routing, and reporting workflows.

Each tag belongs to your team and has an ID, name, and color.

## Surveys

Surveys let you send standardized questions and collect customer responses. Use surveys when your workflow needs structured feedback instead of free-form replies.

## Related pages

<CardGroup cols={2}>
  <Card title="Broadcast messages" icon="megaphone" href="/guides/broadcast-messages">
    Send a message to a contact list.
  </Card>

  <Card title="Lists reference" icon="code" href="/api-reference/lists/overview">
    Review list endpoints.
  </Card>

  <Card title="Templates reference" icon="file-text" href="/api-reference/templates/overview">
    Review template endpoints.
  </Card>

  <Card title="Schedule reference" icon="calendar-clock" href="/api-reference/schedule">
    Review scheduled message endpoints.
  </Card>

  <Card title="Tags reference" icon="tag" href="/api-reference/tags">
    Retrieve tags for segmentation and routing.
  </Card>

  <Card title="Surveys reference" icon="clipboard-list" href="/api-reference/surveys">
    Retrieve surveys for structured feedback workflows.
  </Card>
</CardGroup>