Know who you're actually talking to

A Contact record is supposed to tell you everything about a customer. Today it stops at the edge of your community.

Salesforce 360 creates three custom objects in your org and keeps them current: Bettermode Community Member, Bettermode Community Post, and Bettermode Community Activity. Joins, posts, replies, RSVPs, and event attendance roll up under the Account and Contact they belong to. Every rep opening that record sees the full picture, and every segment you build in Salesforce can use community behavior as a signal.

Your CRM and your community, in agreement

Profile data stays in sync. Map any Bettermode member field to any Salesforce Contact field and pick the direction per field. Updates in Bettermode reach Salesforce within seconds, changes in Salesforce flow back on a regular sync, and empty values are always skipped, so a blank never overwrites good data on either side.

Answers already exist. Put them where people ask.

Federated search brings your Salesforce Knowledge base into the community. A member asks a question and finds the article that answers it, without leaving the thread and without waiting on your team.

Escalate without leaving the post

Some questions do need a human. Staff members get a Create a Salesforce Case option in the (…) menu on every post. Turn on Enable Case Creation, map your Bettermode fields to your Salesforce case fields, and a community question becomes a case with the post's context already attached.

How to turn it on

Go to App store → Apps & Integrations, open Salesforce 360, and click Install. You'll need admin access on both sides and a Consumer Key and Secret from a Salesforce External Client App. Full steps are in the Salesforce 360 setup guide.

What's next

Next we're building revenue influence, so you can see which accounts had members active in the community before a deal closed. Deeper analytics and more mappable objects come after that.

Once you've connected your org, tell us in the replies how the first sync goes. If you need another object or field mapped, ask here. That list is what we build from.

Salesforce 360 connects your Bettermode site to your Salesforce org so community engagement shows up where your revenue and support teams already work. Members, posts, and activity sync into Salesforce as native records that appear on Account and Contact pages, and your staff can open Salesforce cases straight from a community post.

What you can do with it

• See community activity on the customer record. Joins, posts, replies, RSVPs, and event attendance sync to Salesforce and roll up under the Account and Contact they belong to.

• Spot engagement trends. Combine community engagement with the customer data already in Salesforce to find patterns you would otherwise miss.

• Build targeted segments. Use community activity to drive personalized campaigns and engagement workflows for specific customer groups.

• Create cases from posts. Staff members get a Create a Salesforce Case option in the (…) menu on every post, so a support question in the community becomes a case without switching tabs.

Before you start

• Admin access to Salesforce, or an admin who can create an External Client App and assign permission sets for you.

• Admin access to Bettermode.

• The Salesforce 360 app enabled for your site. Check App store → Apps & Integrations.

💡 We highly recommend connecting a Salesforce sandbox first to validate everything before you point the app at your production org. The connect form lets you pick the environment.

Setup path

Work through these in order. Steps 3 and 4 are optional, but most teams want both.

1. Integrate Salesforce with Bettermode Site — create the External Client App in Salesforce, then connect it in Bettermode and choose which spaces sync. Everything else depends on this.

2. Exporting Data from Site to Salesforce — turn on the Enable Site data export toggle and confirm the custom objects exist in your org.

3. Granting Access to Exported Data — assign the Bettermode Salesforce 360 User permission set so your team can actually see the synced records. Skip this and the data is there but invisible to everyone except admins.

4. Create Salesforce Cases from the Bettermode Site — enable case creation and map your fields so staff can raise cases from posts.

What Salesforce 360 creates in your org

Connecting the app provisions three custom objects, a read-only permission set, and a default list view for each object.

Good to know

• Nothing syncs until you choose it. You pick which spaces sync, and no profile fields are mapped by default. Each field mapping is one-directional, so you decide per field whether it flows Bettermode → Salesforce or Salesforce → Bettermode.

• Your consumer secret is stored encrypted and is only used to connect to your Salesforce org.

• Records exist even when a list view looks empty. Salesforce's "Recently Viewed" view is often blank on new objects. Switch to the matching "All Bettermode …" view.

• Surfacing data on Account and Contact pages is a Salesforce-side task. Your admin needs to add the related lists to the page layouts after the permission set is assigned.

All Salesforce 360 articles

1. Integrate Salesforce with Bettermode Site

2. Exporting Data from Site to Salesforce

3. Granting Access to Exported Data: Bettermode Site and Salesforce Integration

4. Create Salesforce Cases from the Bettermode Site

Locale groups: one space per language

