The data model
From the perspective of a B2B company using Fogbender for B2B customer support, each workspace (e.g. Production or Main) has a list of customers, and each customer has a list of users.
Each user has the following attributes:
User avatar URL
User id is mapped to the unique user id in the vendor database.
User id is the same as
User email - in systems where this is the case, it’s not possible for a user to change their email address.
Customer id is the id of the user’s organization in the vendor’s database, and
Customer name is its name.
User name and
User avatar URL are optional, everything else is required.
Ways to import users
1. Automatically via token with embedded support widget
Whenever a vendor uses the Fogbender customer support widget on its customer-facing web dashboard (e.g., https://fogbender.com/admin/-/support), the vendor’s frontend code instantiates the support widget by passing a secure
token to a Fogbender initialization library.
Customers and users instantiated this way are automatically imported by Fogbender. Vendor agents can see all their customers and users in the Customers workspace section:
2. Automatically via Slack (Customer) integration
If end-users access their B2B support environment with a vendor through an integrated Slack channel, Fogbender imports such users by assigning a user’s Slack email address to
3. Automatically via Slack (Agent) integration
Whenever end-users receive multiplayer (B2B, team-to-team) customer support from a vendor via a shared Slack channel connected to Fogbender with the Slack (Agent) integration, Fogbender imports Slack users from the other team as users, assigning user Slack emails to
4. Automatically via Microsoft Teams
The Fogbender Microsoft Teams integration - which works similarly to the Slack (Customer) one - automatically imports users coming from Microsoft Teams, assigning a user’s Microsoft Teams email to
User id in Fogbender. If the vendor is also using the web support widget, as long as a user’s email is the same in Microsoft Teams as it is in the vendor’s internal database - used to instantiate the Fogbender widget - messages originating in Microsoft Teams and in the web widget will be assigned to the same user in Fogbender.
5. Manually via CSV upload
If you’ve got an existing list of users and customer organizations, you can upload your list manually:
The expected CSV format is as follows:
USS Enterprise,uss001,Captain Kirk,firstname.lastname@example.org,k001
Millennium Falcon,mil001,Han Solo,email@example.com,s001
Planet Express,px002,Philip J. Fry,firstname.lastname@example.org,f001
Planet Express,px002,Turanga Leela,email@example.com,f002
Cyberdyne Systems,cs010,Sarah Connor,firstname.lastname@example.org,t001
Cyberdyne Systems,cs010,John Connor,email@example.com,t002
Tyrell Corporation,tyr007,Rick Deckard,firstname.lastname@example.org,d001
6. Manually via 🕵️ Try a live demo!
If you’d like to create a one-off sample user, you can use the 🕵️ Try a live demo! available on https://fogbender.com/admin/-/-/settings/embed:
From there, click the purple “Custom profile” button at the bottom:
Making sure to avoid changing the “Connect to…” section, in the “Connect as…” section, you can specify
Customer ID, and
User id -
In rare instances, you may encounter a customer organization that has users with civilian email addresses. If a user with a civilian email address loses access to a customer organization, Fogbender has no way of detecting such an event, meaning such a user would continue receiving support email notifications - likely an undesirable scenario, which may result in the customer administrator requesting that you remove such a user from your support environment.
To satisfy such a request, you can use the “Delete user” button on the Customers dashboard:
Note that if a deleted user is re-introduced to Fogbender via one of the mechanisms outlined above, the user will become “undeleted”.