Solicitation Request Portal

To standardize incoming requests, and significantly ease the burden of client initiation for solicitations, we have developed an automated Solicitation Request Portal, separate from the current RapidRatings platform.

The solicitation request portal requires use of one of two mail servers: either an external Mailgun® gateway service or a client’s actual SMTP mail-server. This is usually a choice determined by the IT or Tech team at the client.

Regardless of the mail-server utilized, program managers will have the same user experience.

Option 1 Mailgun Method

1. When using the Mailgun® gateway service, a client has to give RapidRatings permission to use their email domain, and RRI handles all security for its use

2. The system requires our clients take certain actions to ready their mail system:

3. We integrate with a 3rd party mail sender called Mailgun®, who will send emails on behalf of approved email domains

4. Using a secure API, our system will send each mail request to Mailgun®, who will then trigger an email to be sent out on behalf of the appropriate sender from our client’s email domain

Option 2 SMTP Relay Method

1. When using the client’s own SMTP mail-server, the client gives RRI access (credentials) to a single account, and the client must ensure security for use

2. This system requires that our clients provide certain information and authorization to permit RRI use of a single client mail account

3. Any introductory letters will be sent via the approved email address directly through the client’s own SMTP mail-server. In order for this process to function smoothly, our client must provide specific SMTP mail-server details to RRI as outlined below: SMTP Server Name, SMTP Port, Username & Password, SMTP Secure Connection: TLS or SSL

What do we need from you?

1. Written permission to send emails on client’s behalf

2. Approval of client introduction letter for new requests

3. List of emails to be copied on letters (typically primary users)

4. A “reply-to” address, should the Target respond to the introduction letter (i.e. no-reply@client.com)

5. Address the emails will be coming from (this is the account the client has provided credentials for)

6. If metadata is part of the account, specification of required fields for request submission (i.e. client unique id)

7. For SMTP option:

1. SMTP Server Name (i.e. smtp.sbcglobal.yahoo.com) 

2. SMTP Port (i.e. 465) 

3. Username (i.e. permitted email address, user@client.com) 

4. Password (i.e. password to access user@client.com email address) 

5. SMTP Secure Connection: TLS or SSL