Localization is built on locale groups. You enable it on a space, pick that space's language, and it becomes the primary. From there you add a locale variant for each language you want to support, and every variant is its own space with its own content, members, and permissions. The group keeps them connected under one shared URL structure, so a group with the base path docs gives you /en/docs, /de/docs, and so on.

Members land in their own language

To a member, a locale group shows up as a single space in the navigation, not one entry per language. Open the base path and you're sent to the space that matches your language. Internal links keep you in that language as you move around, and you can switch languages any time from the nav bar or your account settings. Spaces without a dedicated locale stay visible to everyone.

Built for regional teams

Because each locale is a real space, your regional teams can run their own. They get their own moderators and permissions, and they can publish content that fits their market instead of forcing one translation on everyone. Post types stay in sync across the group, so the structure stays compatible and your content stays portable between languages.

What it doesn't do yet

Localization doesn't auto-translate your content. You publish what fits each market, so you stay in control of what every region sees. If AI-assisted translation is what you're after, that's on the roadmap (more below). v1 is the routing and structure that make a real multi-language community work in the first place.

How to turn it on

Go to Administration > Settings > Localization to manage your community languages.

Then open any space, find the Locales tab, and select Enable localization. Name the group, set the primary language, and start adding locales. The base path is the shared URL path every locale in the group lives under.

The number of languages you can enable depends on your plan. Full steps are in the localization guide.

What's next

This is v1. We're already building AI-assisted translation with a review step before anything publishes, so you'll be able to scale content across languages without handing over editorial control.

Give it a try and tell us how it goes in the replies. If something's missing for your use case, that's exactly the feedback that shapes what we ship next.

Localization does not translate content automatically. Each locale space is managed separately, so you can publish content that fits specific market.

Key concepts

Locale group — A set of spaces linked together as language variants of each other. Every group has one primary Space and any number of locale variants.

Primary space — The space you enable localization on. It becomes the source for new locale variants and represents the group in your community's navigation.

Locale variant — A space added to the group for a specific language. Each language can have only one space per group.

Base path — The shared URL path for every space in the group. Each Space lives at locale/base-path. For example, with the base path docs, your English Space lives at /en/docs and your German Space at /de/docs.

Before you start

Locale groups use the languages enabled for your community. Go to Administration > Settings > Localization to manage your community languages. The number of languages you can enable depends on your plan.

Enable localization on a Space

1. Open your Administration panel and select the Site > Space.

2. Go to the Locales tab in the space settings top right corner.

3. Click Enable localization

4. Enter a Locale group name. It is pre-filled with the space name.

5. Select the Primary space locale — the language of this space's existing content.

6. Select Enable localization.

This creates a Locale group with your space as the primary. You can now add locale variants.

Add a locale

1. In the space's locales settings, find the locales tab and select “Add locale”. You can also select Add locale under the primary Space in the site tree.

2. Select the language. Languages already used in the group are not available — each group can have one space per language.

3. Optionally, enter a name for the new space. It defaults to the primary space's name.

4. Select Add.

The new space is created as a locale variant of the primary space, ready for content in that language.

Manage a Locale group

The Locales > Configuration > Settings tab of any space in the group shows the group settings:

• Name and description — How the group appears in your admin tools.

• Base path — The shared path for every locale. Changing it updates the URL of all member spaces at once.

How members experience localized Spaces

• One entry in the sidebar. A Locale group appears as a single item in the navigation, so members see one space that is relevant to their selected language, not one per language.

• Language-aware URLs. Each locale space has its own URL, such as /en/docs or /de/docs. Members who open the base path (/docs) are redirected to the space that matches their language.

• Language switching. Members change their language from the navigation bar or via their account settings. The community then serves the locale spaces that match their selection.

• Spaces that don’t have a dedicated locale are shown to all users.

Remove a locale or delete a group

• Remove a locale variant. In the Locales > Configuration > Locales tab, select the remove icon next to the variant. This unlinks the space from the group. The Space and its content are not deleted. The primary Space can't be removed.

• Delete the group. Select Danger zone > Unlink group in the Localization settings. This unlinks all member spaces. The spaces themselves are not deleted.

Support for GraphQL aliasing will be removed on October 15, 2026. After this date, API requests that use aliases may return errors.

What are GraphQL aliases?

GraphQL aliases allow you to assign a custom name to a field within a query. They are commonly used to request the same field multiple times in a single API request.

For example:

query {
  firstPost: post(id: "123") {
    id
    title
  }

  secondPost: post(id: "456") {
    id
    title
  }
}

In this example, the aliases firstPost and secondPost allow two different posts to be returned within a single query.

