Verpasse keine relevante E-Mail mehr. Mit in.bounz für Salesforce.

Mit in.bounz überwachst du alle eingehenden E-Mails. Und importierst die wichtigsten automatisch in Salesforce. Für maximal automatisierte Prozesse. Und mehr Zeit für die wichtigen Dinge.

Mehr Infos


Help Center


1. Introduction

out.bounz takes your email communication in Salesforce to a new level.

The Salesforce app enables you to send, evaluate and optimise emails directly in Salesforce in a fully or semi-automated way.

It also helps your sales department: for example, when sending e-mail messages to stakeholders who speak a different language. Thanks to the integrated DeepL translation, your team processes the email in their own native language and sends it translated into the recipient's language at the touch of a button. Completely

With out.bounz, you can also easily create email templates to automate all your communication depending on the status of your data records.

The following documentation gives you detailed information about the app and describes all the steps that are necessary for the successful installation and configuration of out.bounz.

Do you have questions or need support with the setup? Just send us an email to and we will help you immediately.

1.1. Features

With out.bounz you never have to leave your Salesforce environment again to send a message to your CRM contacts.

Send email messages partially or fully automated. And depending on the status of an object. Here's an illustrative example: A prospect's contact details end up in your Salesforce system. After filling out your web form, send the prospect a personalised email welcoming him or her.

If your prospect books an appointment, a demo, etc. and the status of the object changes, you can send another fully automated e-mail - triggered by the status change. You only have to create the e-mail text once in a template.

Would you prefer to adjust the e-mail again before sending it? Partial automation of your email communication is also possible.

But with out.bounz you can do even more:

  • Compose email templates in your native language and translate them into your recipient's language with a click. This is made possible by the integration of DeepL, one of the world's most professional machine translation platforms.
  • Create flexible email templates and dynamically populate them with the information you need from your Salesforce system.
  • Use simple email automations to minimise time and manual effort in your email communication.
  • Optimise your email campaigns using helpful KPIs such as open rate.
  • Build your individual workflows and customer journeys as you need them. Send emails not only to standard objects but also to your custom objects.

1.2. Interface of out.bounz

The interface for configuring and using out.bounz is composed exclusively of native Salesforce components. You will find the following tabs in the application:

Tabs Description
Home On the home interface you will find up-to-date dashboards of your emals sent with out.bounz by mailboxes or triggers. It also sowhs activities and statistics about your systems mailboxes.
Configurations With the help of a "Configuration" record created during the configuration, you control the basic settings and rules of the application.
Mailboxes Here you create and manage your mailboxes to send emails from.
Templates Here you create and manage your email templates.
Wrappers Here you create and manage wrappers for your email templates and mailboxes.
Schedules Here you can create and manage schedules for automated email sending.
Campaigns Here you can create and manage campaigns for automated one-time email sending.
Notification Settings This is where you set up push notifications for one or more Salesforce users.
Activities Here you can see all activities, like email openings if you activate tracking.
Results List of most actions performed in the application with respective result and information about occurred errors.

2. Requirements

To use out.bounz, some preparatory steps are necessary. These include the installation of the tool itself, of course, but also further configurative measures, which we describe in this chapter.

"Enhanced Email" must also be activated in your Salesforce organisation. You can do this under "Setup" → "Enhanced Email".

Another tip: It will be easier for you later on, especially during configuration, if you have the field names in your system at hand. To do this, you can use the "Salesforce Show API Name" plugin in your browser and have the technical name of your fields displayed directly. Simply search for Salesforce Show API Name in your preferred search engine and install it for your browser.

2.1. Salesforce version

To install and use out.bounz, you need a Salesforce-Enterprise, Unlimited- Developer-Version that can perform API calls (if you want to send via SMTP).

2.2. Email


Sometimes, emails that are not sent from within their email-application but from another server (in this case the Salesforce server), will be flagged as spam, if the server is not recognised as safe. For optimal email sending, SPF and DKIM should be configured.

  • SPF: should be added to the SPF in your email application. All Salesforce domains will be recognized that way.
  • DKIM: Search for “DKIM Keys” in “Setup” and choose “Create New Key”. Now select your Key-Size, Selector (Name of your Key), Alternate Selector, Domain and Domain Match (All of those fields are also explained in Help-Texts in your Salesforce interface). The .txt files are published by Salesforce. In your Domains DNS, publish the CName and alternate CNAME. When this is done and works, the SKIM Key can be activated in the Salesforce-Setup.


