1. Choose the workspace shape
We confirm your plan, domain, number of users, data location expectations, backup mode, and which starter workflows matter first.
Support and onboarding
A managed workspace should come with a human path.
ReefOffice is for non-technical teams that want a private office without becoming operators. Support is part of the product: setup, updates, recipe packaging, restore help, and plain-language guidance.
2. Provision and verify
ReefOffice creates the private workspace, checks login, TLS, backups, monitoring, and the core services before you invite the team.
3. Install useful starter recipes
The first automations are selected by business value: client folders, document archive, reminders, digests, lead capture, or AI document summaries depending on the plan.
4. Hand over plainly
You receive the URLs, admin expectations, a short service tour, and the support path. Technical details stay available, but they do not become your day job.
Included help
- Account and login access questions.
- Core service availability checks.
- Managed updates and routine security maintenance.
- Backup status checks and planned restore help.
- Installing or refreshing included automation recipes.
- Explaining the stack to your client, accountant, or technical advisor.
Scoped separately
- Large data migrations from existing SaaS tools.
- Custom vertical workflow packs.
- Sector-specific legal compliance reviews.
- Complex app customization inside upstream tools.
- Emergency work outside normal support coverage.
- Air-gapped handoff or on-premise operating procedures.
By plan
Support follows the value of the plan
Plans are not just server sizes. They define how much onboarding, workflow packaging, and AI enablement should be expected.
Private Office Solo
Clean setup for one owner-operator.
Email support, starter recipe selection, and a short workspace handover.
Private Office Team
Best first plan for small client-service teams.
Team onboarding guidance, included starter automations, and one light workflow adjustment during onboarding.
Private AI plans
Document-aware AI and scheduled summaries.
AI workflow onboarding, document-memory checks, and realistic guidance about privacy, capacity, and when to use external model keys.
Dedicated or on-premise
Higher-isolation or hardware-specific requirements.
Sales-led scope, migration plan, security review questions, and a written operating boundary before deployment.
Response model
Clear priorities, no false 24/7 theatre
Standard support targets a first response within one business day. Service-impacting incidents and security issues are handled first. Full 24/7, regulated, or guaranteed-response support should be priced and documented separately.
Already a client? Open a support ticket directly from your dashboard — it attaches your server context automatically.
Open a ticketGeneral support
Use this for access, onboarding, billing, workflow, restore, or general service questions.
Send email
Security disclosure
Use this for vulnerability reports, suspicious access, or security-sensitive questions.
Send email
Demo and onboarding
Use this when you want to understand which plan and recipe pack fits your team.
Send email
Want to know what support would cover for your team?
Share your team size, current tools, and the first workflow you want to automate. ReefOffice can turn that into a practical onboarding scope.