Example workflows in Nexora
These short examples connect everyday business actions to Nexora's current rules. Open a rule link for the full explanation and limits.
From an action to its result
The examples use no made-up price, schedule, or team size. The business still chooses the real people, times, amounts, and access levels.
Finish an appointment and record payment
An appointment outcome and a payment record describe two related parts of the business's work.
What happens
- The business creates an appointment and it remains Waiting until its outcome is applied.
- After the saved duration ends, routine processing can mark it Completed; the business records money as received only after checking its own payment method.
Result: The work outcome and the confirmed payment record are kept without Nexora claiming to move the money.
Count a package use
A future package appointment does not use a package right just because it exists.
What happens
- The business links the appointment to the customer's package.
- Completed and Paid cancellation count as a use; Waiting and Cancelled do not.
Result: The package balance follows the appointment outcome.
Choose how to cancel after payment
A paid service appointment requires an explicit cancellation choice.
What happens
- The business confirms that some payment was received for a service appointment.
- When cancelling, it chooses Paid cancellation (keep payment) or Cancel and refund.
Result: Paid cancellation keeps the recorded payment. Cancel and refund records a full refund and leaves nothing due. The business moves the real money; Nexora does not send it.
Reach the end of a repeating package period
A repeating package can prepare its next period when its balance reaches zero and the business has suitable access.
What happens
- The counted sessions reduce the current period's balance to zero.
- Nexora checks access before opening the next weekly or monthly period.
Result: With suitable access the next period can open; otherwise renewal may wait.
Add and later remove a group member
Group membership changes future work while keeping the history that already matters.
What happens
- A newly added customer joins later group sessions, not past ones.
- Removing the member clears their Waiting group appointments while keeping completed history and relevant payment records.
Result: Future participation changes without rewriting completed work.
Remove a staff member who has waiting appointments
Waiting appointments remain usable after the personnel relationship ends.
What happens
- The owner removes the staff member from that business.
- Their Waiting appointments move to the owner while dates and times stay the same.
Result: The owner can later assign another staff member.
Open a financial view with a staff role
The visible financial scope depends on the person's current access level.
What happens
- Nexora checks the person's relationship with the business and access level.
- Company-wide, own-summary, and restricted views follow the documented permission boundary.
Result: The person sees only the financial scope allowed for that role.
Share an appointment through WhatsApp
Nexora prepares a message; the business controls the send action.
What happens
- The business opens the prepared appointment message.
- It reviews the text and chooses whether to press Send in WhatsApp.
Result: Nexora does not send this prepared message on its own.
A client books through the online booking link
The business has turned on online booking; the client books on their own, under the business's rules.
What happens
- The client taps the link in the business's Instagram bio and picks a service and one of the free times in the calendar.
- They type their name and send the ready message that opens in WhatsApp.
- If the business has turned on 'Let me approve first', the request goes to the business first; otherwise the appointment is confirmed right away.
Result: The appointment lands in the business calendar and the business gets a notification; the client's WhatsApp chat receives the confirmation and a link to change or cancel the appointment.
Save work when a device notification cannot arrive
The business action and device delivery are separate outcomes.
What happens
- The appointment, package, or payment action is saved.
- A device alert also needs the recipient's account, current device registration, and notification permission.
Result: The saved business action still counts even if no device notification arrives.
Delete an account linked to business customer records
Account deletion removes the account connection without erasing a business's customer history.
What happens
- The person completes the Nexora account deletion flow.
- Nexora removes the user account link from business-owned customer records.
Result: The business records can remain without an account link.
Use different roles in different businesses
One account can have separate relationships with independent businesses.
What happens
- A person is connected to each business through its own relationship.
- Nexora checks the role and access for the selected business.
Result: A role or access change in one business does not change the person's other business relationships.
Last updated: