Skip to content
Contact us
  • There are no suggestions because the search field is empty.

Log analyzed meetings to Salesforce

Write a summary, risk and next steps from each scored meeting to the Salesforce opportunity it belongs to.

When Meeting Analyzer finishes scoring a meeting that belongs to a Salesforce opportunity, Brevity can log it on that opportunity's activity timeline as a completed Task. Reps and managers see what was said, the main risk and the agreed next steps without leaving Salesforce.

CRM write-back is available to a limited group of customers. To join, ask your Brevity CSM.

What Brevity writes to the opportunity

For each scored meeting, Brevity writes one completed Task on each opportunity the meeting belongs to:

  • Subject: the meeting title.
  • Comments: a Summary of the meeting (up to 1,200 characters), the main risk Meeting Analyzer found, under Risks, and up to five Next Steps, each starting with the name of the person who owns it.
  • Date: the day the meeting took place, not the day Brevity analyzed it.
  • Assigned To: the opportunity's owner.
  • Name: the contact on the opportunity who attended the meeting. If several attended, Brevity names the opportunity's primary contact first. If no attending contact is on the opportunity, the field is left blank.
  • Status: Completed. The Task records a call that already happened; it doesn't add a to-do to anyone's list.

If a meeting is analyzed again, Brevity updates the Task it already wrote instead of adding a second one. If someone deletes the Task in Salesforce, Brevity writes a new one the next time that meeting is analyzed.

Private meetings

A meeting's privacy setting in Brevity decides how much reaches Salesforce:

  • Everyone: Brevity writes the full Task described above.
  • Participants only or Only me: Brevity writes a Task with the subject "Private meeting" and the meeting date, and nothing else. There is no summary, risk, next steps or contact. A manager can see that a call happened on the deal, and when, but not what was said.

If you change a meeting to Participants only or Only me after its Task was written, the next analysis of that meeting removes the content and the contact from the Task.

Once a Task is in Salesforce, your Salesforce sharing rules decide who can read it, not the meeting's privacy setting in Brevity. Within an org that has write-back on, you can't exclude a single Everyone meeting; change its privacy setting instead.

What write-back doesn't do

  • It doesn't edit opportunity, account or contact fields, and it never deletes anything in Salesforce.
  • It doesn't create open Tasks or to-dos.
  • It doesn't log role-play sessions or practice. Only meetings scored by Meeting Analyzer are written.
  • It doesn't include the transcript or a link back to Brevity.
  • It doesn't write to HubSpot.

Before you start

You need:

  • Meeting Analyzer, with meetings recorded or imported into Brevity.
  • A Brevity Org Admin to connect Salesforce and turn on write-back.
  • A Salesforce admin who can create an External Client App and approve access.
  • No HubSpot connection in the same Brevity organization. Brevity supports one CRM connection at a time.

Write-back doesn't need the Brevity package for Salesforce. The package adds the Brevity coaching panel to the opportunity page and installs from a link your CSM provides. Write-back works with or without it.

A meeting is written to an opportunity only when at least one attendee's email address matches a contact listed in that opportunity's Contact Roles. Make sure your reps add the buyers they meet with as contact roles.

Choose the Salesforce user who approves access

Brevity writes Tasks as the Salesforce user who approves write-back. We recommend a dedicated integration user. That user needs:

The user's profile or permission set also needs API Enabled.

Step 1: Create the External Client App in Salesforce

Your Salesforce admin does this step.

  1. In Brevity, an Org Admin opens Connections, finds the Salesforce card and selects Connect. The Connect Salesforce window opens and shows a Callback URL. Select Copy callback URL and send it to your Salesforce admin.
  2. In Salesforce, go to Setup › External Client App Manager and create a new External Client App. Name it Brevity.
  3. Turn on OAuth. Paste Brevity's callback URL into the app's Callback URL field, exactly as shown in Brevity.
  4. Add these OAuth scopes: Full access (full) and Perform requests at any time (refresh_token, offline_access).
  5. Save the app, then copy its Consumer Key and Consumer Secret.
  6. Wait 10 to 15 minutes. A new External Client App takes that long to become active in Salesforce, and connecting before then fails.

