Where the Brain plugs in

A Brain is worth something only where the work already happens. These are the kinds of system it connects to, what it reads from each one, and where it answers back.

The systems a Brain connects to

Show one group at a time

CRM and customer records

What the Brain reads there
The account, the entitlement and the history, so an answer can be about this customer rather than about customers in general.
Where the Brain answers
Into the record the employee is already looking at, without a second window.
  • Salesforce
  • HubSpot
  • Microsoft Dynamics 365 Sales
  • Pipedrive
  • Zoho CRM
  • Close
  • Zendesk Sell
  • Insightly
  • Copper
  • Keap
  • Freshsales

Service desks and ticketing

What the Brain reads there
The ticket, its category, its history, and how the last one like it was closed.
Where the Brain answers
Beside the case, while it is open, in the tool the team already works in.
  • Zendesk
  • ServiceNow
  • Freshdesk
  • Freshworks
  • Intercom
  • Front
  • Help Scout
  • Helpshift
  • Gorgias
  • Gainsight

Contact center, telephony and chat

What the Brain reads there
The queue, the channel, and what this conversation has been about so far.
Where the Brain answers
Into the live conversation, in the channel the customer chose to use.
  • Genesys
  • Amazon Connect
  • Talkdesk
  • Sprinklr
  • WhatsApp
  • LiveChat
  • Crisp Chat

Collaboration and messaging

What the Brain reads there
The threads where a decision got made and was never written down anywhere else.
Where the Brain answers
Where the question was asked, so nobody has to leave the conversation to get an answer.
  • Microsoft Teams
  • Slack
  • Zoom
  • Google Workspace
  • Gmail
  • Microsoft Outlook
  • Google Calendar
  • Calendly
  • Miro
  • Figma

Content, documents and files

What the Brain reads there
The pages, documents, sheets and files that hold what the organization has already written down.
Where the Brain answers
Back into the source, so a document that was wrong is corrected once rather than worked around forever.
  • Microsoft SharePoint
  • OneDrive
  • Google Drive
  • Dropbox
  • Box
  • Confluence
  • Notion
  • OneNote
  • Google Docs
  • Google Sheets
  • Microsoft Excel
  • Coda
  • Quip
  • iManage
  • Stack Overflow for Teams
  • Typeform
  • Adobe Experience Manager
  • WordPress

Identity, HR and people systems

What the Brain reads there
Who an employee is, their role, and what that role is entitled to see.
Where the Brain answers
As a boundary rather than as content: the answer an employee gets is the answer their role is allowed.
  • Okta
  • Workday
  • SAP SuccessFactors
  • BambooHR
  • ADP Workforce Now
  • Gusto
  • Zoho People
  • Greenhouse
  • Lever
  • Workable
  • Vanta

Commerce, billing and finance

What the Brain reads there
The product, the plan, the price and the terms that are actually in force today.
Where the Brain answers
At the counter, in the checkout and in the billing conversation, where the number has to be right.
  • Shopify
  • Adobe Commerce
  • WooCommerce
  • Unleashed
  • NetSuite
  • SAP S/4HANA
  • Oracle Financials Cloud
  • Dynamics 365 Business Central
  • Dynamics 365 Finance
  • QuickBooks
  • Xero
  • Sage Intacct
  • Sage Accounting
  • Stripe
  • Ramp
  • DocuSign
  • Adobe Acrobat Sign
  • PandaDoc
  • Dropbox Sign

Data, analytics and reporting

What the Brain reads there
The measures a team already runs on, so a change is judged against numbers they own rather than ours.
Where the Brain answers
Out as usage and gap signals, so the knowledge itself can be managed as something measurable.
  • Snowflake
  • Databricks
  • BigQuery
  • Amazon S3
  • Looker
  • Tableau
  • Power BI
  • Segment
  • Amplitude
  • Mixpanel
  • Heap
  • PostHog
  • Google Analytics
  • Google Search Console
  • Smartsheet

Developer tools, work tracking and automation

What the Brain reads there
The change, the release note and the incident that explain why the right answer is different this week.
Where the Brain answers
Into the tracker and the automation, where the work that follows actually gets created.
  • Jira
  • Azure DevOps
  • GitHub
  • Linear
  • Asana
  • Trello
  • Monday.com
  • ClickUp
  • Shortcut
  • Productboard
  • Hive
  • Todoist
  • Airtable
  • PagerDuty
  • Zapier

AI runtimes and assistants

What the Brain reads there
Which runtime a deployment is allowed to use, and the boundary it has to stay inside.
Where the Brain answers
As the context an AI agent or assistant is given before it answers, so it has less room to guess.
  • Azure OpenAI
  • OpenAI
  • Microsoft Copilot
  • Anthropic Claude
  • Google Gemini
  • Amazon Web Services
  • Google Cloud
  • Cursor
  • Visual Studio Code
  • Windsurf
  • Kiro

Marketing, campaigns and outbound

What the Brain reads there
What the organization published and promised, so the answer given inside matches the message sent outside.
Where the Brain answers
Back to the people who write it, on the day the promise and the procedure stop agreeing.
  • Marketo
  • Pardot
  • Oracle Eloqua
  • MailChimp
  • Klaviyo
  • ActiveCampaign
  • Emarsys
  • Sailthru
  • Outreach
  • Salesloft
  • Gong
  • Apollo.io
  • Google Ads
  • Google Ad Manager
  • Google Campaign Manager
  • Facebook Ads
  • TikTok Ads
  • LinkedIn
  • Facebook Pages
  • Vimeo

Custom integration is available

The line-of-business application built for your organization, and still running years later, is often exactly where the knowledge that matters lives.

What the conversation covers

  • The system, and what it is for in your organization.
  • What the Brain would need to read from it, and how often that changes.
  • Where an answer would have to appear so that nobody has to leave what they are doing.
  • How the system authenticates employees, because the answer each one gets is the answer their role is allowed.

The platform’s own API

Everything the platform does, it does through an interface a customer can call. The ClearMash Developer Support Brain documents it, and the API Terms of Use say what a client application may and may not do with it.

See a Brain read from a system and answer inside it

A demo shows what crosses the boundary: the record the Brain reads, the answer it gives, and the tool the answer arrives in.

Prefer to start with the numbers? The impact estimator works them out