Once configured, the integration runs on its own and does four things:

You'll need:

You need a field on the Account object to record when someone opts out of SMS.

Recommended: a picklist called SMS Status

Alternative: two checkboxes, if your organization tracks opt-in and opt-out separately

Optional: a date field to record when someone opted out

To create these: Setup → Object Manager → Account → Fields & Relationships → New

Build a tabular report on a Person Account report type containing the people you want to message.

Your report must include:

Use report filters to exclude anyone you don't want to message — board members, major donors, Do Not Contact, and so on.

Report formats that work: tabular reports only.

Report formats that don't work: summary, matrix and joined reports, bucket fields, custom summary formulas, and row or column groupings.

This field is what lets Tatango update an existing message on a record instead of adding it again. Tatango gives every message its own ID, and this field is where that ID gets stored in Salesforce.

To create it: Setup → Object Manager → Activity → Fields & Relationships → New

Create this on Activity. That covers both Tasks and Events, and messages are logged as Tasks.

Go to My Account → Integrations → All Apps → Salesforce Nonprofit Cloud and name your app.

Then work through the setup screens:

You don't need to map the Salesforce Account ID. The integration creates a salesforce_account_id field on your Tatango list automatically and keeps it updated.

This is what sends opt-outs back to Salesforce.

Two reports send message activity back to Salesforce — All replies and Recipients. Both go to the same email address, and Tatango works out which is which from the file it receives.

The setup wizard showed you a URL, like this:

Take the ID from the URL — the part before .integration-hook.com — and put it between trigger+ and @traymail.io:

That single address receives both reports.

Here's an article on how to setup destinations.

In Tatango Reports, schedule both reports to be delivered by email to the address you built above. We recommend setting up a daily scheduled report. Here's an article on how to schedule reports.

When you build each report, include the salesforce_account_id column.

This is how messages are matched to the right Salesforce record. Without it, the integration falls back to matching on phone number, which is less reliable — in particular it won't find records whose phone number is stored with an extension, like 555-123-4567x890.

Open a Person Account and go to the Activity tab, then expand Past Activity.

Every message appears as a completed activity.

A broadcast you sent:

A reply you received:

Because both carry the campaign name, the activity timeline reads as a conversation.

Here's an example of how it would appear in Activities -

Every supporter synced by this integration can be tagged and you can also add your own tag during setup. This is useful if you're running more than one instance of the integration:

Each supporter carries the tag from the report they came from, even if they're on the same list. You can then use those tags to segment campaigns or trigger recurring messages.

To skip this, leave the field blank.

Run or save the report in Salesforce, then refresh the setup page. Salesforce only makes reports available through the API once they've been interacted with.

Also check that the report is visible to the Salesforce user you connected with.

This almost always means Tatango_Message_Id__c is missing, or was created without External ID and Unique checked. Correct the field in Salesforce — see Step 1c — and future deliveries will update the existing activity instead of adding another copy.