Build event-driven steps, review dependencies and simulation results, and inspect runs and delivery failures. Improvement proposals require review before applying a new version.
Simulation shows configured behaviour; it does not prove a provider will complete a live action.
Track deliverables, review requests, exceptions, dated hours and retainer periods. Compare assignment and deadline scenarios before changing the project.
Scenario results are estimates based on the recorded inputs, not guaranteed profit or capacity.
Give assistants approved company and project context. Review sources, refresh status and access rather than copying customer information into every prompt.
Answers depend on source quality and the permissions of the person asking.
Review the proposed action, scope and cost. Follow the request, plan, approval, tool call and recorded effect; supported MCP tools use the same access rules.
Some actions remain human-only. MCP coverage is documented per tool, not promised for every screen.
Use customer journeys, campaign attribution and recorded outcomes. Search and AI visibility distinguish appearances, citations, referrals and conversions.
Google Analytics needs authorised setup; search imports and manual experiments are not live ranking or citation guarantees.
Use availability, meeting pages and the coaching kits. Link an existing payment request to the appointment and keep the customer record in context.
Google Calendar and payment providers need authorisation. Linking a request does not charge the customer or make payment a booking condition.
Email uses the monthly plan allowance. Israeli SMS uses verified prepaid packages; international SMS and calling use the wallet. SMS counts parts, not just recipients.
An own-provider account is separate. Provider charges and connection requirements still apply.
Connect supported providers, the WordPress lead plugin, Zapier or Make adapters, and signed webhooks. Inspect connection health and failed webhook deliveries.
Installation and authorisation are required. Marketplace publication is not claimed.
Export supported fields, pipelines, modules, lists, segments, templates, forms and automation definitions. Preview import compatibility before writing.
Structural export is not a full backup or a promise that every external platform can import it.
Connect campaigns, creator codes, orders, refunds and gifting with supported store data. Keep client review, project deliverables and retainer work in the same operating context.
Store connections and client-portal access require setup and the relevant entitlement. Attribution is based on recorded data, not guaranteed sales.
Run the supported business-task evaluations and review saved results, failures and model cost. Inspect media review and cleaning status before using uploaded content.
An internal evaluation is not an independent security audit. Media cleaning and external providers depend on the configured runtime.