Admin level settings

8 min read - updated few hours ago

Admin settings page is used to view and adjust the company-wide parameters for users in Revenue Grid (RG).

To access Revenue Grid Settings, click the Settings icon in the top right corner of the RG interface.

Now more detailed about every of the tabs.


These tabs are editable only by users with Admin rights and changes get applied to all RG users company wide.

Control what to sync with Salesforce

Go to Setting → Schedules sub-tab. Control automatic synchronization of all activities generated by sequences with Salesforce.
Allow creating Salesforce campaigns for each sequence.
Enable automatic import of recipients into Revenue Grid from Salesforce email send out widget.

Allow upload prospects from CSV

This checkbox enables option to upload prospects from a CSV file on the Recipients tab, as well as on the Audience tab.

Manage all users

Go to Setting → Users sub-tab. On this tab, Admins can see company-wide Revenue Grid users, their:

• Names
• Emails
• Who are their delegates (if any)
• What is their Dial-out and Texting phone numbers (if any) to perform SMS and Phone call types of steps
• and Role (Admin or a regular User)

By clicking on a user, Admins can see their Account tab, where they can set up delegates, select SMS and Voice numbers, and grant admin rights.

Set company-wide, default signature

Go to Setting → Signature sub-tab. In this editor, Admins can set the default signature which will be applied company-wide. This signature gets overridden by a signature set by users.

Control sending capacity and other limits

Go to Setting → Limits sub-tab. Enforced limits to the number of RE Sequence emails sent by RG users.

Number of sequence email/sms touches an RG user can send per day

To prevent SPAM generation, most email services impose a limitation on the number of emails a user (or automated emailing software) can send through a single email account per specific period of time. The applied limit is 1 email sent per 1 minute.

When Revenue Grid sends out emails, both custom written by a user and automated ones, it respects this limitation, observing the one minute minimum interval between sending emails.

The recommended (default) value of this setting is 500 emails; this value approximates the maximum number of emails that can be sent over a standard working day's span with a one minute interval. It is the emails quantity "bandwidth" shared by all email sequences you run in RG.

When the limit is reached, all remaining automated emails have to be postponed to the following day's sending span defined by the Sequence's Schedule, regardless of the step's actual timeline. Therefore, please consider this standard limit of 500 emails/day per RG user when planning your emailing campaigns.

The maximum value that can be set for this parameter is 1000, that is approximately 17 hours of automated emailing per 24 hours. If you do not set a limited daily Schedule for the Sequence (for example to imitate emails sending by a real person) that is emails sending will be allowed for 24 hours, this increased limit is easily attainable, since the automated emails are sent out by your email server.


In a realistic common case scenario a single RG user can send out around 100 emails per working day; this number is defined by his/her capability to process the recipient's responses to these emails. However, a informative mass email campaign that requires no specific response can make use from the maximum emailing "bandwidth".
Please note that there is also another factor that defines individual emails dispatching patterns, the *Schedule idle* parameter set for Sequence steps

Number of sequence call and misc steps scheduled per day

Set the limit to number of automatic or manual steps of these types that can be scheduled per user per day.

Sequence touches limit per email domain per day

Set the limit of touches per specific domain to avoid overwhelming a certain company with your outreaches.

Sequence touches limit per prospect per day

​ The number of RG sequence emails allowed to be sent to a prospect per 24 hours. This parameter is set depending on the essence of the campaign and the target auditory. Normally the maximum number of such emails should not exceed 5, not to get a prospect annoyed. Note that this number does not include extra “custom” emails message composed by a RG user, for example a reaction to a prospect’s reply or a follow-up clarifying a previously sent email. This parameter’s default value is 5 and the maximum value is 10.

Sequence touches limit per prospect per week

This parameter is similar to the above one, only it sets the RG sequence emails limit imposed over a period of one week. This parameter’s default value is 10 and the maximum value is 20.

Active sequences per prospect

How many active sequences a user can have at the same time.

Customize status mapping to Salesforce

Go to Setting → Status mapping sub-tab. On this tab, Admins can map Prospect statuses to any value of any field in Salesforce for seamless mirroring, as well as create additional Prospect statuses tailored for any possible business need. Updates on this tab will get applied to all users in an Organization.

By default, you get these Person statuses mapped to following values of the selected Salesforce fields (see the picture below).

Select SMS and call provider

Go to Setting → SMS and Calls sub-tab. SMS reach out is available through integration with Twilio or SMS 360.

If you choose to use Twilio, you have to have Twilio account connected to Revenue Grid. Please go to Twilio in order to create an account and get SID and Token values, which you then enter on this sub-tab.

When this Admin level setting is in place, every user will be able to choose a single number from a pool of available to them numbers on their Settings→Account→SMS sender ID drop-down.

Manage signals

Go to Setting → Signals sub-tab. This setting is available to Managers only. Here you can select which signals to run company-wide. Once a signal is disabled, already generated signals of that type will not disappear from the interface until resolved.

Was this article helpful?

Get back to us
We would love to hear from you