Account access
Workspace access requires sign-in. Use your own account, keep credentials private, and do not treat staff scheduling records as separate staff login accounts.
Clear expectations matter. Here is how Hemxi approaches account access, connections, messaging, and the boundaries of the product.
Workspace access requires sign-in. Use your own account, keep credentials private, and do not treat staff scheduling records as separate staff login accounts.
The integration credential store encrypts saved secrets. Business email and WhatsApp connections use credentials from your provider accounts; keep their permissions and expiration under review.
You choose your workflow, sender, channel, and timing. Preview before publishing and verify live delivery. A provider accepting a message is not the same as confirming delivery.
Hemxi organizes appointments, everyday client context, and administrative follow-up. It is not presented as a medical records, clinical consent, or prescribing platform.
A preferred appointment time or stylist can make service feel personal. Sensitive medical records, treatment images, or clinical consent require a separately assessed system and process.
No such certification is claimed here. Assess the requirements of your business, location, and data before relying on a product for regulated workflows.
No. This page explains product scope and practical use. It does not replace a privacy notice, contractual terms, or your own assessment of data requirements.
Disconnecting an integration does not delete your provider account. Workflows using that selected connection need to be reconfigured or reconnected before they can send. Read the integration guide for the supported behavior.
Yes. The public integration guide explains email domain verification, WhatsApp account setup, supported templates, and delivery tracking. The product tour uses sample data and does not send messages.