Practical guides
Public website pages
Find product information, request a rollout discussion, and move into the client workspace.
Product and workflow information
| Page | How to use it |
|---|---|
| Home | Read the Korenact introduction, then choose the relevant product or workspace link. |
| Healthcare | Review administrative patient-access use cases and the scope to discuss with your facility team. |
| How it works | Read the product-level process; use this documentation for the actual console steps. |
| Workflows | Explore possible roles. Confirm implementation and provider readiness inside your organization’s workspace. |
| Industries and industry detail pages | Review the examples for your industry; they do not activate those roles or integrations. |
| Integrations | Review release-level provider availability. It does not reveal whether your organization is connected. |
| Security | Read the platform’s published controls and discuss deployment-specific requirements with your administrator. |
Pricing, pilots, and contact
| Page | Next step |
|---|---|
| Pricing / Plans | Review available plan information and use the pricing contact flow to discuss service scope. There is no self-service subscription checkout in the current console. |
| Pilot | Describe the facility/workflow scope, provide the required organization and contact details, submit the request, and keep the resulting confirmation. A pilot inquiry does not itself activate service. |
| Contact | Choose the relevant inquiry topic, complete required contact and organization fields, describe your request, submit once, and check for a confirmation or field error. Do not use it as an emergency or clinical channel. |
The public pages do not provide the private client’s organization activity or configuration. Use an existing account to sign in for that information.
Policies and account entry
- Review Terms, Privacy, Cookies, and Acceptable Use for the current published policies.
- Open Sign in for an existing account or Create an account to create a new organization.
- Account and /app links on the public hostname redirect to the application hostname in the standard deployment.
- Follow Accounts & access for field-by-field account instructions and role permissions.