Preview before write Diffs, policy posture, and rollback readiness appear before the connector executes.
Simulation or sandbox first The product starts with a deterministic story before it asks for production trust.
Proof stays attached Approval, audit, artifacts, and recovery context stay on the same governed run.
Support

Support and contact path

The current support model is direct and founder-led. That is a strength if the product makes it obvious what information to send and what kind of help to expect.

Contact paths

Product help

Use support@actionplane.ai for rollout questions, sandbox guidance, and product issues.

Legal and data questions

Use legal@actionplane.ai for legal, policy, and data-processing questions.

Model
What support looks like today

The support path is direct and founder-led rather than an enterprise SLA desk.

The best support interactions are tied to a specific connector, workflow, and rollout stage.

The team can move quickly when the issue is tied to a visible governed run or reproducible sandbox path.

What to send
How to make support effective

Include the connector, scenario, and whether the issue happened in simulation, vendor trial, or customer sandbox.

Call out whether the problem is onboarding, preview, approval routing, execution, rollback, or evidence visibility.

If there is a run id, include it so the same trail can be inspected across evidence, audit, and review surfaces.

Escalation
When to ask early

Ask early when a first workflow needs architectural review or scope advice before credentials are created.

Ask early when the connector matrix or known limitations leave ambiguity about the right evaluation path.

Use Trust and Limits plus this page as the current expectation-setting surface.