[Back to blog](https://zsoftly.ca/blog) [Announcements](https://zsoftly.ca/blog/category/announcements) # How to Reach ZSoftly by Email ZSoftly now handles customer email in one shared inbox. Use this guide to pick the right address for account, support, security and abuse messages. ZSoftly Team November 2, 2026 2 min read Share ![ZCP branded cover for How to Reach ZSoftly by Email, with the headline on a deep blue grid](https://zsoftly.ca/images/blog/2026/how-to-reach-zsoftly-by-email.webp) Customer email to ZSoftly now goes to one shared inbox. Each address below has one purpose. Pick the one that matches your message. ## Which address to use - [hello@zsoftly.ca](mailto:hello@zsoftly.ca): general questions about ZSoftly or the ZSoftly Cloud Platform. Use this address when you are not sure where a message belongs. - [customers@zsoftly.ca](mailto:customers@zsoftly.ca): account matters, such as credit requests, account closure and questions about an offer. - [support@zsoftly.ca](mailto:support@zsoftly.ca): technical support, such as a problem with an instance, a network, storage or signing in. - [security@zsoftly.ca](mailto:security@zsoftly.ca): a security vulnerability in our website, console or platform. - [abuse@zsoftly.ca](mailto:abuse@zsoftly.ca): spam, scanning, phishing or other abuse coming from a ZSoftly IP address. ## If you have an account When you can sign in, open a support ticket from the [console](https://cloud.zcp.zsoftly.ca/). A ticket links to your account, so the resources involved are already attached. Use email if you are locked out of the console or your question covers more than one account. Include your account email address and the region in any support message. If the problem involves a resource, add its name and the time you first noticed the issue. ## Reporting a security issue We publish our security contact details in the standard `security.txt` file on both [the website](https://zsoftly.ca/.well-known/security.txt) and [the docs site](https://docs.zcp.zsoftly.ca/.well-known/security.txt). Send reports to [security@zsoftly.ca](mailto:security@zsoftly.ca). Include steps to reproduce the issue. Abuse from a ZSoftly IP address is a separate matter. Send it to [abuse@zsoftly.ca](mailto:abuse@zsoftly.ca) with the IP address, the time and any logs you have. ## What changed - We no longer publish `info@zsoftly.ca`. Use `hello@zsoftly.ca` instead. - Every address you write to is on `zsoftly.ca`. If you saved a `zsoftly.com` address for support, replace it with `support@zsoftly.ca`. - Emails from the console and from our status page now list `support@zsoftly.ca`. These addresses are listed on our [contact page](https://zsoftly.ca/contact) and on the [Troubleshooting page](https://docs.zcp.zsoftly.ca/troubleshooting/) in our docs. ## Related articles Announcements November 8, 2026 ### [Object Storage Encryption Is Now Available on ZCP](https://zsoftly.ca/blog/object-storage-encryption-now-available) Opt in to server-side encryption for ZCP object storage in YUL and YOW, with SSE-S3 or ZSoftly-managed SSE-KMS and bucket defaults for new uploads. Announcements November 5, 2026 ### [ZCP CLI and Terraform Provider v1.3.0](https://zsoftly.ca/blog/zcp-cli-terraform-profile-auth) ZCP CLI and Terraform provider v1.3.0 share CLI profiles, make credential selection explicit, and fix inactive subscription listings. Announcements October 20, 2026 ### [Why We Are Building ZCP Certification](https://zsoftly.ca/blog/why-we-are-building-zcp-training-and-certification) ZSoftly is launching ZCP certification in January 2027: four levels, free learning paths and labs, paid exams, and a learning platform built on Moodle with IOMAD.