Your CRM knows the customer better than any other system you own, and it is one of the slowest to answer a question. The detail that decides a renewal is rarely in a field — it is in an activity note, a closed-lost reason, an email logged eighteen months ago by someone who has since left. The Salesforce connector is part of askFinz Knowledge, which is still rolling out; here is what it will do, and what it will not.
Ask an account for its own history
"What happened the last time we renewed this account?" gets answered from the opportunity, the activities and the notes attached to it — with each record named, so you can open it in Salesforce and check.
Find the reasoning in notes and closed-lost reasons
Free-text is where the honesty lives. Those fields are matched by meaning, so a search for "lost on procurement delays" can surface a note that never used those words.
Prepare for a call without a report request
Stage, owner and amount stay structured, so "open renewals over 50k in EMEA" narrows properly rather than being matched as words.
What leaves the record, and what does not
What crosses, and what stays in Salesforce
Read
the standard and custom objects you select, and the fields you leave enabled.
Written back
nonenothing. No records, tasks or activities are created or edited.
Stored
a searchable copy of the selected fields, plus a link back to the record.
Never read
objects you did not select, and fields excluded by your field-level security.
What you will be granting
Read-only access through a connected user, so askFinz can see exactly the objects and fields that user can already see — sharing rules and field-level security included.
Setting it up
Planned — not available yetWhat connecting it will look like once the connector arrives.
- 01
Authorise Salesforce from Knowledge with a read-only integration user.
- 02
Choose the objects to include — accounts, opportunities, contacts, activities, custom objects.
- 03
Exclude any fields you would not want quoted in an answer.
- 04
Set the refresh interval.
Limits, honestly
- One-way and read-only. Salesforce remains the system of record.
- Answers reflect the last refresh, not the live record.
- Attachments and files stored in Salesforce are out of scope for now.
- Very large orgs may want to start with a few objects rather than the whole schema.