Create account

Support

Reach the right part of Zelikore.

Tell us which product or account surface you were using, what you expected, and what happened. We will route the request to the system that owns it.

Last updated July 22, 2026

Start with support

Email support@zelikore.com for account access, organization membership, product workspaces, subscriptions, billing, AI tokens, or product behavior.

Include the product, page URL, approximate time and time zone, expected result, actual result, and any safe reproduction steps. Screenshots are useful when they do not expose private customer data. Never email a password, session cookie, access token, private key, or complete payment-card number.

Who owns the first support workflows

Account recovery · Zelikore identityWe verify control of the account, restore a safe sign-in method or explain why access remains restricted, and revoke compromised sessions when needed.
Billing questions · Zelikore billingWe identify the subscription, invoice, cancellation, or payment state and return a corrected state, an invoice link, or a written explanation.
Entitlement mistakes · Zelikore accessWe reconcile subscription, product entitlement, and the product's paid/free state so each product applies its own policy without duplicating commercial state.
AI-token disputes · Zelikore walletWe reconcile the immutable ledger with raw usage and return an adjustment receipt or a line-by-line explanation. Products cannot choose their own debit.
Workspace registration · Zelikore directoryWe confirm that the product-owned workspace exists, register its exact ID, and return the remaining product-side blocker when registration cannot be completed.
Product-link repair · Zelikore platformWe validate both product-owned workspace identities, repair the explicit link record, and confirm the product opens without moving product-domain data.

A question about Zelio business records, a Protheos live session, or an Autokore run is handed to that product's owner with the Zelikore case context; the customer does not need to reconstruct the control-plane history.

Google and email sign-in

Most people should choose Continue with Google. Use the Google account whose verified email belongs to your organization. If you first created an email/password account, a later verified Google sign-in with the same verified address connects to that stable account rather than creating a duplicate.

Email/password remains available as a first-class sign-in method. If sign-in returns an error, copy the visible error text and the page URL into a support message; do not send credentials or browser cookies.

Go to sign in

Product help

ZelioBusiness records, operations, processes, customers, workforce, assets, documents, money, and reporting.
ProtheosLive worker guidance, voice, camera, mobile, browser, device, and realtime session behavior.
AutokoreDurable runs, browser and connector work, waiting, retries, approvals, assignments, and evidence.

For product concepts and workflows, start with the Zelio documentation or name Protheos or Autokore in the support subject so the request reaches the right owner.

Privacy and security

Privacy requests belong at privacy@zelikore.com. Potential vulnerabilities or security concerns belong at engineering@zelikore.com. Do not include secrets or unrelated customer data in an initial report.