Users are more likely to engage with SMS messages from senders they know and trust. With this in mind, Iterable allows you to attach your brand's contact card to your SMS campaigns. Users who save it to their device have an easier time recognizing your future messages.
This article describes how to create contact cards and attach them to your SMS campaigns.
NOTE
To add MMS to your Iterable account, talk to your customer success manager.
# In this article
- How do contact cards work?
- Creating and attaching contact cards to SMS campaigns
- Modifying contact cards
- Deleting contact cards
- Personalizing contact cards with Handlebars
-
Frequently asked questions (FAQ)
- I don't see a phone number field in the contact card editor. Where is it?
- Are contact cards sent as MMS messages?
- Can I send a contact card and a separate image in the same campaign?
- What if my phone numbers change?
- How many phone numbers can a contact card contain?
- Can I use Handlebars in my contact card definition?
- How many contact cards can I attach to a single SMS campaign?
- Can I attach a contact card that isn't associated with the same sender as the campaign?
- Can I use Handlebars to personalize the phone numbers in a contact card?
- If I modify a contact card, will the change be visible to people who've already saved it to their devices?
- What kind of vCard does Iterable send?
- Want to learn more?
# How do contact cards work?
A contact card is an electronic business card that you can attach to a SMS campaign as a vCard 3.0 (Virtual Contact File, or VCF). When users receive a contact card, they can save it to their device to make it easier to recognize future messages from your brand.
It contains the following details:
- A company name
- A phone number (gathered automatically by Iterable from the associated SMS sender)
- A website URL
- An image URL (such as a logo)
- A company email address
Every contact card is associated with one of your project's SMS senders. An Iterable project can have many contact cards, and you can have multiple contact cards per sender. They're defined in the contact card library that's available as you set up the content (template) for a campaign.
# SMS usage
Because a contact card is an attachment, your message converts to MMS, which counts towards total MMS sent in your account usage. Additionally, you can only send either a contact card or an MMS attachment, but not both.
# Personalization
When you send a campaign with an attached contact card, Iterable regenerates the card for each of the campaign's recipients. This means you can personalize the card's fields with Handlebars. See Handlebars in contact cards to learn more.
# Creating and attaching contact cards to SMS campaigns
To attach a contact card to an SMS campaign, edit the campaign's content (template):
-
In the Details section, next to Contact cards, check Send an SMS contact card with this message.
IMPORTANT
If you send a contact card to an iOS user before they've ever replied to one of your SMS messages (for example, to consent to messaging), they'll receive your contact card as a file attachment, without a friendly preview. They can still click this file and save it to their address book, but it's best to send contact cards after the user has replied to one of your messages.
-
If there's an existing contact card you'd like to send, select it from the dropdown menu.
Make sure to choose a contact card that's associated with the same sender as your template. If you choose a card for a different sender (maybe to do some cross-brand promotion), it won't help users recognize future sends from the current sender.
If you attach a contact card, you can't also include an image in your campaign (other than the image that's part of the contact card itself).
-
To create a new contact card, click Manage contact card. This brings up the Contact cards window:
In this window, choose Add Contact Card.
Then, enter the following information, then click Save:
- Company name — The company name to associate with the sender.
- Sender - The sender to associate with the contact card (including that sender's phone numbers).
- Website — The URL of the sender's website.
- Image URL — An HTTPS URL to an image that you'd like to associate with the contact card. This image should be square (ideally 400x400px) and no more than 900kb.
NOTES
At send time, Iterable fetches your sender's phone numbers from the underlying SMS provider, adding them to the contact card you're sending. Because of this, the contact cards you send always have your sender's current phone numbers, even if you've changed something under the hood.
In contact card fields, you can use Handlebars to reference user profile fields and data on campaign-triggering events. For more information, read Handlebars in contact cards.
When you're done, click Add to template.
To preview an SMS message notification, the full message, or the contents of an attached contact card, use the device preview (under Design). Use the dropdown menu below the previewer to switch between these different kinds of previews.
Finish editing your campaign, test it thoroughly, and send it when you're ready.
# Modifying contact cards
In the Contact Cards window, you can create new contact cards, or you can modify the ones that already exist.
Remember, though: when you modify an existing contact card, the change doesn't automatically propagate to users who've already saved it to their devices. You'll need to send the card again, and your users will have to save it again or update their existing contact.
# Deleting contact cards
To delete an existing contact card that you no longer need, from the Contact Cards window, select the contact card, click Edit, and click Delete contact card.
WARNING
Deleting existing contact cards impact every location the contact card is used and cannot be undone.
# Personalizing contact cards with Handlebars
When you attach a contact card to a campaign, Iterable regenerates that contact card for each of the campaign's recipients. Because of this, you can personalize the contact card, using Handlebars to reference dynamic fields on user profile fields and campaign-triggering events.
For example, to set the value of a contact card's Nickname to the name of a
familiar account rep, as stored on each user's profile, you might use a
Handlebars expression such as {{accountRep}}
(wherever you store that
information).
To resolve Handlebars expressions in contact cards, Iterable uses:
- Universal merge parameters
- Fields from a campaign-triggering event (if there was one)
- User profile fields
(In that order of precedence).
NOTES
You can't reference data feeds in contact card fields.
-
For a contact card's Image URL field, you can provide a single Handlebars expression or a full URL with no Handlebars at all. For example, these are valid image URLs:
{{imageUrl}}
https://example.com/images/contact-photo.png
But this is not:
https://example.com/images/{{city}}/contact-photo.png
# Frequently asked questions (FAQ)
# I don't see a phone number field in the contact card editor. Where is it?
Iterable automatically adds phone numbers to your contact cards.
When setting up a contact card, you'll associate it with one of your Iterable project's SMS senders. And when you attach the contact card to a campaign, Iterable grabs the sender's phone numbers from the underlying SMS integration, adding them to the contact card. No need to enter the phone numbers manually.
# Are contact cards sent as MMS messages?
Yes, contact cards are attachments and they are sent as MMS messages. Each time you send a contact card with a campaign, the contact card and message body together count as one MMS sent.
# Can I send a contact card and a separate image in the same campaign?
No. You can attach a file (of a supported type), or a contact card, but not both.
# What if my phone numbers change?
If any of your phone numbers change, you don't need to do anything. The next time you send it, Iterable automatically grabs the latest phone numbers.
Remember, though: changes to a contact card don't automatically propagate to users who've already saved the card. You'll need to send it out again.
# How many phone numbers can a contact card contain?
We've tested cards with up to 50 phone numbers.
# Can I use Handlebars in my contact card definition?
Yes, you can use Handlebars to personalize your contact cards. For more information, read Handlebars in contact cards.
# How many contact cards can I attach to a single SMS campaign?
You can send one contact card per SMS campaign.
# Can I attach a contact card that isn't associated with the same sender as the campaign?
Yes. You can attach any contact card to an SMS campaign, regardless of the template's sender. For example, this might be a useful way to cross-promote different brands.
Be careful, though. Mismatching contact cards and senders may confuse your users, since they may expect that they're saving a contact card for the current sender, even if they're not.
# Can I use Handlebars to personalize the phone numbers in a contact card?
Not yet, but we may add this in a future release. If you'd like to do this, please tell your customer success manager!
# If I modify a contact card, will the change be visible to people who've already saved it to their devices?
No. If you modify a contact card, it doesn't automatically update on devices where it's already saved. If necessary, send a new contact card and ask people to update.
# What kind of vCard does Iterable send?
Iterable sends vCard 3.0 contact cards, also called a Virtual Contact File (VCF).
# Want to learn more?
For more information about some of the topics in this article, check out these resources. Iterable Academy is open to everyone — you don't need to be an Iterable customer!
Iterable Academy
Support docs