Platform / Tools

Every surface of support, one system.

The channels your customers already use, a help center that answers for itself, a widget in your product, and Clad working inside the helpdesk you already run.

/ The toolkit

Integrations

Slack, Discord, Teams, Telegram, and email become native ticket channels. Linear and GitHub keep engineering in sync. Stripe, HubSpot, and PostHog feed revenue and usage context into every thread.

Integrations

12 connected
SlackTickets from shared channelsConnected
DiscordCommunity server triageConnected
EmailShared inbox, every thread trackedConnected
LinearEscalations with two-way syncConnected
GitHubRepo context for investigationsConnected
StripePlan and billing on every accountConnected
PostHogProduct usage signalsConnect
IntegrationsClad toolkit

Help center

A branded, publicly hosted knowledge base on your own domain. Keyword search, AI answers grounded in your articles, and a one-click path to a human when the answer isn't there.

help.yourdomain.com

How can we help?

How do I rotate an API key?Ask AI

Getting started

12 articles

API & keys

8 articles

Billing

6 articles

Popular articles

Rotating and scoping API keys
Connect your Slack workspace
Set up SLAs and support hours
Help centerClad toolkit

Chat widget

An embeddable chat SDK for your app or site. Conversations arrive as native tickets, AI answers draw on your published articles, and agents reply from their inbox or straight from Slack.

MKAI

Support

Typically replies in minutes

Can I move our billing date?

Yes, under Settings → Billing you can pick any day of the month. Changes prorate automatically.

AI · from “Plans and seats”

Perfect, and does that change our invoice?

Write a reply…
Chat widgetClad toolkit

Inside your helpdesk

Keep Pylon or Zendesk as your system of record. Clad mirrors each ticket, investigates it against your repo, logs, and billing, and shows the findings in a panel right inside the ticket. Approved replies go back through your helpdesk as a named Clad teammate — or run it read-only until you trust it.

c.l.CladAssist
CodeBillingFile ticket

Findings ready

Export pagination introduced in 2.14.0 caps pages at 5,000 rows; the CSV writer only consumes the first page.

exports/csv.tsL112
PR #2481merged Fri
Full response
Insert reply
Open in Clad
Inside your helpdeskClad toolkit

And underneath

The platform doing the work.

CapabilityAI reply draftsEvery ticket gets a draft grounded in your knowledge base and past resolutions, checked by a validator before an agent sees it.
CapabilityIssue investigationA coding agent reads the ticket, then your repo, logs, and billing to trace the real root cause — with the files and PRs that matter.
CapabilityKB generationPoint Clad at a repo, a Slack channel, or your site and it drafts articles in your voice. Review, publish, keep fresh.
CapabilitySLAs & support hoursResponse and resolution targets per plan or account, measured against your hours. Breaches are flagged before they happen.
CapabilityCustomer healthA daily read across tickets, sentiment, usage, and billing per account. Churn risk surfaces with the evidence behind the score.
CapabilityProduct insightsTickets clustered into the themes actually driving volume — bugs, confusion, requests — so product knows what to fix next.
CapabilityMeetings & notetakersCalendar sync attaches customer calls to their account. A notetaker joins, and the summary lands beside the related tickets.
CapabilityProactive outreachScheduled follow-ups, health-triggered check-ins, and post-incident broadcasts — sent from the same inbox, tracked like any thread.
CapabilityAccounts & contactsEvery contact and company with plan, spend, and ticket history in one view. Two-way HubSpot sync keeps sales and support aligned.
Capability · For buildersAPI & MCPA GraphQL API for issues, accounts, and knowledge with scoped keys and webhooks — plus a hosted MCP server so your own AI agents can open investigations, approve drafts, and file tickets from wherever they already run.

query {

issues(status: OPEN) {

id title severity

account { name plan }

}

}

See the whole system on your stack.