Step 2: Connect Salesforce in Brevity

  1. In Brevity, go to Connections and select Connect on the Salesforce card.
  2. In Consumer Key (Client ID) and Consumer Secret (Client Secret), paste the values from the External Client App.
  3. If you're connecting a sandbox, check This is a Salesforce sandbox. Leave it unchecked for your production org. A sandbox's Consumer Key also works against production, so if you connect a sandbox with the box unchecked, Brevity connects and syncs your production org without an error.
  4. Review What Brevity accesses in your Salesforce org, then select Next.
  5. Select Connect. Salesforce opens. Sign in as the Salesforce user you chose and approve access.

When you're back in Brevity, the Salesforce card shows which org Brevity reached, for example "Connected to yourcompany.my.salesforce.com · Production". If it says Sandbox when you meant production, or the other way round, disconnect and connect again with the checkbox set correctly.

Step 3: Turn on CRM write-back

  1. Ask your Brevity CSM to turn on CRM write-back for your organization.
  2. In Brevity, go to Connections. On the Salesforce card, select Enable CRM write-back.
  3. If Brevity asks for them, enter the Consumer Key (Client ID) and Consumer Secret (Client Secret) from the External Client App you connected with, then select Continue to Salesforce. Connections made before write-back was available need this step once.
  4. Salesforce shows a second Allow screen. Your Salesforce admin, signed in as the user chosen above, approves it. This approval lets Brevity write Tasks; it doesn't change what Brevity already reads.
  5. Back in Brevity, the Salesforce card shows CRM write-back enabled.

From then on, each newly scored meeting on a Salesforce opportunity is written to that opportunity.

Turn write-back off

  • Disconnect Salesforce in Brevity. On the Salesforce card, select Disconnect. Brevity deletes its stored Salesforce credential, including the write-back approval, and stops reading and writing. Tasks already written stay in Salesforce.
  • Revoke the write-back approval in Salesforce. Write-back has its own entry under the user's OAuth connected apps, separate from the one Brevity uses to read your data. Revoking only the write-back entry stops write-back and keeps the sync running. Both entries carry the same app name; the write-back entry is the one created when write-back was approved.
  • Remove Create and Edit on Tasks from the approving user. Salesforce then refuses every write, and the sync keeps running.

Troubleshooting

A meeting didn't appear on the opportunity
Check each of these:

  • The meeting was scored by Meeting Analyzer. Meetings that weren't scored aren't written.
  • At least one attendee's email matches a contact in the opportunity's Contact Roles. A transcript you upload by hand has no attendee emails, so Brevity can't match it to an opportunity.
  • The opportunity has an owner.
  • The meeting is in the same Brevity organization as the Salesforce connection.
  • The Salesforce card shows CRM write-back enabled.

The card says "CRM write-back needs re-authorization"
Salesforce no longer accepts Brevity's write-back approval, for example because it was revoked. Select Re-authorize CRM write-back and approve the Allow screen again.

The card says "CRM write-back enabled" but no Tasks are written
The card shows only that an approval is stored. If someone removed the approving user's Create or Edit permission on Tasks, the card still reads CRM write-back enabled while Salesforce refuses each write. Check that user's permissions in Salesforce.

The card stays on "Syncing…" or shows a setup error
The Salesforce user who connected doesn't have a permission Brevity needs. When the card reads "The Salesforce user who authorized doesn't have API Enabled", grant API Enabled to that user's profile or permission set; setup retries on its own. If the card says setup stopped retrying, fix the permission, then disconnect and connect again.

Brevity says "Salesforce is connected, but CRM write-back was not authorized"
The second Allow screen was declined or closed. Select Enable CRM write-back to try again.

Connecting fails right after you created the External Client App
The app isn't active yet. Wait 10 to 15 minutes and connect again.

Frequently asked questions

Who in Salesforce can read a Brevity Task?
Your Salesforce sharing rules decide. A Task on an opportunity is typically visible to anyone who can see that opportunity.

Who is the Task assigned to?
The opportunity's owner, so it appears where the rep already looks. Salesforce records the approving user as the Task's creator.

A meeting involved two opportunities. What happens?
Brevity writes a separate Task on each opportunity.

Does the Task show the call date or the date Brevity analyzed it?
The call date.

Do I need the Brevity package for Salesforce?
No. Write-back needs Meeting Analyzer and a Salesforce connection in the same Brevity organization. The package adds the Brevity coaching panel on the opportunity page.

Can I use write-back with HubSpot?
Not yet. Write-back is available for Salesforce only.