If you want to send emails via SMTP you should have your credentials ready. For a more detailed guide on how to setup “Mailboxes” with SMTP settings, please referre to the “Mailboxes” chapter.

3. Installation and Configuration

3.1. Installation

The installation of out.bounz is don via Salesforce AppExchange.

Click the "Get It Now" button to start the installation process.

When you are on the installation page, select "Administrators only". This selection is necessary, otherwise non-authorized users could gain access to sensitive data.


Click "Install" and confirm the message "Yes, grant access to these third-party websites".

As part of the installation, release must be granted to address different interfaces. In addition to the interface, communication must also be established with out.bounz servers for the smooth operation of the tool.

Click "Next" to start the installation.

As soon as your installation is finished, you will find all components belonging to the package in your Salesforce-Org. You can recognize them by the name range "out.bounz".

You may see a notification that says, "This application will take some time to install. You will receive an email when the installation is complete." If such a message appears to you for the first time, don't worry. Just click "Done." Salesforce will then email you to let you know if the installation was successful.

After the installation is complete, we recommend that you check the installation in the "Packages" section under "Installed Packages" in the Salesforce Setup.

3.2. Granting rights of use

The use of the application requires the assignment of certain rights to desired Salesforce users. A basic distinction is made here according to the type of use:

  • out.bounz licenses
  • Salesforce permission sets*

out.bounz licenses are assigned in the "Installed packages" area, directly at the out.bounz package listed there. To do this, click on the "Manage licenses" button and assign the desired users.

The assignment of Salesforce permission sets, on the other hand, is done separately. The following types of Salesforce permission sets are basically distinguished in out.bounz:

  • out.bounz Admin: for administrative full access to all areas of the application
  • out.bounz Manager: for managing Templates, Wrapper, Campaigns and Schedules
  • out.bounz User: for user access

To assign these permission sets, search for "permission sets" in Setup.

Search for "out.bounz Admin", ”out.bounz Manager” and "out.bounz User" in the list and click on the respective set of rights you want to assign to a user.

Go to "Manage assignments" and add the desired users by ticking the checkbox.

3.3. Activate the out.bounz Lightning record pages via the Lightning App Builder

For a basic setup, just assign them for the out.bounz app. Down the line, however, you might want to activate some record pages in other apps, too, depending on whether those records will be viewed from that app. For Objects with multiple record-types you need to set up the record pages under ”App, Record Type and Profile”. Those objects are:

Object Types / Name of record page
Attachment Rule Filter / Attachment Filter Rule Record Page
Limit / Attachment Limit Rule Record Page
Order / Attachment Order Rule Record Page
Preselection / Attachment Preselection Rule Page
Recipient Contact / Contact Recipient Record Page
Dynamic / Dynamic Recipient Record Page
Lead / Lead Recipient Record Page
User / User Recipient Record Page
Sender Dynamic / Dynamic Sender Record Page
User / User Sender Record Page
Scope Field / Field Scope Record Page
Free / Free Scope Record Page
List / List Scope Record Page
Primary / Primary Scope Record Page
Mailbox Gmail / Gmail Mailbox Record Page
Other / Other Mailbox Record Page
Outlook / Outlook Mailbox Record Page
Salesforce / Salesforce Mailbox Record Page
Record Rule Filter / Record Filter Rule Record Page
Limit / Record Limit Rule Record Page
Order / Record Order Rule Record Page

3.4. Configuration

Now, open the out.bounz app in your Salesforce Org, navigate to “Configurations” and open the out.bounz Configuration Record. Here, you can and should do a couple of things:

  1. Set an error email address (optional for minimal setup, but highly recommended)

  2. Configure the translation functionality (optional for minimal setup)
    a. For this, you will need a DeepL Account and the Account’s Authentication Key (Authentication Key). Just copy-paste the key into the UI and hit “Enter”.
    b. In order for translations to work, you need to specify an editing language on template level and specify a recipient language field for your recipient. If at least one of those is empty, there will be no option to translate your mail.

  3. Add additional Recipient Types (optional for minimal setup)
    With out.bounz, you can send emails to any Object/Record in your Salesforce Org. In order to add a new recipient type, just click “New”, next to “Recipient Types”, name your Record, specify the Object, the field, where the email address is located and the Recipient Field Name (The API name of the field at recipient object level that contains the reference to the tartget record (e.g. Contact)). You can also choose an “Order” parameter that lets you choose the order in which the Recipient Records are listed.

