Sync Company Information to CRM from Kixie and Yesware Prospector
B
Braeden Ager
Request to sync company information to the CRM from Kixie and Yesware Prospector so that companies can be created from these syncs and contacts can be properly assigned to the companies.
Log In
D
Daniella Lukach
Needed behavior + optional company “general email” field
What we need (minimum):
- Dedupe contacts on create/sync using:
- email match (case-insensitive)
- phone match (normalized, ideally E.164)
If a net-new contact must be created, auto-associate to Company when:
- incoming phone matches Company main phone, and/or
- domain/website matches (when available)
If matching confidence is not perfect, show “possible duplicate / possible company match” suggestions immediately (or queue for review).
Optional (nice-to-have):
allow storing a general company email directly on the Company profile (e.g., info@ / office@ / billing@) without creating a Contact. This prevents creating fake contacts just to hold a shared inbox and keeps the CRM cleaner.D
Daniella Lukach
Vendasta Find Leads → Yesware Prospector
also breaks company associationWe see the same issue with Vendasta’s own Yesware Prospector workflow, even without Kixie.
Repro (Find Leads → Yesware):
- We use Vendasta CRM Find Leads to create/import a Company (general business info often from Google Maps/public listings).
- We then use Yesware Prospector (paid tokens) by entering the company name to pull a real decision-maker contact.
- Yesware creates/syncs a new Contact into Vendasta.
- That contact is not automatically associated with the Company record that already exists in Vendasta — and no match suggestion is offered.
So we end up with a Company and a Contact that should be linked, but aren’t, which again forces manual cleanup and breaks downstream workflows.
D
Daniella Lukach
This isn’t just a data hygiene annoyance — it makes automations nearly impossible to trust.
We rely on lifecycle stage changes + workflow automation (Zapier/Make → Asana tasks/subtasks, onboarding sequences, follow-up tasks, reporting). With duplicates/unlinked contacts:
- Automations trigger on the wrong record (or multiple records)
- Task creation duplicates (or misses) happen
- Activity history + attribution are scattered
- Any “single source of truth” logic collapses
Even a perfectly built automation stack can’t function if contacts are duplicated and not linked to the right company consistently.
D
Daniella Lukach
Repro (Kixie → Vendasta):
A Company record already exists in Vendasta with a main phone number saved on the company profile.
- A rep makes a call in Kixie to that same number.
- Kixie sync creates a new Contact in Vendasta.
- Vendasta does not match that new contact to:
*an existing Contact (by phone/email), or
*the existing Company that already has that phone number, and
- we don’t get a “possible match / dedupe” suggestion.
Result:
a growing pile of duplicate contacts (often partial/placeholder records) that require manual cleanup + manual company association. This scales terribly in real outbound calling.D
Daniella Lukach
+1 — we strongly support this request, and want to add detailed context because this is causing real CRM breakdown for us. The core issue is
contact matching + company association during sync
(especially by phone number and/or email
) — the current behavior creates duplicates and makes automations nearly impossible to rely on.