Support
Last updated: July 10, 2026. Boring AI is operated by Tilton Group LLC. This page is the official support and customer-service contact page for Boring AI. It explains what support covers, how billing questions are handled, how custom service work is fulfilled, and what information should not be sent over normal email.
Boring AI handles questions about paid growth-system builds, preview status, Stripe receipts, implementation scope, cancellation or refund review, access handoff, and support for pages or automations we have delivered. If the question is about a preview or checkout, include the business name, checkout email, and the URL you are asking about.
Payments are processed by Stripe in USD. Boring AI does not store full card numbers. Use support for receipts, payment-link questions, invoice confusion, cancellation requests, refund review, or if the wrong email was used at checkout. We may ask for the checkout email, business name, transaction date, and the service package purchased.
Paid work begins after payment, scope confirmation, and safe access handoff where access is actually needed. Normal implementation support covers asset requests, copy changes, approved access questions, page readbacks, launch questions, and reasonable fixes tied to the accepted scope.
Do not send passwords, full payment card data, private customer lists, medical details, legal files, bank logins, identity documents, or regulated data through normal email. If a project requires sensitive access, we will confirm a safer handoff path and only request the narrow access needed.
Support is handled with paid-customer and billing/access issues first. Normal support target is one business day. If a live page we delivered is broken, include the URL, screenshot if available, browser/device, and what you expected to happen.
Boring AI builds custom service work. If a requested change is outside the paid scope, we will say so before implementation and quote or schedule the next step rather than quietly expanding the project and surprising you later.
Boring AI is operated by Tilton Group LLC. Email [email protected] or use the plain review-safe address shown here: support@tryboringai.com. Support URL: https://tryboringai.com/support/. Principal and mailing address: 2108 N St, Ste N, Sacramento, CA 95816. Stripe, bank, and platform login actions that require your identity remain yours unless a safe delegated access path is explicitly approved.
Plain-text support address for account review: support@tryboringai.com.
Every support request is triaged by outcome: billing/access first, broken delivered pages second, scope questions third, general questions after that. We look for the actual URL, checkout email, expected behavior, and the business outcome being blocked. If the fix is inside the original paid scope, we handle it as support. If the request is a new campaign, new funnel, extra automation, new platform, or new offer, we will label it as a scope change and quote the next step before work begins.
For Stripe account review, this page is the public customer-service location. It lists the service sold, support channel, billing path, cancellation/refund route, fulfillment boundaries, and privacy/terms links so a reviewer or customer does not need to guess what happens after checkout.
Billing, refund, and cancellation requests should be emailed to [email protected] with the checkout email, business name, product purchased, and reason for the request. General implementation support remains at [email protected]. Support is monitored during normal U.S. business days; the target first response is one business day. Custom work, delivered files, and started implementation time are reviewed under the Terms of Service rather than automatically reversed.
Support-account review addendum: Boring AI support is the public path for customer-service questions, disputed charges, cancellation review, refund review, delivery questions, privacy requests, and implementation blockers tied to paid work.
Support is email-first. We do not offer live phone or chat support unless a paid scope separately includes a scheduled call. Each request should include the checkout email, business name, URL or deliverable involved, screenshots if helpful, and the requested outcome. Support replies will create or reference an email thread that acts as the case record. If an issue blocks paid delivery or payment access, mark the subject line “billing/access blocker” so it can be triaged ahead of general questions.
Cancellation or refund review requests must be emailed before chargeback/dispute escalation when practical. We review whether work has started, whether custom assets were delivered, whether the blocker is caused by missing customer inputs or third-party platform decisions, and whether an unused portion remains. If a refund is approved, it is normally returned to the original payment method through Stripe. We target an initial decision within five business days after receiving enough information.
Typical service flow: checkout, scope confirmation, asset/access request, build, customer review, included fixes, and final delivery. A project counts as started once strategy, production, implementation, or custom analysis begins. A deliverable counts as delivered when files, live URLs, implementation notes, or review-ready assets are sent to the customer or posted to the agreed workspace.