3.5. Trial version

You have the opportunity to test out.bounz for 30 days free of charge and in full. You do not need any credit card information. After 30 days, the trial expires automatically and you can no longer access out.bounz.

If you want to test out.bounz in a sandbox, the installation process works exactly like in the live environment. The only exception is if the sandbox is created after installing out.bounz, i.e. if out.bounz is already pre-installed in the sandbox with partially existing configuration data. In that case, it is mandatory to use the "Reset Configuration" button for smooth operation.

3.6. Order licenses

After you have created the configuration record, you need to complete the purchase process.

This step is especially important so that you can use out.bounz!

The license fees for the use of out.bounz will be collected by direct debit from the account you specified. That is how you can deposit your corresponding information.

  • In the out.bounz app, you will find the "Manage Licenses" button in the "Configuration" tab. Clicking on the button opens a login page to your license management area. In this customer portal you will find all important information about your out.bounz licenses, payment information, but also the possibility to add more licenses with a click.
  • To log in, you will receive an individual code by email, which you enter in the login mask.
  • After logging in, the overview page will open with some information about what you need to tell us in order to use out.bounz in the future.

By clicking on "Check your billing address" you can enter a valid billing address. Then click on "Check your SEPA direct debit mandate" to issue a valid SEPA direct debit mandate. You can also find the input masks for your data below in the tabs "Billing" and "Payment".

After you have entered and saved the necessary data, you will receive an email confirmation and a document with all information about your SEPA direct debit mandate.

Note : The confirmation email will be sent to the email address that was entered during the out.bounz download in the Salesforce AppExchange!

3.7. Authentication

Once the record is created and you have deposited your payment information, you need to authenticate with the out.bounz servers to ensure all available functionalities.

This authentication is done once. To do this, simply click on the "Authenticate" button in the created record.

After successful authentication (which may have to be finalized by confirming the OAuth2 query), the user is forwarded to a results page. If successful, the authentication is indicated by a check mark in the "Authenticated" field.

In case of successful authentication, the following message appears:


The check mark under "Authenticated" is then also set in the configuration record.


3.8. Mailboxes

For all active users in the org, we already created a Salesforce-Mailbox for you. You just need to activate them.

There are 4 Types of Mailboxes available:

  • Salesforce
  • Gmail
  • Outlook
  • Other

For the first three, you can authenticate your Mailbox via OAuth, for the “Other” type, you can specify SMTP information and set your password via the “Set Password” button.

Important for OAuth-Authenticated Mailboxes: You can set an app password in most applications and use it to authenticate your out.bounz mailbox, so you don’t have to type in your personal password (and change it every time you change your personal password). For SMTP, just insert Server, Port, User and Encryption and set your password like you’d do in other mailboxes.

Make sure to activate your mailbox before you try to use it. After a successful activation, you will receive an email from that mailbox to your specified Error Email Address from the Configuration Record.

3.9. Templates

To create templates, you navigate to the tab “Templates” and click “New”. Now you can specify the following information:

  • Name: Choose a simple but telling name. You will need this to find and choose your template later.
  • Type
    1. Mixed: You can use HTML and “normal” text
    2. HTML: The whole template-body will be interpreted as HTML

3.9.1. Scopes

