Get unstuck, and stay calm.
Articles, opinionated tours, and live office hours. If you can’t find what you need here, every channel below has a published response time and a real person on the other end.
Other
Getting started
12 articlesYour first 30 minutes with Pulse
An opinionated tour: connect one source, watch the map populate, get your first briefing.
What Pulse is (and what it isn’t)
Mental model: Pulse is a per-tenant memory + governance layer, not another chat box.
Inviting your team
SSO via SAML or OIDC, SCIM provisioning, or one-by-one. The cost trade-offs of each.
Setting your working hours & quiet windows
How Pulse decides when to deliver briefings and when to hold output.
Choosing a model provider
Anthropic vs OpenAI vs self-hosted. When the choice matters and when it doesn’t.
The first map review
Spend 15 minutes correcting the map graph in week one, it pays back forever.
Connectors & data
38 articlesConnecting Slack
OAuth scopes explained; what Pulse does and doesn’t read; per-channel allowlists.
Connecting Salesforce
Standard + custom objects; the per-field consent model; rate-limit guidance.
Connecting Google Workspace
Drive, Calendar, Mail, Meet recordings, what each scope grants Pulse.
Self-hosted MCP bridges
Run a connector in your own VPC. mTLS, deploy modes, when to choose this.
Reading from a private wiki (Notion, Confluence, Coda)
Notion’s permission model is unusual, here’s how Pulse mirrors it faithfully.
Forgetting a source
Disconnect ≠ delete. The 7-day soft-delete and how to make it immediate.
Briefing & map
26 articlesHow the morning briefing is built
The five sections, where each one comes from, and how to tune signal vs noise.
Customising your briefing
Section weights, “always include” entities, “never surface” filters, delivery channel.
Editing the map graph
Merging duplicates, fixing relations, adding aliases. Edits feed back to the calibration loop.
Why is my briefing empty?
Common causes and the diagnostic flow we walk customers through in support.
Skills & agents
22 articlesWhat is a Skill?
A scoped, reviewable agent that does one job: drafts a renewal note, prepares a 1:1, etc.
Writing your first Skill
The Skill manifest, capability requests, the eval harness. End-to-end in 25 minutes.
The capability budget
How Pulse bounds long-running runs so they can’t cost more than you authorised.
Approving an agent run
The review surface, the diff format, the “approve” / “edit” / “reject” workflow.
Governance & admin
31 articlesThe capability model in 5 minutes
Scopes, redactions, retention, lawful-basis tags. The least-privilege concept Pulse runs on.
Writing a policy
The DSL, the linter, deploying via CI, common gotchas.
Streaming the audit log to your SIEM
Splunk, Datadog, Elastic, S3. The hash-chain verifier and how to use it.
Granting break-glass access
Time-limited support access with customer approval, fully audited.
API & MCP
19 articlesChoosing between API, SDK, and MCP
Three doors into Pulse. When each is the right one.
Authenticating with capability tokens
Service accounts, scoped tokens, rotation. Why we don’t use long-lived API keys.
Using Pulse from Claude Code or ChatGPT MCP
Connect either client; what tools your agent gets; how to scope them safely.
Troubleshooting
36 articlesPulse says “calibrating” for too long
The expected timeline for a 50-person team and what to check if you’re past it.
The map has a duplicate of a customer
Merging entities, the alias system, and how to teach Pulse the disambiguation rule.
Connector keeps disconnecting
OAuth re-consent loops, expired refresh tokens, and the IT escalation path.
Audit log entries look wrong
Reading the hash chain, validating the signature, what to do if verification fails.
Still stuck?
If the article you needed wasn’t here, here’s exactly who to ask. Each route is staffed by humans with published response times.
Open chat from any Pulse page.
It carries your auth and tenant context, so you don’t have to describe your environment. Backed by humans, not a model.
P1 · 1h · P2 · 4h · P3 · 1bdsupport@pulsehq.tech
For when chat isn’t convenient. Same triage. Reply lands in your inbox; thread continues there.
median first-reply · 47mLive calls · weekly
Tuesdays 17:00 UTC and Thursdays 09:00 PT. Bring a question, leave with an answer, or schedule a deeper session.
register →