Getting your sales tools to play nice together isn’t just a “nice to have”—it’s table stakes if you want your team closing deals instead of chasing down data. If you’re using Koncert to power your outbound calling and Salesforce as your CRM, connecting the two can save hours of grunt work and cut down on error-prone data entry. This guide is for admins, sales ops folks, or anyone tired of jumping between tabs.
Here’s how to actually get Koncert and Salesforce working together, what to watch out for, and what’s honestly not worth your time.
Why bother integrating Koncert with Salesforce?
Let’s keep it real: the only good reason to add another integration is if it makes life easier. Here’s what you get when these two are set up right:
- Call activity and outcomes logged automatically in Salesforce (no more “I’ll update it later” excuses).
- One source of truth—no more double-checking which tool has the right info.
- Easier reporting on calls, connects, and outcomes.
But don’t expect miracles. If your data is already a mess, integration won’t magically fix it. It just means you’ll have matching messes in two places.
Step 1: Get your ducks in a row
Before you start clicking, do some basic prep. Here’s what you’ll need:
- Salesforce admin access (not just a standard user).
- Koncert admin login.
- A clear idea of which Salesforce objects you want to sync (Leads, Contacts, Accounts, Tasks, etc.).
- A test Salesforce user and a sandbox environment, if possible. Never test integrations in production first unless you like living dangerously.
Pro Tip: If your Salesforce is heavily customized, make a list of the custom fields and automations that could affect call logging. Koncert’s out-of-the-box sync won’t magically know about your custom triggers or weird field mappings.
Step 2: Connect Koncert to Salesforce
Most of the time, Koncert connects through Salesforce’s OAuth process. Here’s how it usually goes:
- Log into Koncert as an admin.
- Head to the Settings or Integrations section.
- Find the Salesforce integration option and click Connect.
- You’ll get bounced over to Salesforce to log in and authorize the app. Make sure you’re using an admin account with API access.
- Approve the permissions Koncert asks for. If you’re squeamish about this, check with IT — but most of the time, “Full Access” just means Koncert needs to write call data and read leads/contacts.
Heads up: If your org has extra login security (like IP restrictions or login hours), you might need to whitelist Koncert’s IP addresses or tweak Salesforce settings. Don’t ignore security popups—they can block the sync entirely.
Step 3: Map your fields (don’t skip this!)
This is where most integrations go sideways. You’ll need to tell Koncert exactly how Salesforce fields should line up with its own data. If you just go with the defaults, you’ll probably miss important stuff—or end up with half your call notes lost in the void.
Typical fields to map:
- Lead/Contact Name
- Phone Number(s)
- Call Outcome or Disposition
- Call Notes
- Owner/User
How to do it:
- In Koncert, go to the Salesforce integration settings.
- Look for a “Field Mapping” or “Data Mapping” section.
- For each field, pick the matching Salesforce field. If you have custom fields, you may need to add them in Salesforce first so they show up here.
- Double-check that any required fields (in Salesforce) are mapped. Otherwise, you’ll get sync errors later.
Don’t waste time mapping every possible field. Start with the basics. You can always add more mappings later, but cleaning up a bad mapping is a pain.
Step 4: Set sync preferences and test
Now, decide what actually gets synced. Do you want every call logged, or just connects? Should new contacts be created in Salesforce from Koncert, or just update existing ones?
Common options to consider:
- Which Salesforce objects get updated: Just Leads and Contacts, or Accounts too?
- Direction of sync: One-way (Koncert to Salesforce) or two-way? Most teams just need one-way.
- Frequency: Real-time, hourly, daily? Real-time is nice but can cause more API calls (and hit Salesforce limits).
- Activity logging: Do you want every dial attempt, or just completed calls?
Set these in Koncert’s settings. If you’re not sure, start small—sync less at first, then expand.
Test, test, test:
Try a few calls using your test user. Check Salesforce to see if the activity shows up where you expect. If it doesn’t, check:
- Field mapping errors
- API permission issues
- Salesforce validation rules blocking the sync
Don’t assume it works just because you got a “Success” message in Koncert. Go look at the actual records in Salesforce.
Step 5: Roll out to the team (and set expectations)
Once you’ve tested things end-to-end, it’s time to roll out. Here’s what to do:
- Train your team: Show them where to find call logs in Salesforce. If workflows change (like how they log calls), make it clear.
- Document the new process: Even a quick one-pager helps. Include what to do if calls aren’t syncing.
- Monitor for weirdness: For the first week, keep an eye on sync errors, missing data, or duplicate records. Encourage the team to flag anything off.
What not to do:
Don’t try to automate every edge case right away. Get the basics working, then improve. Over-engineering kills momentum.
What works well (and what doesn’t)
What works:
- Basic activity logging is reliable. Most teams are happy just getting calls and notes into Salesforce automatically.
- Time savings add up. Once set up, reps can focus on actual selling, not admin work.
What doesn’t:
- Custom Salesforce workflows and automation can break things. If you have triggers that expect certain data, Koncert might not provide it, causing sync failures.
- Reporting isn’t always perfect. Out-of-the-box reports can be generic; you’ll probably want to tweak or rebuild them.
- API limits. If you’re a heavy user, Salesforce API call limits can sneak up on you, especially with real-time sync.
Ignore the hype:
No integration is truly “seamless.” You’ll need to tweak as you go, and there will be hiccups. But it beats manual updates every time.
Common pitfalls (and how to dodge them)
- Testing in production. Always use a sandbox or dummy records first.
- Assuming defaults are right. Field mapping and sync rules are rarely “set it and forget it.”
- Not involving users. If you don’t show the team what’s changed, they’ll find workarounds that break the process.
- Chasing every possible feature. Start simple, get adoption, then build on it.
Keep it simple and iterate
Integrating Koncert with Salesforce isn’t rocket science, but it’s easy to overcomplicate. Get the basics right, actually watch what happens, and improve over time. Don’t let “perfect” get in the way of “calls are logged and I can find them.” You’ll save yourself (and your team) a ton of headaches—plus, you might even get to spend less time in Salesforce, which is a win in itself.