Scopes are used to give you the ability of loading data into the template. For example, if you define the primary Scope as “Lead”, you can access all fields of the “Lead” object in your template. You will need a Scope to define Recipients, Dynamic Senders and to reference data in your email. Create a Primary Scope with the Button “Create Primary Scope” and selecting the Object you want to use. You can always add more Scopes to your template, once your Primary Scope has been created, if you need data from another object in your mail. You can always reference the current Users' data, even if there is no Scope defined.

  1. For Scopes you can also define an Attachment Rule. Attachment Rules can determine which Attachments can be pulled and added to the template. You can either Filter, Limit, Order or choose a preselection with Attachment Rules.
  2. With Record rules, you can determine which records should be considered in Free and List Scopes.
  3. Now, you can add a Sender to your template by creating a Dynamic or User Sender Record.
    a. Dynamic Senders need to have a User-Object-Scope
  4. Attachment Records are used to manage attachments to your emails. To upload an attachment, create a new record, name it appropriately, and click “Upload Files” under the “Files” section. You can also pull attachments dynamically from Scopes. For example, an invoice attachment on your opportunity can automatically be pulled into your template when you have an opportunity scope (this is mostly useful for sending email via button).
    a. You can also limit the amount of attachments pulled to your template with the “Attachment Batch Size” parameter. Then, attachments will be pulled in those batch sizes. For example: You have 25 possible attachments from different scopes that can be pulled to your template. You set the batch size to 10. Initially, you will see the first 10 attachments. However, if you need an attachment that is not under those 10, you can pull the next 10 attachments, and so on. You can then choose which attachments should be attached to the mail you want to send.
    b. You can also check the “Attachment Required” checkbox, so the days of needing to send the “Sorry I forgot the attachments I mentioned, here they are” emails are well in the past.
  5. With Field Updates, you can specify whether and which fields of a scope should be updated once an email has been sent. For example, one important field update that should be created for most templates that are to be used with a scheduler is one that updates the sending condition to false after the email has been sent to make sure that no duplicate emails are attempted to be sent (out.bounz has an inbuilt duplicate management that will detect if the same mail would be sent to the same recipient and not send that duplicate mail, but it is best practice to update the sending condition).
  6. Other Information displayed on the template record page:
    a. Results: Result objects with information on sent emails that used that template
    b. Email Messages: Email Message objects with the email sent from that template
    c. Template History:
    History of edits on the template objects
  7. Now you can fill your Email template with data:
    a.Subject” is quite self-explanatory, as it saves the string that will be the mails subject. Here you cannot use HTML Tags as they will not be interpreted.
    b.Body”: Here you can write your text in either pure HTML or mixed, depending on your template type. For examples on how to use Scopes in Templates, please look at the examples below.
  8. Notification Settings can be used to determine when a User should be notified (First opening/click or all openings/clicks; Depending on whether tracking is enabled) and also for which template. In order to work, they need to be activated.
  9. Depending on whether tracking is enabled, you can see the openings and clicks on emails in the “Activities” tab

3.9.2. Wrappers

Wrappers are used to wrap information around your email. You can have Wrappers on a Mailbox-Level (e.g. for footers) or Template-Level (e.g. reoccurring specific information for templates like information for customers about current and new products).

3.9.3. Schedules

Schedules are, as the name suggests, used to schedule email sending. For the creation of a new schedule record, you need a telling name, a template and the API Name of a field on the level of the templates' primary scope that determines whether an email should be sent. You can also specify a user to send the mails from, overriding the templates' sender, and filter the user's mailboxes by inputting the string name of the mailbox that has a connection to the user into the “Mailbox” field. Schedules are, by default, evaluated every 5 minutes.

Please note: The possibility to schedule emails is only available from ordering ten or more licenses.

3.9.4. Campaigns

Campaigns are, basically, schedules that will only be evaluated once. The only addition to the schedules' input is the possibility to set a scheduled date for when the campaign should start. (You can, for example, schedule a campaign with Christmas greetings to all your customers to the last business day before next Christmas at 08:00am).

4. Operational use of out.bounz

In this chapter we describe how you can get the most out of out.bounz. This also requires minor configurations, which - like the configurations already done - only need to be carried out once.

We will show you the settings based on a few use cases to make the configuration more clear. Of course, you can configure and use out.bounz for your own individual use case and with your own custom objects.

4.1. Create a campaign

Preliminary work: You need a valid configuration and at least one active mailbox.

For this example, we want to send a friendly hello to all leads in our org. We create the following template:

  • Name: Hello World

  • Type: Mixed


We hit “Save” and then click on “Create Primary Scope”, search for Lead, check the checkbox and hit “Create”.


We now create a Field Scope (under Scopes - New) with the following information:

  • Name: Lead_Owner
  • Object Name: User
  • Parent: Lead (Name of the Primary Scope)
  • Field Name: OwnerId

