Loading...
Forceworks · User Guide
RapidClaw
User Guide · For the people who operate RapidClaw
Operate it deliberately.
A practical guide for CRM administrators, supervisors, champions, and approved business users. RapidClaw is deployed safely first, activated intentionally, operated through Command Center, and used in Teams through the orchestrator.
RapidClaw is designed to be —
Four operating principles, in order.
PRINCIPLE 01
Deployed safely first
PRINCIPLE 02
Activated intentionally
PRINCIPLE 03
Operated primarily through RapidClaw Command Center
PRINCIPLE 04
Used in Teams through the RapidClaw orchestrator
01 / 08
How RapidClaw works in practice
The most important thing to understand is that a completed deployment does not mean RapidClaw is fully live.
RapidClaw is provisioned in a non-live posture by default. That means:
- the runtime exists
- the administrative surfaces are available
- Teams can be made available to selected users
- specialist agents, schedules, and live behaviors should be activated deliberately rather than assumed to be on
1.1Normal operating model
- RapidClaw Settings inside RapidStart CRM is where deployment, configuration, and reset actions begin
- RapidClaw Command Center is the primary operating surface for runtime status, approvals, controls, readiness, and supervision
- Teams is the primary end-user interaction surface
- users interact with the RapidClaw orchestrator, not directly with every specialist agent
- OpenClaw Admin is available for advanced runtime work, but normal operation should not require it
1.2Access model
- Teams access is not automatically available to everyone
- the RapidClaw Teams app can be assigned only to approved users through Teams administration policies
- outbound email activity remains approval-gated
1.3Source-of-truth model
- Dataverse is the system of record for deployment state, policy, business context, and control data
- local runtime files and workspace artifacts support execution, but they are not the authoritative operational record
02 / 08
The first hour after deployment
Work this list top to bottom after deployment finishes.
01
Open RapidClaw Settings and confirm the deployment completed cleanly
If deployment ended with errors, resolve those first before making the environment available to users.
02
Open RapidClaw Command Center and check overall runtime health
Command Center is the main place to confirm the environment is reachable and ready for supervised use.
03
Decide who should get Teams access first
Start with a small pilot group. Publish and assign the RapidClaw Teams app only to the people who should interact with it initially.
04
Test the Teams experience with an approved pilot user
Send a simple message to RapidClaw in Teams and confirm:
- the app is visible
- the chat opens normally
- the orchestrator responds
05
Review the current activation posture in Command Center
Confirm which agents, schedules, and live behaviors should remain inactive and which should be turned on for the pilot phase.
06
If outbound email workflows are in scope, confirm the approval path first
Make sure the right reviewers know where the approval queue lives and who is expected to watch it.
07
If you are using a test or safety-routing email, leave it in place during early validation
Do not move to real recipients until you are comfortable with output quality, approval flow, and operational supervision.
The goal is not "everything live." The goal is runtime healthy, admin surfaces reachable, a controlled pilot in Teams, and supervised activation of the behaviors you actually want in production.
03 / 08
Where to do what
Four surfaces. Each one has a clear job.
RapidClaw Settings
CRM Admins
Start deployments, adjust core configuration, reset or redeploy when needed.
RapidClaw Command Center
Admins & Supervisors
Day-to-day operation, approvals, readiness, controls, diagnostics, and runtime supervision.
Microsoft Teams
Approved End Users
Ask RapidClaw for help, summaries, record context, and guided CRM support through the orchestrator.
OpenClaw Admin
Advanced Admins
Advanced runtime inspection, runtime-level management, and future OpenClaw runtime updates.
Simple rule
- Use
Settingsto provision and configure - Use
Command Centerto operate - Use
Teamsto work with RapidClaw - Use
OpenClaw Adminonly when Command Center is not the right level of control
04 / 08
Daily tasks
TASK 4.1
Approve, edit, or reject a drafted action
- Open RapidClaw Command Center.
- Go to the Approvals area.
- Open the draft and review what the agent wants to do, which record or conversation it relates to, and the rationale for the draft.
- Choose Approve if the action is ready, Edit if it needs human correction, or Reject if it should not happen.
Operating habit
Approval decisions are one of the strongest supervision signals RapidClaw gets. If the same draft type keeps being edited or rejected, treat that as a policy or activation issue — not just a wording issue.
TASK 4.2
Ask RapidClaw a question in Teams
- Open Microsoft Teams.
- Open the RapidClaw app.
- Ask the question in plain language.
Examples
"Which open opportunities have gone quiet this month?"
"Summarize the most recent activity for Harbor Logistics."
"What changed on this account since last week?"
Behavior
Users interact with the RapidClaw orchestrator. RapidClaw coordinates with specialist agents behind the scenes — users never need to decide which specialist to call.
TASK 4.3
Activate or pause a capability
Use Command Center when you need to:
- activate an agent for live use
- pause an agent that is too noisy
- review whether a schedule or background behavior should be active
- confirm the current supervised/live posture of the environment
Mindset
Treat activation as an administrative decision, not something assumed to happen automatically after deployment.
TASK 4.4
Move from supervised mode to broader live use
Before broadening the environment beyond a pilot, confirm:
- the right users have Teams access
- approvals are being reviewed consistently
- draft quality is acceptable
- any test-routing or safety-routing email settings are no longer needed
- the agents you want active are active, and the ones you do not want are not
Cadence
Go live intentionally, in stages if needed. RapidClaw is meant to be introduced with supervision, not all at once.
TASK 4.5
Manage who can use RapidClaw in Teams
Use Teams administration controls to decide who receives the RapidClaw app.
- start with a pilot group
- expand only after the orchestrator experience is working well for that group
- keep general tenant-wide exposure off unless that is an explicit decision
TASK 4.6
Review what RapidClaw has been doing
Use Command Center to review:
- recent approvals
- current runtime status
- agent activity
- readiness and diagnostics
- cost or usage trends
Why
This is the best way to understand whether the system is healthy and whether its live behaviors still match your intent.
05 / 08
Weekly & monthly checks
WEEKLY · 5.1
Approvals & supervision quality
- Backlog growing too quickly
- Repeated rejection patterns
- Heavy edit volume from the same type of draft
- Supervisors taking too long on time-sensitive work
WEEKLY · 5.2
Teams access & rollout shape
- Only intended users have access
- The pilot group is still the right size
- The app is not exposed more broadly than intended
- End users understand they interact with the orchestrator, not specialists directly
MONTHLY · 5.3
Runtime health & operational posture
- Overall runtime health
- Readiness indicators
- Cost and usage trends
- Which agents and schedules are active
- Whether the current live posture still matches the business need
MONTHLY · 5.4
Communication safety
- Approval review still happening reliably
- Deliverability is healthy
- Sender-domain decisions still make sense
- Temporary test-routing controls have actually been removed
Repeated rejection patterns and heavy edit volume usually signal that activation, policy, or prompt boundaries need attention.
06 / 08
Troubleshooting
Symptom · 6.1
Command Center shows the runtime is unhealthy
Resolve
Start in RapidClaw Command Center, not by guessing at the runtime.
- whether the environment is reachable at all
- whether the issue is broad or isolated
- whether it affects Teams, approvals, or the runtime more generally
If not clearly recoverable from Command Center, move to Settings for redeploy/reset decisions or escalate.
Symptom · 6.2
Teams works for some users but not others
Resolve
Usually this is an access-assignment issue rather than a runtime issue.
- whether the RapidClaw Teams app has been assigned to the affected users
- whether Teams policy propagation has had time to complete
- whether those users are in the intended pilot or approved-access group
Symptom · 6.3
Drafts appearing, but reviewers unhappy with quality
Resolve
Treat this as an operating signal, not just a content problem.
- whether the right agents are active
- whether too much has been activated too early
- whether test-routing is still in place
- whether rejection reasons are being used consistently
If quality is not good enough, narrow live behaviors before widening them.
Symptom · 6.4
Email-enabled workflows not behaving as expected
Resolve
- whether the relevant workflows are actually active
- whether approvals are being reviewed
- whether temporary safety-routing or test-routing is still enabled
- whether sender-domain choices or deliverability posture need attention
Symptom · 6.5
Something looks wrong after a deployment or update
Resolve
- the OpenClaw version deployed is the current version available at deployment time
- upstream changes can introduce regressions
- future OpenClaw runtime updates should be initiated intentionally from OpenClaw Admin
If the issue appears runtime-specific, use OpenClaw Admin or escalate.
07 / 08
When to use OpenClaw Admin
Most administrators should spend most of their time in RapidClaw Command Center, not OpenClaw Admin.
Use OpenClaw Admin when you need:
- deeper runtime inspection
- advanced runtime management
- lower-level visibility than Command Center currently exposes
- to initiate future OpenClaw runtime updates intentionally
Do not treat OpenClaw Admin as the normal day-to-day operating surface. The primary supervised operating model lives in Command Center.
08 / 08
Support
When escalating a problem, include the following context.
Escalation checklist
- Surface used — RapidClaw Settings · Command Center · Teams · OpenClaw Admin
- Expected behavior — what you expected to happen
- Actual behavior — what actually happened
- Scope — one user, one workflow, or the whole environment
- Mode — pilot / supervised, or broader live use
- Identifiers — deployment ID and any visible error text from the affected surface
Command Center first. Teams through the orchestrator. Activation by deliberate admin choice. OpenClaw Admin only for advanced runtime work.