Send a campaign to multiple recipients with bulk send

Bulk send lets you send one Reachdesk gifting campaign to multiple recipients at once. You can upload recipients using a CSV file or add recipients manually.

Reachdesk validates bulk send data in real time. If the system detects missing or invalid information, it surfaces the affected contact fields and details exactly what needs to be fixed before you can proceed.

Recipients in a bulk send do not need to exist in your CRM to claim their gift. CRM verification only applies to gifts claimed via dynamic/multi-use links.

Start a bulk send

To send a Reachdesk campaign to multiple recipients:

1. Click Send Gift.

2. Select the campaign you want to send.

3. In the Recipient step, choose Bulk.

4. Choose one of the following bulk recipient options:

   • Drag and drop a CSV file

   • Add contacts manually

Upload recipients using a CSV file

You can upload up to 5,000 contacts at once using a CSV file. To prepare a bulk send CSV file:

1. In the Bulk recipient step, click Download CSV Template.

2. Open the downloaded CSV template.

3. Complete the CSV template using the exact column format provided in the file.

4. Save the completed CSV file.

5. Return to Reachdesk.

6. Drag and drop the CSV file into the CSV upload area, or click the upload area to select the file from your device.

💡 Tip: The CSV template dynamically changes depending on the campaign type you select. Download a fresh CSV template before each bulk send to minimize upload errors.

Understand the CSV template fields

The downloaded CSV template automatically includes the fields required for your specific campaign. The template features

• Columns marked as Required when a field must be completed.

• Extra guidance in parentheses, such as accepted formatting or field values.

• Campaign-specific fields based on the chosen Reachdesk campaign type.

For example, a required country field appears as Country (Required). If you select a warehouse Bundle campaign, the template includes a Delivery Method column that accepts explicit values of either standard or express.

Use the Sender email column to send on behalf of another user

Only Admins and Campaign Managers can send on behalf of another Reachdesk user. The Sender email, Wallet Type, and Wallet Currency columns remain visible in the CSV template for both eligible roles.

If you add an email address to the Sender email column, the subsequent wallet fields control the budget drawdown:

• Default Fallback: If you leave the Wallet Type and Wallet Currency columns blank, the campaign automatically draws from the individual user wallet of the person listed in the Sender email column.

• Explicit Wallet Routing: If you choose to specify a wallet, you must provide a valid wallet type and currency that the sender has active access to.

• Multi-Team Defaulting: If you route to a Team wallet type and the sender belongs to multiple teams, Reachdesk will automatically pull the budget from their designated Default Team wallet.

⚠️ Role Restriction: If a user assigned the standard Sender role inputs a value into the Sender email column, the platform ignores the input. The campaign will simply process under the identity and wallet of the user uploading the file.

Follow CSV formatting requirements

To completely avoid CSV upload errors, ensure your file meets these validation requirements:

• Use the exact format and headers from the downloaded CSV template.

• Download a fresh CSV template before preparing every new bulk send.

• Keep all physical address fields (Street 1 and Street 2) and company name fields to a maximum of 30 characters. Fields exceeding this limit will trigger a validation error.

• Review all real-time errors or warnings displayed after uploading your file.

• Fix all missing or invalid contact data before attempting to continue.

• If you need to include custom personalization variables, read the Custom CSV Variables for Bulk Sends support article.

Fix CSV errors after uploading recipients

After uploading a CSV file, Reachdesk highlights any contacts with pending issues. You can correct these:

1. In Reachdesk, by editing each affected contact directly within the platform's interface.

2. Locally, by editing the CSV file on your device, then click Replace CSV to upload the corrected file.

To edit a contact directly in Reachdesk:

1. Locate the contact row displaying a pending error flag.

2. Click the pencil (edit) icon for that contact.

3. Correct or fill in the invalid or missing information.

4. Save the updated contact details.

💡 Tip: If you cannot source the required information for a specific recipient, click the trash icon to remove that row from the bulk send entirely. You can only proceed to the next step once all contact rows are valid.

Complete the Payment step

Reachdesk automatically calculates and validates the total estimated cost for all valid contacts in your bulk send during the Payment step. Review your selected funding source and estimated costs before moving forward.

⛔ Budget Limitation: Team Wallets are not supported for bulk sends. Senders must select either an Organization Wallet or an individual User Wallet to fund bulk campaigns.

Review and send the bulk campaign

In the final Review step, you can verify the precise send details for each recipient before launching the campaign.

1. Go to the Review step.

2. Click the dropdown arrow next to a recipient's name to expand and audit their individual send data.

3. If all bulk send details are correct, click Send now.

Frequently Asked Questions 

Will Reachdesk push bulk send data back to Salesforce?

Reachdesk automatically logs bulk send activity as completed tasks in Salesforce only when all of the following conditions are met:

• The Reachdesk campaign is actively synced with a Salesforce campaign.

• The recipient row in the CSV contains a valid email address.

• The email address in the CSV exactly matches an existing Contact or Lead record email in your Salesforce instance.

Reachdesk will not log a task if the recipient was processed without Salesforce linkage.

Note: If a recipient does not match a CRM record, they can still successfully claim and redeem their gift. Lack of a matching CRM record only prevents the transaction from logging back as a task; it does not block the claim.