Skip to content
SABSUSServices
RUDiscuss a task

The service-business workspace

An appointment is the start.
Connect the whole visit.

Schedules, services, practitioners, clients and visit settlement share one administrator workspace. SABSUS Services connects an appointment to its order, tasks, files and available payment methods instead of leaving it as an isolated calendar event.

Working data requires an account, permissions and relevant connections.

One visit with connected contextWORKFLOW
  1. 01AppointmentClient · services · practitioners
  2. 02WorkTasks · files · comments
  3. 03SettlementAmount and confirmed payments
  4. 04Next visitHistory and the next step
Workflow illustration · not an app screen.

Calendar + order

Timing and visit details connect to settlement

Client + context

Shared profile, history, tasks and files

Team + access

Administrators use Services; practitioners use Master

01 / A clear workflow

From choosing a time to the next visit

Suppose a client needs two services from different practitioners. The administrator selects timing and services, checks the price, saves the appointment and continues with the same client and order.

  1. 01

    Build the visit

    Choose the client, services, practitioners, duration and available time. Service options and modifiers are included in the quote.

  2. 02

    Check and save

    Review the current price and schedule warnings. Wait for confirmed saving, not merely a card appearing in the queue.

  3. 03

    Work with the order

    Add relevant tasks, comments or files. The practitioner continues their part in Master within granted permissions.

  4. 04

    Reconcile settlement

    Check the total and confirmed payments. Use an authorized settlement method or prepare an available payment link.

02 / Working tools

Not just booking, but the operations around it

01

Calendar and multiple services

Plan across days, weeks and other available periods, viewing practitioners and resources. One appointment can include several services with different practitioners and options. Conflicts and out-of-hours work require review; a deliberate overlap can be confirmed.

02

Services and team schedules

Maintain service names, prices, durations, galleries and options. Configure working periods, shifts, breaks and days off. Available services and practitioners come from company data, not fixed demonstration lists.

03

Shared client profile

Find a client or create a profile with the necessary contacts, comments and group. Changes affect the shared SABSUS profile, not a separate calendar-only contact. Visit history provides context for the next interaction.

04

Tasks, files and retail items

Link tasks, deadlines, assignees and files to a visit. When needed, add an authorized retail item through quantity, price and availability checks. Files and extra actions save separately, so their outcomes should be checked.

05

Order settlement

Review the amount, discounts, tax, confirmed payments and balance. Where permitted and configured, use partial payment, tips, a client deposit, bill splitting and promo codes. A manual payment record does not mean a terminal actually charged a card.

06

Connected communication and bookkeeping

Configured Social and Voice workspaces open with client and appointment context. Internal accounts and transactions support income, expense and transfer bookkeeping. They do not execute bank transfers or replace bank reconciliation.

Payment follows the actual status

A link is created.
That is not yet payment.

Payments and connected devices

With a connected and eligible Stripe account, prepare a hosted link for the remaining balance, a configured deposit or a selected amount within the balance. Link status and confirmed payment are separate. SMS requires a connected channel with the necessary permissions, a client number and an explicit send.

  • Availability depends on the company, provider and payment-method setup
  • A queued message does not yet confirm delivery
  • A payment link does not guarantee payment

03 / Illustrative scenarios

Three administrator scenarios

A multi-service appointment

Find the client, assign two services to suitable practitioners and check the price and warnings. Wait for saving, then add preparation tasks and relevant files.

Visit and settlement

Review the order, add an agreed retail item if needed and prepare an available deposit or balance link. Follow confirmed payment, not merely the fact that a link was sent.

Review a working period

Review selected visits, service amounts and recorded payments. Compare internal cash and terminal entries with source records without calling revenue profit or practitioner pay.

These are workflow examples, not customer case studies or promised outcomes.

Requirements and boundaries

A workspace for a configured company

Services requires company-administrator access, valid services, practitioners, location and schedules. Payments, telephony, SMS and devices have their own connections and limits. A pending card is not a saved server record. Printing a receipt through a configured template and browser does not establish fiscal compliance or confirmed physical output.

FAQ

The important
questions.

Is Services only an online booking form?

No. It is an administrator operations workspace for the calendar, services, team, clients and linked orders. Booking covers appointment scheduling; Services connects the subsequent visit work.

How does Services differ from Master?

Services is for the company administrator. Master is a separate practitioner workspace for their day, service execution, notes, extra materials and portfolio. Available actions depend on the role.

Is double booking impossible?

The system checks availability and shows conflicts. A deliberate overlap can be separately confirmed, so absolute prevention of every double booking is not claimed.

Are payment links immediately available to every company?

No. An eligible connected Stripe account, enabled online payment method and location setup are required. Availability also depends on the provider, country and account conditions.

Does an internal transfer move money at the bank?

No. Internal accounts and transactions are bookkeeping records. They do not establish actual movement between bank accounts.

Start with your task.
Not another interface.

Explore the right workflow, required connections and access boundaries for your scenario.