Support Chat: Intercom and Zendesk
Two integrations put a help or chat window on Full Fabric pages. Intercom shows an Intercom messenger from your own Intercom workspace: one messenger for staff and one for applicants and students, each switched on and configured separately. Zendesk shows the Full Fabric help widget, where people search Full Fabric help articles and contact Full Fabric support; it always uses Full Fabric's own help centre, so there is nothing to connect.
Both live in Settings → Other integrations, under the Communication heading.
Intercom
Connect
Open Settings → Other integrations → Intercom. The page has two cards:
| Card | Shown to |
|---|---|
| Staff messenger | Staff, across the app |
| Applicant and student messenger | Applicants and students, in their portal |
For each messenger you want:
- Click Add credentials (or Update credentials).
- Enter the App ID of your Intercom workspace and its Secret key. The secret key is the identity verification secret: Full Fabric uses it to sign each signed-in user's ID, so Intercom can trust who they are.
- Click Save credentials.
- Click Enable in the card header. Disable asks for confirmation first.
The secret key is masked once saved. When updating, leave Secret key empty to keep the saved value.
Note: Save both the App ID and the Secret key before enabling a messenger. The staff messenger does not appear without both, and the portal pages expect both as well.
Who Sees Each Messenger
| Messenger | Appears for | Does not appear for |
|---|---|---|
| Staff messenger | Signed-in users with a staff role, on staff pages | Users who hold the staff support role (staff::support); users without a staff role |
| Applicant and student messenger | People on portal pages, signed in or not | Staff pages |
Visitors who are not signed in get an anonymous messenger: only your App ID is sent. Neither messenger checks cookie choices.
What Full Fabric Sends to Intercom
When a signed-in person opens a page with a messenger, Full Fabric passes their details to Intercom so conversations are linked to the right person.
| Data | Staff messenger | Applicant and student messenger |
|---|---|---|
| User ID, and a hash of it signed with your Secret key | Yes | Yes |
| Full name and email | Yes | Yes |
| Date the account was created | Yes | Yes |
| Institution name and handle | Yes | No |
| Company: institution ID, name, creation date, edition and Full Fabric web address | Yes | No |
New Institutions
Institutions created on production start with the Staff messenger active, using Full Fabric's own Intercom app. Replacing its credentials moves the staff messenger to your Intercom workspace; disabling it removes the messenger for all staff.
Zendesk
Open Settings → Other integrations → Zendesk. The page has the Enable / Disable action and a Web widget card describing the widget. There are no fields: the widget is always connected to Full Fabric's help centre.
When Zendesk is enabled:
- The help widget is loaded on Full Fabric pages but starts hidden, so nothing changes on screen at first.
- It opens from a help button (question-mark icon) that appears in the top bar of the older staff page layout while Zendesk is enabled.
Disabling removes the widget from every page.
Help Centre Sign-In
People can sign in to the Full Fabric help centre with their Full Fabric account. Full Fabric passes their name and email to Zendesk to sign them in. This sign-in works whether or not the widget is enabled. If the browser has not been used to sign in to Full Fabric before, there is no institution to send the person to, and they see a not-found page instead.
Common Problems
| What you see | Usual cause | Fix |
|---|---|---|
| The staff messenger does not appear | The card is not enabled, or its App ID or Secret key is missing | Save both credentials, then Enable |
| One staff member sees no messenger while others do | They hold the staff support role, or have no staff role | Expected: the staff messenger skips those users |
| The applicant and student messenger does not appear in the portal | The card is not enabled, or its credentials are incomplete | Save both credentials, then Enable |
| Zendesk is Active but no widget is visible | The widget starts hidden | Open it from the help button where it is shown |
| The changes could not be saved. or another error in the card | The save was refused, for example because your role cannot change institution settings | See Permissions below |
Permissions
Opening these pages needs Global integrations (core.institutions.global_integration_settings). Saving goes through the institution settings, so the role also needs permission to change institution settings; without it the page opens but changes are refused. See Permissions.