The examples below are a very rough estimate of the number of API calls Playbooks will make to your CRM since the number of factors can vary wildly.
30 dials and 20 emails are completed = ~105 API Calls
This is at least 50 API calls to sync the 50 completed tasks plus roughly 5 more to get the Task schema. There will be an additional 50 API calls for updating the "Playbooks Play Status" field on the Lead or Contact record.
Add 1 Lead/Contact to Playbooks = 3 API Calls
When you add a record to Playbooks from the Dashboard's "Add To Playbooks" button, 1 API call will retrieve the schema* (description of the fields on the object), 1 API call will retrieve record data and 1 API call to save any edits made to the record.
(*We only need to get the schema 1x/hour.)
Let's say you've got an Automation Rule to add new records to a Play. This rule only applies to the BDR team consisting of 15 users and Automation Rules run every 10 minutes. And let's say on average you get 200 new records each day.
Automation Rule will run 144x per day
144 API calls X 15 users = 2,160 API calls to look for qualifying records
+200 API calls to enroll the new records
+200 API calls to update the record with the Play name
Total = 2,560 API Calls
If the Automation Rule had an action to “Mark Successful and Remove from Playbooks”, that would increase the number of API Calls. Depending on the number of qualifying records, there could also be an increase in API Calls.
Other Automated API Calls
- Do Not Call / Do Not Email: Playbooks will check throughout the day for records that have been flagged as Do Not Call/Do Not Email. This would add 5 API calls throughout the day.
- Email Interactions: (Salesforce customer only). Due to email tracking, when an email recipient opens an email, clicks on a link, or forwards the email, that information will need to be synced back to the CRM. Each event would result in one API call.
- Neural Score Updates: Recent optimization now batches 25 updated scores and sends over as 1 API call.