Service terms

Bounded work, written before access.

These terms summarize the standard Mercury Automation service. The checkout page and buyer-specific written scope control the exact plan, price, source, destination, exclusions, timing, and renewal.

Scope and start

Mercury provides only the implementation and managed operations identified in the accepted written scope. Work begins after the required payment, source confirmation, provider-fit confirmation, and minimum access are complete. Unsupported paths can be rejected before implementation.

Offer and payment

Stripe checkout displays the charged items and renewal timing before payment. Taxes, if applicable, are handled according to the checkout configuration and governing requirements.

Managed operations and cancellation

Managed operations can include monitoring, exception review, failed-event repair, provider and routing changes within the accepted boundary, recurring acceptance testing, reporting, and support. Monthly service renews after the included period until canceled. A customer can cancel by emailing marco@mercuryautomation.co before the next renewal. Cancellation stops future managed-service renewals; completed implementation work and already-incurred charges are not automatically reversed.

Acceptance and correction

The accepted implementation is evaluated through the published four-point test: inquiry capture, acknowledgment delivery, staff alert delivery, and timed follow-up plus booking handoff. A pass confirms execution of the agreed technical and operational path under the controlled test. Mercury will correct reproducible in-scope defects during the written support or stabilization period.

Customer responsibilities

No outcome guarantee

Mercury does not guarantee bookings, revenue, ROI, customer behavior, lead volume, third-party uptime, universal compatibility, regulatory compliance for the customer’s business, or uninterrupted operation. The service proves the accepted process execution—not a commercial result outside Mercury’s control.

Data and prohibited scope

The service follows the written data boundary. Protected health information, raw payment-card data, government identifiers, credentials sent by email, illegal use, deceptive messaging, and regulated or highly sensitive data are excluded unless a separate supported written arrangement exists.

Changes and disputes

Additions outside the accepted scope require written approval and can require a new price or timeline. Questions or disputes should first be sent to the founder at the company inbox so the parties can review the written scope, provider evidence, acceptance results, and payment record.

Company contact

Marco Iker, Mercury Automation
16854 Charmel Ln, Pacific Palisades, CA 90272
marco@mercuryautomation.co

Last updated: August 11, 2026.