Enterpret can write its analysis back onto your Salesforce Case records: a summary of the feedback, an overall sentiment, and the taxonomy (themes/topics) Enterpret classified the feedback into. This guide lists exactly what you need to set up on the Salesforce side. Once these steps are done, the Enterpret team finishes the configuration on our end.
There are four things to do:
Create three custom fields on the Case object.
Make sure the Connected App has API write access.
Give the integration user permission to edit those fields.
Re-authorize the Salesforce integration in Enterpret.
1. Create the custom fields
Create these three custom fields on the Case object. Use these exact API names — they are what Enterpret writes to.
Field label (your choice) | API name (must match) | Recommended type |
Enterpret Summary |
| Long Text Area (32,768) |
Enterpret Sentiment |
| Text (255) |
Enterpret Taxonomy Paths |
| Long Text Area (32,768) |
Notes:
Summary can be long (and may combine multiple feedback items), so use a Long Text Area, not a short Text field.
Sentiment is a single value such as
Positive,Negative, orNeutral. We recommend a plain Text field rather than a restricted picklist — a restricted picklist will reject any value that isn't on your list and the write will fail. If you prefer a picklist, tell us and we'll confirm the exact set of values Enterpret emits first.Taxonomy Paths is multi-line text, one path per line, formatted like
Level1 > Level2 > Level3 > Theme > Subtheme. Use a Long Text Area.
If you must use different API names, that's fine — just send us the names you chose and we'll match our configuration to them.
2. Confirm the Connected App has API write access
Enterpret connects to Salesforce through an OAuth Connected App. To write data (not just read it), that app needs the api OAuth scope ("Manage user data via APIs").
Your Salesforce admin should open the Enterpret Connected App → OAuth settings → Selected OAuth Scopes, and confirm
apiis included. Add it if it isn't.This is a small admin change, but it must be done before the re-authorization in step 4, otherwise the new login won't carry write permission.
3. Grant the integration user edit access
The integration user is the Salesforce user whose login authorizes the Enterpret integration. That user needs:
Object permission: Read + Edit on the Case object.
Field-Level Security: Visible and Editable (not read-only) on all three custom fields above.
This is usually done with a dedicated Permission Set assigned to the integration user, rather than changing a profile.
Please also be aware: when Enterpret writes to these fields, Salesforce treats it as a normal record update. That means:
The Case's
LastModifiedBy/LastModifiedDatewill reflect the integration user.Any Apex triggers, Flows, Workflow Rules, or Validation Rules tied to these fields (or to the Case) will fire on our writes.
If you have automations or notifications on the Case object, review them so an Enterpret write doesn't cause unintended emails or rule failures. You may want to exclude the integration user from those automations.
4. Re-authorize the Salesforce integration in Enterpret
Existing access tokens do not automatically gain the new write scope. After steps 1–3 are done, re-run the OAuth authorization for the Salesforce integration inside Enterpret so the new token includes write access. Your Enterpret CSM will coordinate the timing with you.
5. Enterpret finishes the setup
Once the above is done, send your CSM:
Confirmation the three fields exist (and the API names, if you changed them).
Confirmation the integration user has edit access on Case and the fields.
Confirmation the
apiscope is on the Connected App and the integration has been re-authorized.
The Enterpret team then enables the write-back for your account. After that, Enterpret keeps these fields up to date on your Cases automatically as it analyzes the underlying feedback — re-writing them if the analysis changes.