Support centerFor an outage, include the affected domain, exact error, start time, and last known change.Open request
Product, project, and infrastructure help

Route the problem to the right support path.

Tell us what is affected, what the user sees, when it started, and what changed. Clear evidence helps us distinguish application, hosting, domain, email, configuration, and user-operation issues.

Before opening a request

Capture the facts while the issue is happening.

  • Affected domain, page, account, device, or product area
  • Exact error text and a screenshot when safe
  • Approximate start time and whether the issue is continuous
  • Last code, content, password, DNS, hosting, or settings change
  • Steps another person can follow to reproduce it
  • Whether a recent backup or working version exists

Security rule

Do not send passwords, private keys, database exports, payment details, or personal customer data through an ordinary contact form or public chat.

Urgent outage: State “Production outage” first, provide the affected domain and time, and avoid repeated restarts or uploads that may destroy useful evidence.
Support request

Prepare a useful request in one pass.

The form opens your email client so the request remains associated with your own address. Existing managed clients should include their business or project name.

  • Service hoursMonday-Friday, 8 AM-6 PM, with managed coverage handled by agreement.
  • EmailContact@starlifetech.com
  • Phone / WhatsApp+237 694 713 793

No credentials should be included.

Support boundaries

Coverage depends on ownership, access, and agreement.

Warranty fixes, paid support, third-party failures, hosting incidents, change requests, and new feature work are different categories. We confirm the route before making changes.

Defect assessment

We first verify whether behavior differs from the agreed product or project scope and whether the current version and environment are supported.

Operational support

Configuration, user guidance, deployment, hosting, email, backups, and incident work are handled under the relevant service or care coverage.

Change request

New features, redesigned flows, integrations, increased limits, migrations, and architecture changes are scoped separately to protect stability.