OpenClaw Setup & Customization
Provisioning
Section titled “Provisioning”- Navigate to Settings → OpenClaw
- Click Enable OpenClaw
- Heard provisions a dedicated container for your organization
The container runs Heard’s two built-in skills:
heard-brain— The conversational interface (query Heard from any connected channel)heard-proactive-scan— The scheduled scan engine
Connecting a Messaging Channel
Section titled “Connecting a Messaging Channel”The OpenClaw communicates through any channel supported by OpenClaw. Slack is the most common, but WhatsApp, Telegram, and other connectors are available.
Slack (Primary Example)
Section titled “Slack (Primary Example)”- In Settings → OpenClaw → Channels, click Connect Slack
- Authorize Heard in your Slack workspace
- Select the notification channel — where proactive alerts and action plan notifications will be posted (e.g.,
#customer-intelligence) - Click Save
The OpenClaw appears as a bot user in your workspace. Team members can DM it or mention it in channels with @OpenClaw.
Other Channels
Section titled “Other Channels”To connect additional channels:
- In Settings → OpenClaw → Channels, click Add Channel
- Select the channel type (WhatsApp, Telegram, etc.)
- Follow the OAuth flow for that platform
- Configure the notification destination
The OpenClaw works identically across all channels — same queries, same approvals, same proactive alerts. Your team can use whichever channel they prefer.
Proactive Scan Configuration
Section titled “Proactive Scan Configuration”Configure what the OpenClaw checks for and when:
Schedule
Section titled “Schedule”| Setting | Default | Description |
|---|---|---|
| Frequency | Weekdays at 9:00 AM | When the scan runs (cron schedule) |
| Timezone | Your organization’s timezone | So 9:00 AM means 9:00 AM for your team |
| Channel | The channel selected during setup | Where alerts are posted |
What It Scans For
Section titled “What It Scans For”| Check | Description | Default |
|---|---|---|
| Stale Actions | Triage cards with no activity for N days | ✅ On (3 days) |
| Sentiment Drops | Customers whose sentiment declined over recent interactions | ✅ On |
| Time Bomb Warnings | Actions approaching auto-execution | ✅ On |
| Unread Triage | Triage cards not viewed within N hours | ✅ On (48 hours) |
| Weekly Metrics | Team performance summary (sentiment avg, actions completed, response time) | ✅ On (Fridays) |
Customizing Thresholds
Section titled “Customizing Thresholds”- Navigate to Settings → OpenClaw → Scan Rules
- Adjust the defaults:
- “Flag stale actions after 5 days instead of 3”
- “Only alert on sentiment drops of 0.3 or more”
- “Disable weekly metrics”
- Click Save
Conversational Commands
Section titled “Conversational Commands”The OpenClaw responds to natural language. Here are common commands:
| Command | What Happens |
|---|---|
| ”What are the open issues for [customer]?” | Shows the customer’s profile and open issues |
| ”Show me at-risk customers” | Lists customers with risk score > 0.7 |
| ”What happened with [customer] this week?” | Shows recent interactions and analysis |
| ”Run a scan now” | Triggers an immediate proactive scan |
| ”Approve plan #1234” | Approves the specified action plan |
| ”Hold plan #1234” | Pauses a Time Bomb countdown |
| ”Show my team’s stats” | Shows current team metrics |
Custom Instructions
Section titled “Custom Instructions”Standing instructions are persistent rules that shape how the OpenClaw handles requests and scans. They apply alongside your team’s playbook.
Adding Instructions
Section titled “Adding Instructions”- Navigate to Settings → OpenClaw → Custom Instructions
- Click Add Instruction
- Write the instruction in plain language:
“When asked to research a company, always check HubSpot for existing data first, then search the web. Format the result as: Company Overview, Recent News, Key Contacts, Relationship History.”
- Set the scope:
| Scope | When It Applies |
|---|---|
| Always | Every OpenClaw interaction and scan |
| On request | Only when the user asks about a relevant topic |
| Scheduled | Runs on a cron schedule (e.g., “Every Friday at 5pm”) |
- Click Save
Instruction Priority
Section titled “Instruction Priority”When multiple instructions could apply, the OpenClaw follows this order:
- Custom instructions (configured here — most specific)
- Team playbook (configured in Team Setup)
- Default behavior
If a custom instruction conflicts with a team playbook rule, the custom instruction wins.
Custom Skills
Section titled “Custom Skills”Extend your OpenClaw with additional OpenClaw skills from ClawHub.
Installing a Skill
Section titled “Installing a Skill”- Browse available skills at clawhub.io
- Navigate to Settings → OpenClaw → Skills
- Click Install Skill
- Enter the skill ID (e.g.,
web-research,spreadsheet-sync) - If the skill requires credentials (e.g., a Google Sheets API key), enter them
- Click Install
The skill is now available to your OpenClaw. You can test it immediately:
@OpenClaw Use web-research to find recent news about Acme Corp
Managing Skills
Section titled “Managing Skills”In Settings → OpenClaw → Skills, you can:
- View installed skills — see version, last used, and status
- Update skills — apply new versions from ClawHub
- Remove skills — uninstall with one click
- Configure credentials — update API keys or tokens per skill
Security
Section titled “Security”Your OpenClaw runs inside an OpenShell sandbox — an open-source runtime that enforces strict security boundaries:
- Filesystem isolation — skills can only access designated paths; they cannot read other tenants’ data or system files
- Network control — only your Heard API and registered MCP servers are reachable; all other outbound connections are blocked
- Credential protection — API keys and tokens are injected at runtime as secure Providers, never stored on the container’s filesystem
- Each skill only accesses the credentials you explicitly configure
- The OpenClaw’s HITL rules still apply — a custom skill can’t bypass approval requirements