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

# Overview

> Send SMS and MMS messages from SFMC journeys, powered by Tatango

The Tatango integration for Salesforce Marketing Cloud (SFMC) adds a **Tatango Transactional Message** custom activity to Journey Builder. Drop it into any journey to send SMS or MMS messages to your contacts, with delivery status, replies, opt-outs, and cleaned numbers tracked in data extensions inside your SFMC account.

## How it works

1. A contact reaches the Tatango Transactional Message activity in your journey.
2. The activity sends the message through the Tatango platform using your API key.
3. Delivery status updates, replies, and compliance events flow back into three data extensions: `tatango_messages`, `tatango_replies`, and `tatango_subscribers`.

Compliance is automatic: contacts who opted out (for example, by replying STOP) or whose numbers can't receive text messages are skipped on future sends. See the [data extensions](/messaging/sfmc/data-extensions) page for details.

## What you need

* An SFMC account with Journey Builder and permission to create installed packages.
* A Tatango account and an [API key](/messaging/sfmc/setup#step-5-create-a-tatango-api-key).

## Get started

<CardGroup cols={2}>
  <Card title="Setup" icon="screwdriver-wrench" href="/messaging/sfmc/setup">
    Install the package, import the data extensions, and complete the one-time configuration.
  </Card>

  <Card title="Sending messages" icon="paper-plane" href="/messaging/sfmc/sending-messages">
    Configure the activity in a journey and send SMS or MMS.
  </Card>

  <Card title="Data extensions" icon="database" href="/messaging/sfmc/data-extensions">
    The fields behind messages, replies, and subscriber status.
  </Card>

  <Card title="Reporting" icon="chart-column" href="/messaging/sfmc/reporting">
    Build reports from the data extensions with Automation Studio.
  </Card>
</CardGroup>