Sign-in Issues
Signing in to the RingDNA dialer requires both a Revenue.io account and a connected Salesforce org. Revenue.io uses Salesforce OAuth to validate your sign-in session — when you enter your credentials, you do so on a Salesforce page, and once authenticated, Salesforce gives you the option to allow Revenue.io access.
If you hit an error during sign-in, it’s worth doing a quick web search for the exact message first — many are standard Salesforce authentication errors with their own Salesforce documentation.
Most common sign-in problems
- Multiple Salesforce sessions open at once. Try clearing your cache and cookies. This signs you out of Salesforce so you can sign in with a fresh session.
- Salesforce username or password is incorrect. Check your credentials. If you use SSO or a custom domain in Salesforce (for example, acme.lightning.force.com or acme.my.salesforce.com), select Use Custom Domain so you’re directed to the correct Salesforce instance.
- System clock is out of sync. Salesforce requires your system clock to be in sync to generate a valid session token. Make sure your computer is set to sync its clock with the internet.
Find your error message
In some cases you can authenticate with Salesforce, but Revenue.io still can’t grant access to your account. Select the error you’re seeing for detailed steps:
MultipleAccounts — your org maps to more than one account.
Your account was deactivated by an administrator.
Common after a Salesforce sandbox refresh.
Your org limits sign-in to specific IP ranges.
No Revenue.io user is linked to your Salesforce account.
Your Salesforce profile doesn’t have API access enabled.
Your Salesforce org has hit its daily API call limit.