Public product portal
Electri City Site Optimizer
Support and contact

Support can be public. Protected operator authority cannot.

This page is the public entry for support, commercial inquiry preparation and technical scope clarification around the portal, the plugin path, licensing boundaries and documentation. It does not expose protected operator or customer actions.

Support entry is public and informationalOperator and customer execution surfaces remain protectedCommercial and contact details stay explicit when not yet confirmedRequest preparation is allowed; protected fulfillment is not
Prepare access context Start with the docs
Reference Modeobserve_only
Portal Gateapproval_required
Homepage Status200
Response Time236.9 ms
HTML Size183,759 bytes
Sitemap Status200
Readiness summary

Portal-visible readiness without protected execution

Support readinessoperator input required

Contact: operator input required; Email: operator input required.

Commercial readinessoperator input required

Commercial inquiry path: operator input required; Pricing: operator input required; Packages: source not yet confirmed.

Access readinessapproval_required

Portal copy is request-ready, but live request handling remains protected.

Download readinessapproval_required

Portal gate: approval_required; no open download or private route exposure.

Support lanes

Support, commercial inquiry and technical scope clarification stay separate

The support surface is now clearer about the kinds of requests it is preparing for: documentation guidance, technical scope clarification and later commercial inquiry preparation.

What it still does not do is expose a live support desk, login flow, private download service or operator-side control action.

  • Technical scope clarification: public and informational
  • Commercial inquiry preparation: public but placeholder-only
  • Protected execution or fulfillment: approval_required
  • Public contact page: pierre.stephan1@electri-c-ity-studios.com
Current contact state

Operator-contact placeholders remain explicit

Primary support contact is currently documented as operator input required. The portal keeps that honest instead of inventing contact details that are not yet confirmed.

Current support contact field: operator input required.

  • Support email: operator input required
  • Commercial inquiry path: operator input required
  • Public issue intake flow: source not yet confirmed
Request readiness

What support needs from you

Support is most useful when it helps clarify domain scope, source ownership, plugin coexistence, commercial fit and validation expectations before any later change request.

  • Which WordPress domain is in scope
  • Which theme, builder and SEO plugin are active
  • Which business or operational goal is driving the request
  • Which rollback owner and validation owner are assigned
Check license and scope boundariesReview access-request readinessOpen public contact details
What is not publicly available

This page remains informational and does not open protected functions

This support entry does not act as a login page, a license issuance page, a private download endpoint or a customer execution dashboard. Those paths remain protected and approval-gated.

  • No login flow
  • No customer dashboard
  • No live operator action path
Support readiness

Support visibility can improve through config without changing the protection model

The support surface now reads operator-configured visibility fields. That allows cleaner public support guidance later, while protected delivery, activation and customer actions remain out of scope.

  • Support readiness: operator input required
  • Commercial readiness: operator input required
  • Access readiness: approval_required
FAQ

Frequently asked questions

Can I request immediate live changes through this support page?

No. Support can guide scope and documentation, but real changes remain approval-gated and protected.

Why does the page still show operator input required?

Because unconfirmed contact or commercial details are intentionally not invented or implied.

Can support activate a license or send a private package from this page?

No. This page prepares inquiry and scope clarification only. Any real activation or fulfillment remains protected and approval_required.

Next step

Use support to qualify fit before any protected workflow exists

Clarify domain scope, plugin ownership, commercial readiness and rollback responsibility first. Protected execution stays separate.

Check licensing boundariesReview the plugin pilot path