Deduplication Settings
Deduplication prevents creating duplicate records from your CRM. You can enable deduplication at the contact, company, lead, or deal level.
1. Contact-Level Deduplication (Email-Based)
Prevents sourcing prospects that already exist as contacts (matched by email).
Optional filters can refine the logic (e.g., only dedupe if
lifecycle_stage = customer).
2. Company-Level Deduplication
Excludes prospects from the same company domain already in your CRM.
Filters can be applied (e.g., by industry, company size).
Push Settings
Katie can automatically push contacts, companies, and activities to your CRM when specific outbound actions occur.
Supported Push Triggers
First Outreach: When Katie sends the first email or LinkedIn message.
LinkedIn Connection Accepted: When a request is accepted.
Positive Reply: When a reply is marked positive.
Phone Fetched: When a phone number is enriched.
Field Mappings
Each trigger can be customized with field mappings:
Static: Fixed value (e.g., Lifecycle Stage =
preMQL).Dynamic: Prospect attribute (e.g., Seniority).
Send on Update: Choose whether the mapping updates existing records or only applies on creation.
⚠️ Note: Field values are required when sync is enabled. Empty values will cause an error.
Push Configurations
Contacts Push Configuration
Can be triggered by events (first outreach, LinkedIn accepted, etc.)
Each trigger can have its own field mapping configuration
Leads Push Configuration (only for SalesForce)
Can be triggered by events (first outreach, LinkedIn accepted, etc.)
Each trigger can have its own field mapping configuration
Companies Push Configuration
If enabled, companies will be created if they don’t already exist
You can add your desired field mapping.
Email Activity Push
If enabled, email activities are logged inside your CRM with a link to the prospect matching entity.
Update Existing Data
When enabled, Katie updates existing CRM records with the latest info, without creating duplicates.
It searches for a matching contact/lead by email or phone number.
Prospect "Sync to CRM" action
Pushes the prospect as a contact/lead (by configuration) and company (if needed) to the CRM connected.
CRM as Source for Campaigns
Once your CRM is connected, you can create a campaign using a CRM list as the source.
HubSpot: Campaigns using HubSpot as a source are linked to a list of type Contact or Deal.
Salesforce: Campaigns using Salesforce as a source are linked to a specific entity type of Contact or Lead.
Campaigns using a CRM source are live and will continuously fetch new entities as long as the campaign is active.
After selecting the source, you need to map the CRM fields to the person's fields. Each person must have a unique identifier—either an email, LinkedIn URL, or a combination of full name and company. We’ll attempt to enrich the prospect using this identifier, though enrichment is not required.
You can also apply filters to narrow down which entities are included in the campaign.