Routing with Salesforce lookup FAQs

This article contains common questions and answers related to Calendly routing with Salesforce lookup.

What types of records can I look up an owner for in Salesforce?

Calendly can lookup an owner for:

• Leads
• Contacts
• Accounts
• Opportunities
• Custom object lookups

Can I do lookups on custom objects in Salesforce?

Yes.

Can I do lookups on custom fields in Salesforce?

Yes, Calendly can do lookups on any standard or custom field in Salesforce.

How can I make sure leads are directed to their assigned rep's booking page when sharing links in mass email campaigns?

Instead of sharing an event type link in the email, you can share a link to a Calendly routing form. This form just needs the email address (you can add more fields if needed) to handle the routing.

You can set up a Salesforce ownership route on the form so that when a prospect clicks the link in your email, enters their email, Calendly will route them to their assigned rep’s booking page. In this setup, the routing form works like a gate to the event type link you'd usually share.

Can I assign the lead to someone other than the usual Account, Lead, Contact, or Opportunity Owner in Salesforce?

You can reference a custom field on the Account, Lead, Contact or Opportunity object for routing leads to another assignee. An example would be an “Account Rep” field or “CSM” field.

How are leads added into Salesforce from Calendly?

• If a meeting is booked, it will be added to Salesforce through the Calendly package.
• If no meeting is booked, the lead is still added to Salesforce through Marketo or Pardot's integration with Salesforce.

Will ownership routing work with Shield Platform Encryption?

It will work differently depending on the type of encryption your organization is using.

• For probabilistic encryption, owner based routing will not work. This is because the type of query we use is not supported. 
  • You can’t include fields encrypted with the probabilistic encryption scheme in the following SOQL and SOSL clauses and functions:
    • Aggregate functions such as MAX(), MIN(), and COUNT_DISTINCT()
    • WHERE clause
    • GROUP BY clause
    • ORDER BY clause
  • For more information, check out this help center article from Salesforce Support: General Shield Platform Encryption Considerations
• For deterministic encryption, our platform will support exact field matching, but will not support partial matches.
  • For example, search by full email address would work, but not search by email domain.
  • Deterministic encryption only supports exact, case-sensitive matches. Comparison operators that return partial matches aren’t supported. For example, LIKE and STARTS WITH statements aren’t supported.
  • For more information, check out this help center article from Salesforce Support: Considerations for Using Deterministic Encryption.