---
title: "Chimes"
description: "Send customer notifications by SMS or email and track delivery state."
canonical: "https://studio.inttegro.com/products/chimes"
format: inttegro-machine-docs/v1
language: "Go"
sdk_version: "v11.0.1"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/go/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 371
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 2126
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Send customer notifications by SMS or email and track delivery state. This Go representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Chimes?

Use this product guide to understand behavior, boundaries, and lifecycle before choosing API operations.

#### Q2. What is authoritative on this page?

This page is authoritative for product behavior and lifecycle intent. Linked API references define exact operations and data shapes.

#### Q3. What page-specific constraint matters most?

Keep product behavior separate from transport details and confirm current capabilities before hard-coding market or lifecycle assumptions.

#### Q4. Can Inttegro MCP materially help with this task?

No catalog ability is sufficiently specific to recommend for this page. Use the documentation directly; consult the MCP catalog only if the task later requires governed live account context or a supported operation.

#### Q5. How should the reader verify the answer and continue?

Confirm the chosen behavior against the linked guide and API operation, then verify the resulting resource state rather than relying only on UI presentation. Continue with [Message templates](https://studio.inttegro.com/machine/go/api/message-templates.md) and [Broadcast to customers](https://studio.inttegro.com/machine/go/guides/broadcast-to-customers.md) when those concerns enter scope.

## Document content

# Chimes

Chimes are customer notifications. Use them for receipts, order updates, reminders, campaign messages, and other merchant-to-customer communication that is not an authentication challenge.

> Mcp Guide Callout is interactive content. Use the canonical page to view it.

Use this page to choose the right communication primitive. Use the [Chimes API reference](https://studio.inttegro.com/machine/go/api/chimes.md) for exact request attributes, response shapes, and examples.

## What Chimes are for

A Chime is one notification to one recipient. It records the recipient, channel, sender, rendered message, delivery status, timestamps, and optional tracking data.

Schedules and broadcasts are higher-level orchestration records. They create individual Chimes when they execute, and those individual Chime IDs are what you inspect for recipient-level delivery.

| Need | Use |
| --- | --- |
| Message one customer now | [Send chime](https://studio.inttegro.com/machine/go/api/chimes.md#send-chime) |
| Message one or more recipients later | [Schedule chime](https://studio.inttegro.com/machine/go/api/chimes.md#schedule-chime) |
| Send the same message to many recipients | [Broadcast chimes](https://studio.inttegro.com/machine/go/api/chimes.md#broadcast-chimes) |
| Check one notification | [Lookup chime](https://studio.inttegro.com/machine/go/api/chimes.md#lookup-chime) |
| Browse recent notifications | [Page chimes](https://studio.inttegro.com/machine/go/api/chimes.md#page-chimes) |
| Verify phone control | [One-time passwords](https://studio.inttegro.com/machine/go/products/otps.md), not Chimes |

## The communication model

Chimes separate recipient selection from message content.

| Part | What it controls |
| --- | --- |
| Recipient | Inline phone or email, or a saved customer plus selected transport. |
| Transport | SMS or email. The resolved recipient determines which content shape is valid. |
| Message content | Plain SMS, email content, or a stored template reference. |
| Purpose and custom data | Your tracking fields for support, campaigns, or reconciliation. |
| Transmission | Provider handoff, delivery, failure, or suppression details when available. |

Stored templates must match the transport. An SMS template cannot be sent to an email recipient, and an email template cannot be sent to an SMS recipient.

## Choose the right sending pattern

| Pattern | Best for | Watch out for |
| --- | --- | --- |
| Immediate Chime | Receipts, one-off support messages, order updates, simple reminders. | The API call creates the notification immediately. Use idempotency keys. |
| Scheduled Chime | Appointment reminders, delayed follow-ups, known future messages. | Store the schedule ID and inspect recipient-level execution results after it runs. |
| Broadcast | Campaign or announcement to many recipients. | Creation is asynchronous; inspect the broadcast and generated Chimes instead of assuming every recipient succeeded. |
| OTP | Sign-in, sensitive action approval, phone ownership checks. | OTP has a verdict-bearing verification flow; Chimes do not. |

Chimes are not a real-time chat system. They are outbound notifications with delivery tracking.

## Delivery and observability

Delivery state tells you what Inttegro and the downstream provider know so far. It does not prove that a human read or understood the message.

Use lookup and page operations to answer support questions:

- Was the Chime created?
- Which channel was used?
- Was it handed off for delivery?
- Did the provider report delivery, failure, suppression, or another terminal outcome?
- Which schedule or broadcast created it, if any?

Keep your own business action separate from delivery telemetry. For example, “receipt SMS delivered” is not the same as “customer accepted the order.”

## Content and safety

Write messages for the channel.

- Keep SMS short and action-oriented.
- Avoid secrets, OTP codes, private tokens, and sensitive account details in Chimes.
- Use templates when many messages share the same structure.
- Include enough context for the customer to trust the message.
- Use purpose and custom data for your own tracking.
- Respect consent, opt-out, and country-specific messaging rules for your customer base.

Email Chimes support richer content, but plain text still matters. Send clear subject lines, useful fallback text, and only HTML you are comfortable showing to customers.

## Where MCP helps

MCP currently helps with a narrow, safe subset:

- send a short SMS to an existing saved customer after confirmation;
- list recent message delivery statuses; and
- look up one message’s lifecycle state.

MCP does not expose arbitrary phone-number sends, email sends, schedules, broadcasts, message bodies, or raw recipient contact details. Use the API or dashboard for those workflows.

## Implementation checklist

Before relying on Chimes in production:

- decide whether the message is immediate, scheduled, broadcast, or OTP;
- use saved customers when possible so recipient state stays centralized;
- use idempotency keys for create operations;
- store returned Chime, schedule, or broadcast IDs;
- build delivery-status handling for failed or suppressed messages;
- avoid putting credentials or sensitive personal data in message bodies;
- use templates for repeated operational messages; and
- page or lookup Chimes when support needs delivery evidence.

## Related resources

- [Chimes API reference](https://studio.inttegro.com/machine/go/api/chimes.md) - Immediate sends, schedules, broadcasts, and lookup.
- [Send customer notifications](https://studio.inttegro.com/machine/go/guides/send-customer-notification.md) - Task guide for one-off customer messages.
- [Send scheduled notifications](https://studio.inttegro.com/machine/go/guides/send-scheduled-notifications.md) - Task guide for future delivery.
- [Broadcast to customers](https://studio.inttegro.com/machine/go/guides/broadcast-to-customers.md) - Task guide for campaign-style sends.
- [One-time passwords](https://studio.inttegro.com/machine/go/products/otps.md) - Verification-specific SMS flow.
- [Message templates](https://studio.inttegro.com/machine/go/api/message-templates.md) - Reusable message content.