Start with support
Email support@zelikore.com for account access, organization membership, Zelio workspaces, subscriptions, billing, AI credits, or Zelio behavior.
Include the Zelio page URL or Zelikore account surface, 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.
Google and email sign-in
Waiting for a confirmation, password reset, or sign-in email? Check Spam or Junk if it hasn’t arrived within a few minutes. If you find it there, mark it “Not spam” so future account emails reach your inbox. If the link or code has expired, request a new one on the same sign-in screen.
You can 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.
You can also use email and password. 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 inPlan your first Zelio workflow
The public demo is free and uses fictional records. For beta setup, request a meeting with Zelikore to discuss your business needs, current tools, team and locations. Setup help, custom screens and custom workflows are included in your subscription, with no separate setup or custom development fees. Creating an account alone does not grant beta access.
For Zelio concepts and workflows, start with the Zelio documentation and include the page URL and expected result in your support subject.
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.