Who is affected?

This change only affects customers who use GraphQL aliases in:

• Custom applications

• API integrations

• Scripts

• Middleware

• Other custom implementations that connect to the Bettermode GraphQL API

If your API requests do not use GraphQL aliases, no action is required.

What do I need to do?

If your implementation uses GraphQL aliases, you'll need to update those requests before October 15, 2026.

In most cases, this means replacing a single aliased query with separate API requests.

For example, instead of retrieving multiple posts within a single aliased query, you should send one request for each post.

We recommend completing any required changes by October 1, 2026. This gives your team additional time to test your integrations before support is removed.

Why is this change being made?

Removing support for GraphQL aliases is part of our ongoing effort to improve the security and reliability of the Bettermode API.

Need help?

If you have questions about this change or how it affects the Bettermode platform, please contact our Support team.

For implementation guidance and API reference material, we recommend reviewing the related developer documentation below.

Check out Bettermode’s Developer's Guide to learn more about Bettermode’s GraphQL.

Other articles you might be interested in:

• Bettermode's Support Scope

• Get started with GraphQL API Tutorials

• Getting Started with GraphQL Developer's Guide

1. Admin access to Salesforce is required.

2. Admin access to Bettermode is also required.

3. The Salesforce 360 app enabled for your community. Contact the Bettermode team if you don't see it on your App store → Apps & Integrations page.

4. You need to add a callback URL in Salesforce (provided below).

5. Consumer Key & Secret from your Salesforce External Client App.

💡 We highly recommend connecting to a Salesforce sandbox first to validate the integration before connecting your production org. The connect form lets you choose the environment.

Part 1: Create an External Client App in Salesforce

1. Log in to your Salesforce org and click the gear icon in the upper-right corner, then select Setup.
   

   

2. In Setup, search for "Platform Tools" on the left side and click External Client App Manager under Apps, then click New External Client App on the top-right.
   

   

3. Add an app name (e.g., Bettermode Salesforce 360) and press tab so the API name fills automatically.

4. Add your email.

5. Tick the box next to API (Enable OAuth Settings) and insert the Callback URL and scopes.

   Callback URL: https://salesforce360.bettermode.app/salesforce/callback 

6. Add OAuth Scopes:

   1. Manage user data via APIs (api)

   2. Perform requests at any time (refresh_token, offline_access)

      

7. Click Create and wait up to 5 minutes for Salesforce to finish provisioning the app.

8. Open your app in External Client App Manager and click Settings → OAuth Settings → Consumer Key and Secret (you may need to complete 2-factor authentication). Copy the Consumer Key and Consumer Secret. You'll need both in Part 2.

   

Part 2: Connect Salesforce 360 in Bettermode

1. Log in to your Bettermode account, go to Administration view and navigate to the App store section.

2. Go to Apps & Integrations page

3. Click on Salesforce 360 and click Install.

   

4. In the app's settings, fill in the connection form:

• Environment: choose Production or Sandbox (Sandbox uses test.salesforce.com)

• Salesforce Consumer Key (Client ID): from Part 1

• Salesforce Consumer Secret: from Part 1 (stored encrypted and only used to connect to your Salesforce org)

The Connect button stays disabled until both credentials are entered.

Click Connect. You'll be redirected to Salesforce. Log in and complete 2-factor authentication if enabled, then review the requested permissions and click Allow.

💡 When logging in to a sandbox, remember that your sandbox username includes a suffix after your email (e.g., you@company.com.sandboxname).

5. After authorizing, you'll be redirected back to the Salesforce 360 settings page, where you can choose which spaces sync to Salesforce and configure field mappings.

💡 No profile fields are synced until you explicitly map them. Each field mapping is one-directional: you choose per field whether it syncs Bettermode → Salesforce or Salesforce → Bettermode.

The integration between Salesforce 360 and Bettermode is now set up. Salesforce 360 will provision three custom objects in your org (Bettermode Community Members, Bettermode Community Posts, and Bettermode Community Activities), along with a read-only permission set (Bettermode Salesforce 360 User) and default list views.

What syncs to Salesforce

💡 Salesforce's "Recently Viewed" list view can appear empty even when records exist. Switch the list view to "All Bettermode …" to see synced data.

To surface this data on Account and Contact pages and grant access to your team, your Salesforce admin needs to assign the permission set and add the related lists to page layouts.

Related

1. Granting Access to Exported Data: Bettermode Site and Salesforce Integration

2. Create Salesforce Cases from the Bettermode Site

3. Exporting Data from Site to Salesforce