Rhealo Technologies

Start with the issue. Keep the context.

Whether you need help with access, a slow task or an implementation question, a clear description saves time.

Illustrative photograph for support
Illustrative photograph
In practice

Find the guidance for your request

Use these support guides to collect useful evidence and choose a contact route. Coverage, response targets and access are confirmed against the agreement for your service.

Explore the details

Find the guidance for your request

Whether you need help with access, a slow task or an implementation question, a clear description saves time.

54 pages

Account Management

Account changes need a clear owner.

Best Practices

Support becomes easier when changes and incidents leave a readable record.

Certifications

If a project requires specific training or certification evidence, identify the requirement before scheduling an assessment.

Community Resources

Community advice can help with general usage questions, but it may not match your system version or configuration.

Documentation

Before following a guide, check that it applies to your application version and user role.

Drivers & Tools

A driver or utility must match the device, operating system and approved deployment.

Email Support

A clear support email lets the team start with the right context.

Emergency Support

For a serious interruption, contact your agreed incident owner immediately and describe the impact in plain language.

Escalations

An escalation should explain why the current route is no longer sufficient.

FAQs

Support questions often depend on the system and the agreement behind it.

Feature Guides

A feature guide is most useful when it follows the job you are trying to finish.

Feedback & Suggestions

Useful feedback describes a moment in the workflow rather than only a requested feature.

Forms & Policies

The right support form depends on the change being requested.

Help Articles

When a help article does not resolve a problem, the most useful detail is the first point where your result differs.

How-to Guides

For help with a routine task, describe the starting screen and the result you need.

Implementation Help

Implementation questions often arise where one team's work meets another system.

Incident Reports

An incident report should preserve a timeline people can learn from.

Instructor Led Training

Training support begins with the users' actual tasks.

Known Issues

An issue seen elsewhere may have a different cause in your environment.

Learning Paths

When a team is new to a system, organise learning by role and task.

Live Chat Support

For a quick enquiry, you can start a conversation through Rhealo's WhatsApp contact.

Maintenance Schedule

A maintenance window needs an owner, an affected scope and a way to confirm service afterwards.

Mobile Apps

For a mobile app issue, record the app version, phone model and operating system.

Onboarding Support

A smooth start means people know how to access the system, complete their first task and ask for help.

Online Courses

For online training related to an implementation, first identify the tasks and knowledge gaps.

Performance Reports

A performance report needs a defined workload and measurement window.

Phone Support

A short call can help clarify the impact of an issue quickly.

Planned Upgrades

An upgrade should be reviewed for compatibility before its date is agreed.

Plugins & Extensions

An extension can affect security, performance and the next upgrade.

Product Tutorials

A tutorial should match the task, product edition and permissions you use.

Product Updates

Update information should explain the change users will notice and any action required.

Release Notes

When reviewing a release, check changes to behaviour as well as new features.

Remote Assistance

Remote assistance should begin with your approval and a clear task.

Renewals & Billing

A billing enquiry is easier to resolve when it identifies the agreement and invoice involved.

SDKs & APIs

For an integration question, share the API or SDK version, endpoint and a sanitised example of the request and response.

Security Advisories

Security information needs the affected version, exposure and recommended action.

Service Status

To confirm the status of a service, identify the specific application and affected function.

Skill Assessments

When assessing readiness to use a system, choose the task the person will actually perform.

Software Downloads

Request installation files through the verified source for your product or project.

Status History

A useful status history connects events to a specific service and time window.

Submit a Ticket

To raise a support request, prepare a short description of the issue and its impact.

Success Stories

After resolving a support issue, a short review can prevent the same confusion from returning.

Support Hours

Support coverage is confirmed for the service and agreement involved.

Support Plans

A support plan should describe what happens when help is needed.

System Status

If a system appears unavailable, check which part of the journey fails and whether the issue affects other authorised users.

Templates

A support template is helpful when it captures the details needed for the next action.

Training Calendars

Training dates should allow users to practise before the system becomes part of daily work.

Troubleshooting

Start with the first failing step rather than changing several settings at once.

Update Notifications

An update notice should reach the people who must act on it.

Uptime Dashboard

Uptime needs a stated measurement method: which service, which checks and which time window.

Usage Guides

Usage help should follow your role and the task you need to finish.

Video Tutorials

For a video walkthrough, choose a task that benefits from seeing the sequence on screen.

Webinars

Support webinars can help several users discuss the same workflow or common question.

Workshops

A support workshop is useful when a team needs to untangle a shared process, not only fix one screen.

Let’s talk