Now, we create a Dynamic Sender with the following information:

  • Name: Lead Owner
  • Scope: Lead_Owner
  • Template: Hello World

Now, our Leads will receive their emails from the user that is the lead owner (All users that are Lead owners for your test should have an active mailbox in order for this to work properly).

Next, we create a recipient. We can create a Lead-Recipient, however, let’s choose a dynamic recipient to explain the process. We create the following dynamic Recipient:

  • Name: Lead Recipient

  • Scope: Lead

  • Template: Hello World

  • Category: To

  • Email Field Name: Email


Finally, we can fill the email with content.

Input the following information:


Friendly Hello from {Lead_Owner.Name}


Hello {Lead.Name} from {Lead.Company}
I wanted to say a friendly hello to you and get in contact,

Kind regards,

Now, if we wanted to use this template to sent emails via button, it would be good to go. However, for Campaigns and Schedules we need to do some extra steps:

  1. We need a field of type boolean on the Lead object that is true, if our mail should be sent and false otherwise. For this, let’s create the following field:

    a. Type: Checkbox
    b. Default Value: Checked
    c. Field Name: Send_Mail_c

  2. We create the following Field Update Record:
    a. Name: Update Send Mail
    b. Operator: =
    c. Condition Value: true
    d. New Value: false
    e. Scope: Lead
    f. Field Name: Send_Mail__c


Now, if an email that uses this template is sent and the “Send_Mail__c” checkbox is checked, it will be unchecked.

Having done this, we can now create a new Campaign. We use the following information:

  • Name: Lead Hello World

  • Template: Hello World

  • Field Name: Send_Mail_c


After that, we click on the campaign, set the scheduled date to now and hit the “Start” Button. The page the button will open will also ask for a scheduled date but autofill it to the date set previously. After starting the Campaign, its status will change from “Draft” to “Planned” once the next cycle of the schedule executes, the Campaign will begin to end emails. You can always abort a campaign with the “Abort”-Button. However, emails sent can’t be undone. After the first email has been sent, the Status will update to “Running” and after having sent all emails, it will change to “Finished”.

4.2. Button for Translation

In this example, we will create a button on Lead level to send the same email as in the Campaign earlier, but with the added flexibility of translation and customisation of the template. For this, we create a Detail Page Button called “Send Mail“ with an URL of the following Syntax:

/apex/outbounz2__SendMessage?id={![object].id}&template=[TEMPLATEID]&user=[USERID]&mailbox=[MAILBOX]&language=[LANGUAGE CODE]

[object] is the object of the templates' primary scope.

The Template Identifier can be found on the Template Record Page and has the following form:

OZTxxxx where x is a number. The first Template has the Identifier OZT0001. Any other parameters, apart from the template ID are optional.

After adding the Button to the layout, you can now use it, to send a single email to the defined recipient on your record. After clicking the button, you will see that the template has been loaded with the correct data from the defined scopes. You can now edit the email to your liking and also add other recipients (Here you can either select a Recipient Type or an adress and just type in the adress you want to send the mail to).

Finally, you can also schedule the sending of the mail or preview the final layout before sending your mail by hitting “Send”.

Now, let’s add the translation functionality. For this we need to do two things:

  1. Add a language to our Template. In this example we simply type in “English”

  2. Add a Language Field to our recipient record. This is already configured for the out-of-the-box Lead Recipient, however for our Lead Recipient, we simpy add the “outbounz2_Language__c“ field into the “Language Field Name”. Now, we will get the option to translate our email into the language, specified in our lead record. (e.g. Add FR into this field for french, DE for german, etc.). Instead of this, you can add the &language=DE parameter to the URL inside the button to enable translation to, in this example, german.

5. Error Handling

The more diverse the functionality of a system, the more complex the configuration. Errors happen in the process. A central focus of out.bounz is to support users in analysing configuration errors as best as possible and to avoid input errors directly.

Should you nevertheless encounter an unknown error message, simply send a screenshot to and we will help you.

5.1. Data entry error

In the event of errors due to incorrect entries or connection problems, the user receives a corresponding message.

If there is no indication of an error, it can generally be assumed that the triggered action was successful.

If an error message is unclear, we recommend consulting the Salesforce administrator responsible for the installation.