NivoDesk Pro / Modules
Planned family · illustrativeWorkflow modules, one planned family.
Jobs, appointments, local information, stays, support and lead finding each have different rules. Start by naming the unit of work, then compare the module built around it.
Concept page. No live tool, account or contact intake is offered.
The family
Six planned modules
Each page explains the intended workflow model and the questions to ask. None of them can be activated yet.
Operations
Clarify scope, ownership and the next handoff.
Explore →Bookings
Separate a request from a confirmed appointment.
Explore →Local
Keep public business details tied to a source.
Explore →Hospitality
Plan arrival and overnight-stay journeys.
Explore →Support
Keep questions and human handoffs in context.
Explore →Lead Finder
Find local businesses and review public contacts.
Explore →How to choose
Compare modules in four steps
A quick way to match your work to the right workflow model.
- Step 1
Name the unit
Job, appointment, room-night or question.
- Step 2
Start and finish
What starts it and what makes it complete.
- Step 3
Map handoffs
Who needs which information, and when.
- Step 4
Check permissions
External access needed before connected actions.
01 · Unit of work
Identify the unit of work
Business operations software can cover very different activities. Before comparing modules, name the unit you need to manage: a job request, a timed appointment, a room-night allocation or a customer question.
Then describe what starts it and what makes it complete. This prevents a general task list from being mistaken for a booking system, or a conversation from being mistaken for a confirmed service arrangement.
| Unit | Starts with | Complete when | Module |
|---|---|---|---|
| Job request | An enquiry | Work confirmed done | Operations |
| Appointment | A requested time | Explicitly confirmed | Bookings |
| Room-night | Dates asked | Stay agreed | Hospitality |
| Question | A message | Owner resolves it | Support |
02 · Boundaries
Consider the boundaries between modules
A workflow may cross from an enquiry into scheduling and later into support, but that does not mean every person needs access to every detail.
When evaluating a product, ask how handoffs would retain context, how a mistake could be corrected and which external permissions would be needed before connected actions are enabled.
03 · Availability
Assess the family without assuming availability
The NivoDesk Pro pages describe planned modules for operations, appointments, local visibility, hospitality, support and lead finding. They do not schedule jobs, manage rooms, accept payments or access business accounts.
Use the individual pages to compare the intended workflow models with your current needs.
- Schedule jobs: not available
- Manage rooms: not available
- Accept payments: not available
- Access business accounts: not available
FAQ
Questions you might have
Can I activate a module?
No. All modules are planned; none can be activated.
Which module fits my business?
Name your unit of work first, then read the matching page.
Do modules share data?
The concept is that only relevant information crosses each boundary, with clear handoffs.
Find your unit of work
Then explore the matching module and guides.