M
Maya lane
Local behavior: front-desk intake and draft follow-up.
Manual fallback: support review and owner approval. Future-approved connector: website intake only, if approved later.
Integrations boundary
Keep connectors narrow, owner-approved, and future-only.
This page replaces broad marketplace framing with a launch-safe integrations boundary. It maps Maya, Miles, and Nora to local behavior first, manual fallback second, and future owner-approved connectors only.
M
Miles lane
Local behavior: lead summaries and draft follow-up.
Manual fallback: support review and owner approval. Future-approved connector: CRM handoff only, if approved later.
N
Nora lane
Local behavior: support triage and escalation notes.
Manual fallback: support review and owner approval. Future-approved connector: support inbox only, if approved later.
What stays out of scope
- No live OAuth.
- No live connector calls.
- No customer-data sync claims.
- No marketplace expansion claims.
- Customer-fit gating and the action-tier ladder stay guided until owner approval expands the boundary.
Safety labels stay visible
- Tenant and workspace scope remain visible on the local routes.
- Secret references stay local; public pages do not expose secrets.
- Audit logs stay reviewable with a kill-switch posture, not live control-plane claims.
- Owner approval is required before any future connector path is considered.