Where to look, and who to ask
Most questions are answered in the documentation. When it is not, or when something is broken, this page says how to reach a person and what to include.
Documentation
A walkthrough of the admin workspace, setup order, billing, accounting, journal entries, and year-end close. It is written for whoever ends up running the books, not for a developer.
Support
Support is by email, and every message reaches a person. There is no phone line and no chat window yet; both would be dishonest to advertise while the team is this small.
When you write in, these make the difference between one reply and three:
- The community account number, like C-100168, and the unit if it concerns one
- What you expected to happen, and what happened instead
- Whether it is repeatable, and roughly when it started
- A screenshot if the problem is visual
Write to support@ourridge.com. If the matter is urgent and affects the books — a payment posted twice, a year closed by mistake — say so in the subject line.
Service status
There is no public status page yet, which means an outage is reported by whoever notices it first. That is a gap, and it is on the list.
What is true today: the platform runs as separate services, so a fault in the operations console does not take down the resident portal or the books. If a page fails to load, reloading or waiting a minute is worth trying before writing in.
Account recovery
If you have lost access to the account holder address, or the person who held it has left the board, use the recovery request form. It is reviewed by a person, not answered automatically, because recovery is exactly the path an attacker would take.
Contact
For anything else — a question about pricing, a complaint about how something was handled, or feedback on the product — the contact form reaches the same inbox as support.