Questions and answers

Yes. The public flow includes the service, the professional, the day and the time according to the configured availability.

From the management link the customer receives or from the staff calendar; cancellation and deposit rules live in Booking settings.

24 hours and 2 hours before the appointment, by email. SMS and WhatsApp reminders run only on the simulator; SMS is not connected in production.

The waitlist makes a single active offer for the slot; the outcome is checked before the next offer.

The CRM profile keeps notes, preferences, consents and the appointment history. Record only what the service needs.

Yes: session packages and renewing memberships; each booking consumes one session exactly once.

Yes, the arrived and completed states are part of the booking and feed the daily report (revenue, no-shows, utilisation).

Not yet. The till prints «KUPON JO FISKAL» (not a fiscal receipt). A real receipt waits for the easyPos connection and the taxpayer’s token.

Not yet. Payment is made at the salon. Card deposits and no-show fees exist only in test, because there is no payment connection in production.

Yes. The service keeps the processing time: the stylist is free while the colour works and takes another client, while the chair stays occupied. The service can also require the allergy test within N days: the public page asks the client, reception records it on the card and a missing test shows as a warning, never silently.

Yes, from approved information. For a booking she proposes a form that a person executes, and she hands the conversation to staff when needed.

Yes. Online booking respects capacity, hours and exceptions, and the confirmation arrives by email. SMS confirmation is not connected.

The resource hours and exceptions are enforced by the engine; no slot is offered outside them.

Yes. Order lines appear on the kitchen screen by station, with the states acknowledged, started, ready, served. Tickets are not printed; they show on the screen only.

Conversation in the Inbox, a task with an owner and the room resource in the calendar when the request concerns the space.

A campaign can be drafted, but it needs the guest’s consent and a second person’s approval. Real sending is not connected; today it runs only on the simulator.

Not yet. The till prints «KUPON JO FISKAL» (not a fiscal receipt). The easyPos adapter is built, but a real receipt waits for the production connection and the taxpayer’s token.

In the Audit: every command with its author, time and change hash.

Because the module is not licensed or enabled: see Licence and Modules; after activation the buttons open.

Yes, on the bank’s separate terminal: the till records the card payment. The integrated terminal exists only in test and online card payment is not connected.

Partly. Offline, opening an order, lines, hold, sending to the kitchen and discount are kept. Payments, shifts and fiscalisation never work offline.

Not yet. The Wolt and Glovo channels are blocked until there is a channel contract and a verified link for the business; outside production they run only with a simulator.

Yes, from the approved FAQ and information, citing the source; without a source the request goes to staff.

Yes, the till finds the item by barcode (weighted barcodes too) and takes the price from the active list.

Yes: sales, receipts, transfers and counts move the stock; the last unit is never promised twice.

Tags and consents on the profile; campaigns with approval before sending.

Not yet. SMS is not connected; SMS offers run only on the simulator.

They are scanned, classified and OCR proposes the supplier invoice; staff confirm before posting.

Yes: cashier, warehouse, manager with separate permissions; location-restricted where needed.

Card yes, on the bank’s separate terminal: the till records the authorisation code. The integrated terminal exists only in test. The fiscal receipt is blocked and the till prints «KUPON JO FISKAL». Offline the cart is kept, but payment waits for the connection.

Yes, both as resources: the appointment is created only when both are free.

Yes. The clinic page has public booking with an email code and a choice of branch; reception confirms per the process.

No. Reminders are sent by email. SMS and WhatsApp are blocked until a provider is connected.

The system reminds reception: after a completed visit a task is created 14 days before the recall date. A patient who opened the portal sees a notice in «Shëndeti im» (My health) with only the clinic and the date. The SMS reminder is blocked and the system does not send it by email, so reception contacts the patient according to their consent.

Reading works: records sealed under RLS and a grant per person with 2FA. Clinical writes in production open per clinic only after the platform validates the environment.

Classification, quarantine with scanning, restricted access and deletion hold.

No. The AI covers reception information from approved sources; diagnosis and treatment belong to the clinician.

Yes: consent evidence and export of personal data from the profile.

Not yet in production. Payment is by bank or cash at the desk. Card deposits and the fiscal number exist only in test.

Yes for small and mid-size hotels: rooms, rates, stays, folio, housekeeping, night audit (Step 16).

Not yet with real channels. The channel port works only with a simulator; the real link has not started and needs a partner contract. Reservations from channels are entered by hand.

The availability grid by room and night with an instant quote; the general calendar stays for rooms-for-events and services.

Yes, from approved information with a source; questions without a source go to reception.

No. WhatsApp is blocked until the hotel connects its own channel. The confirmation is sent by email, with the guest’s link.

Today’s arrivals/departures, in-house, the housekeeping board, tasks and the Inbox.

Yes, as classified documents; guest evidence stays a document reference, not a loose copy.

Yes, the stay price from the rate plan and calendar, with a snapshot per night on the folio.

Not yet. Card and deposits are blocked; payment is made at the hotel. An invoice draft is made from the folio, but the fiscal number waits for the easyPos connection.

Housekeeping has its own tasks and states, separate from room occupancy. The housekeeper sees only hotel data and housekeeping.

Lead, viewing, offer, contract, won or lost; forward only, lost with a reason.

Yes: matching explains the score, the reasons and what is missing; only listings on the market with a mandate.

Yes, listings with statuses draft → available → reserved → closed and a publication mandate.

From the deal: agent, interval, note; an agent conflict is refused (SLOT_UNAVAILABLE).

Yes: closing a listing raises a task for every open deal; the analyst flags stalled deals.

Viewing confirmation and cancellation arrive by email. Reminders by SMS or WhatsApp run only on the simulator and are blocked in production.

Yes. For every deal the commission moves expected → earned → invoiced → paid, with splits between agents; the server refuses a split that does not add up with 422. The property price is never revenue. The invoice leaves without fiscalisation and is paid by transfer.

Won closes the listing and loses the other deals; the commission is earned only with contractual evidence.

Yes, on the Marketplace (/treg), no account needed: sale or rent, zone, price with currency, area, rooms and type; only listings of published agencies with a valid mandate, no simulators; the address at the allowed level (exact, street or city).

Not on the public search: the map provider is blocked (the owner’s decision on tiles and self-hosting); the list is complete without it. Coordinates are geocoded by the platform and stay at city precision when the geocoder does not answer.

Yes: photos are authorised documents of the agency (mandate files stay private and no public lead reads them) and the history is listed from the audit log; no empty field is filled in by the AI.

Yes, both as resources with duration and buffer time.

On the vehicle record: VIN or plate, make, model, year, mileage, condition, documents and price; the purchase cost is seen by managers only. Inventory and customer cars never mix.

Yes: a work order with statuses, hours, materials, the «Quality check» checklist and change orders; the warranty is registered at handover.

Yes: the 12-area DVI inspection with photos from the technician’s phone; the photos live in Documents with role-based access and the inspection becomes a quote.

With a change order the customer approves online; extra work above the business threshold is not billed without a new approval and a changed quote never inherits the old acceptance.

Yes: the job’s parts leave the warehouse exactly once under approval, as material entries on the work order, and are billed from the job; a second entry for the same part is refused.

Yes, by email with an approved template. SMS and WhatsApp are blocked without a provider.

Yes, the invoice from the billable work, paid by bank or cash. The fiscal number waits for the taxpayer’s easyPos token; until then the invoice leaves without a fiscal number.

Yes, on the business’s public page, the «Vehicles for sale» tab: make, model, year, mileage, price and condition as the business keeps them; reserved or sold cars never appear.

No: the CarCheck history is blocked until there is authorisation and a provider contract; a car without a source shows «Unknown — no linked source» and nothing is invented.

Yes: in the automotive settings switch on the dealership, the workshop or both; the tabs and the first steps follow the choice and no data is lost.

Yes: on the studio’s public page they pick the specialisation, the professional, the day and the time; the confirmation code comes by email only (no SMS provider) and staff confirm as configured.

The need, the deadline, the owner and the required documents with due dates; each document opens the task «Collect: …» for the owner, the reminder is sent once 24 h before the due date and a valid portal upload closes it by itself; the client is qualified or declined with a reason.

Yes: planned → active → done phases inside the same job; the transition needs an evidence document when set; hours are recorded per phase and each phase is invoiced exactly once — the second is refused.

Only the business owner and the administrators, the responsible, the assignee and the allowed users; its list, details, hours and documents are shown to nobody else and the commands are refused on the server.

Classification (business, personal, sensitive, restricted), quarantine and scan before they open, a version that supersedes the old one, an owner, an expiry date and access restricted to people; deletion hold and audit.

No: the portal carries only their quote, job and documents — no internal note, work description or intake; the test suite proves the absence.

SMS stays blocked without a provider (the channel is not offered and the request is refused); real email works from the platform; task reminders reach the owner inside the app.

E-signature is not planned: the client accepts the quote from the portal with proof (their link, identity, the proposal hash and the time); a changed quote needs a new acceptance.

No: the assistant answers only from approved sources, drafts and summarises; it never sends documents, accepts quotes or approves anything — the professional signs off. Generation with a language model is off until the superadmin enables it.

From the approved hours of the phase, or of the job when it has no phases: one live invoice per phase (the second is refused), an invoiced entry is never invoiced twice; PDF and client portal. A prepayment is optional; the fiscal number waits for the easyPos connection.

Yes. The public request takes the problem, urgency, zone, skill and time window, and creates a service case.

Dispatch checks skill and time: without the right skill the server answers 422, and when the slot is taken 409. The owner is shown on the job.

Yes, including tasks created automatically by workflows.

A native app is planned. The web app works on a phone and has an offline queue for progress, materials and the checklist.

Yes, in Documents with role-based access, linked to the job.

With a new quote or version, which the client accepts from the portal or on the technician’s device; acceptance is bound to the hash of the quote.

By email, yes. SMS and WhatsApp are blocked until a provider is connected.

Not by online card. The invoice is paid by bank or with cash declared in the field and reconciled by another person. Online card payment waits for the owner’s payment provider.

The shopping agent opens the cart and places the order only after the code the customer confirms. In production the inbound channel (WhatsApp, Instagram) is blocked, so today it runs only on the simulator.

Yes. The page /dyqani/<name> has products, availability, a guest cart, an email code, cash on delivery or transfer, and order tracking. It is a fixed page: themes, SEO and an app store are not part of the offer, and online card payment is blocked.

From the catalogue, price lists and the approved FAQ, showing the source.

Stock is reserved by the server, the same as at the till. If the last unit is taken, the second buyer gets a 409 error instead of a double sale.

The shipment and the expected cash are recorded, and the courier settlement is entered by hand. A real courier link needs the owner’s contract and is blocked.

Yes, tags, preferences and consents; approved campaigns.

Not yet. Real messages need the connected channel (the owner’s verified app and number); today they run only on the simulator.

They start from registered events and create messages/tasks per the approved template.

Reading works: the record sealed under RLS, a grant per person with 2FA and an audit of every open. Clinical writes in production open per clinic only after the platform validates the environment.

Profile, history with allergies, visits with states linked to the appointment, medications; versioned corrections; an open log.

No. A per-person clinical grant is needed; neither the owner nor the superadmin open it by default.

No: reception sees the profile and counts; clinical content needs a clinician/reader grant.

No. It generates no diagnoses, prescriptions, doses or interactions.

Only inside the app. The completed visit creates a task for reception 14 days before the recall date, and a patient who opened the portal sees a notice in «Shëndeti im» (My health) with only the clinic and the date. No email is sent; SMS and push are blocked, so reception contacts the patient according to their consent.

With a reason and the current version; the previous version is kept; or it is marked “recorded in error”.

Not yet for clinical writes: after the environment is validated (hosting, keys, backup with restore, access procedure) the platform opens writing for the clinic. Booking and the calendar work today.

No. On “My health” the patient sees appointments, the reason and the plan of the completed visit, medications and the recall — the diagnosis and the history stay with the clinic.

That nobody has written yet; it is not the absence of allergies. “No known allergies” shows only when the clinician declares it; recorded allergies appear by name at the top of the record.

No. Booking, confirmation and “Arrived” move only the appointment; the calendar says “Clinical visit: not documented” until the doctor writes the visit linked to the appointment and completes it.

Before a new profile an existing one with the same name and birth date, phone or email is looked up; its code is shown and you choose “Open the record” or “Create anyway”.

Not yet: the platform has no SMS provider, so the public page refuses the SMS channel with a reason and the code travels by email; a patient without email books through reception.

Yes: the case from request to invoice draft runs on the server (SEK, VAT 25%, RUT as an estimate). Fortnox, BankID and the Skatteverket submission are blocked without credentials.

Request, versioned quote with validity, approval by a second person, acceptance with a reference, schedule without clashes, job with minutes and materials, invoice draft with the source of the lines.

VAT yes. RUT/ROT only as an estimate for private customers, with the status «Needs verification» until a person other than the one who quoted verifies it; the submission happens in Skatteverket’s service, not from the platform.

Not yet: acceptance is done with a reference. BankID is blocked until the owner brings the provider’s credentials; its state is shown under Integrations.

No: Fortnox is blocked without API credentials; the invoice draft stays in Finance and can be exported.

The Vepra invoice is a full document with a number and a PDF; payment is recorded when it arrives. Card payment is blocked.

Yes: within the business calendar and with a database constraint — two concurrent assignments cannot both pass; external calendars no.

Not yet. Swedish voice is blocked without a voice provider; templated messages need a connected channel and are not sent today.

Yes: the public page /udheto/<slug> accepts a saved place, the phone position or a typed address geocoded by the platform; denying GPS does not block the booking.

The server, line by line from the business tariff (base, km, minute, minimum, night, zones, promo), with the tariff version; the quote is valid for 5 minutes — an expired one is not confirmed, a changed tariff needs a new quote.

By a server offer with a deadline and an estimated compensation (auto dispatch) or by the dispatcher’s assignment; two concurrent acceptances give one assignment, an expired offer is refused.

The state (accepted, on the way, arrived, started, finished), the driver, the plate and the vehicle, the ETA with its source and time, the position only when fresher than 90 s, the PIN for the driver; the driver’s phone is not shown.

Yes: a scheduled booking is registered without a promised driver (registered → assigned → reconfirmed), with the terminal, flight number and meeting point for the airport; the passenger can be someone other than the booker.

Licence, ID, insurance and inspection have an expiry and a verified status; with an expired document the driver cannot go online and is not assigned.

Today cash or card with the driver; online payment needs the owner’s payment adapter and until then is not shown as active.

From its account link with the cost centre; the driver never sees the room; over the monthly limit the booking waits for the dispatcher’s approval; a monthly report per account.

No: “My day” separates trips, cash collected (handed to the business), the commission and the driver’s share; transfers are only the settlement rows the business records.

Not without a provider: the flight is checked manually, masked communication and SOS need a telephony provider — nothing is shown active without one.

Nothing: the category is free by design — School, Customers, Calendar, Finance, Reports, HR, Team and Documents open without a plan and without a licence ladder; there is no price and no “request activation”.

Under Individ → Family & school, only when the account’s verified email is the guardian email at the school and the school gave its consent on the pupil: the group, the timetable, today’s attendance, the 30-day summary, grades, fees due, the 14-day menu and the time of the data. Never who recorded a grade, never the health notes; a stranger sees nothing.

No. There is no public school profile, search or booking: the parent’s entry is the portal after signing in with a verified email and the school’s consent; the public site never lists or invents a school.

The group’s teacher (staff role) only for their own group, or the administration: attendance as a batch per day (present, absent, late, excused) only for today or earlier in the school’s time and only for enrolled pupils — the same day overwrites; one grade per pupil, subject and term. Another group’s teacher is refused by the server.

With the Individ bell inside the platform, once per pupil and day, only when the pupil has the consent for messages and the guardian a verified email; the note text never leaves. No email, SMS or push is sent from here.

Issue the month once for every enrolled pupil with a fee (a second issue of the month is refused); then “paid” with a reference or “waived” with a reason — nothing leaves paid/waived. With Finance on, every fee has its own invoice following the same state; when finance refuses, the fee is kept and the warning shows under the dialog. Teachers never see fees.

No: the platform moves no money. The parent sees the fees due and the payment hint; the school marks it with a reference. Online payment needs a payment adapter and the owner’s decision and until then is not shown as active.

Every administration write (groups, pupils, menu, fees, official notices, staff cards, activities) requires 2FA switched on — without it the server answers 401 MFA_REQUIRED; reads stay open. A teacher records attendance and grades without 2FA.

The save carries the version you saw; if someone changed it meanwhile, the server answers 409 VERSION_CONFLICT and the dialog keeps your draft with a “Reload” button — nothing is overwritten without seeing the new version.

Under School: official notices with the audience fixed at publication (reading ≠ acknowledging, reminders every 2 days), staff cards over the HR employees, activities with clash checks and substitutions, the merged calendar, the staff chat over team channels and Payroll as a read over HR — no parallel registers.

Not yet: parent–teacher messaging is a later phase, and email, push or WhatsApp for parents wait for the owner’s decision on the channel and the consent. Today notices stay inside the platform.

On the category page “Try the demonstration” opens an example on demo data (labelled “Example”), not your school; the real school is registered for free and the Getting-started list takes you to the parent portal.

Because the dashboard belongs to the trade: a restaurant opens on the floor and the kitchen, a hotel on rooms and stays, a salon on the staff schedule, an agency on properties and viewings, a garage on work orders. The numbers and the "To check" list are computed from your data in real time.

Per the owner’s request, no popup appears inside business categories (release notes, the suggestion reminder, the 2FA reminder). You find them on their own pages: What’s new, Suggestions and Account → Security.

The pages a category lives in come first, in the order of the concept screens; nothing was removed — the rest stays below under "More".

Business → Preview: the public booking page, the shop, the client portal, the career page and the client flow of each. The superadmin opens it for any business from Companies or the Simulator ("Open as").

Suggestions use only the skills, languages, city, schedule and availability of the professional profile; every match is explained (matches, gaps, unknowns). You apply; the CV is read and proposed, you confirm the fields. Professional conversations are unrelated to Social+.

Because there is no API or publishing agreement: the channel shows its true capability (none). Assisted channels (Duapune, Njoftime, KosovaJob, PortalPune) get the ready package and are confirmed with the posting link; Google Indexing and Recruitee work through their connection; Jooble through the feed.

5 % of the referred person’s spend every time they pay, for the life of the account; a click is valid 30 days, a claim is one-time, self-referral is refused; earnings are held 30 days and paid above the currency threshold.

Superadmin → AI observability: statistics per function and category, recent traces, people’s ratings, the tracing test. "Create missing prompts" creates the vepra.<function> prompt in Langfuse; a change with the production label applies within 5 minutes, without a deploy. The Langfuse UI opens at langfuse.vepra.ai (DNS record by the owner).

Four screens: System (RAM with a 30-minute history, load, disk, API memory, database, queues), Users (accounts by category, sessions, logins, sign-ups per day), Activity (every action of every user, a live stream every 2 s with a cursor, pause and filter) and Services. The bot line summarises the state and raises alerts from thresholds.

In the database: "business" = active member of a company with a real business, "individual" = a personal workspace without a business, "both", "platform" (the desk) or "uncategorised" (registered, nothing yet). Refreshed every 10 minutes by the worker; the superadmin filters and counts by category under Users.

Not for now, per the owner’s instruction; the Expo skeleton exists as source, binaries are not built. The web works on the phone (bottom menu, PWA).

The country comes from the trusted route header (or the GeoIP provider), never from a client header; XX/T1 and private IPs do not count. You can change and save it; the IP never overrides a manual choice. The full IP never enters the interests profile or the AI.

Because they start OFF at three levels (Individ → news → category) and per channel. Activate them under Categories: choose categories, frequency (digest or immediate), countries and channels. "Breaking" never bypasses OFF; during quiet hours (22:00–08:00) sends are held and stale ones are dropped.

From sources registered in the superadmin desk (News → Sources) with rights as fields: metadata, excerpt, text, photo, AI, translation. A found URL never activates a source; the superadmin tests it ("Test import") and activates it after checking the terms. When a source allows metadata only, you see the headline and "Read at the source". Copies of one article link into one card; different reportings of one event group without losing their differences.

Social is the @username profile, ten communities, daily and weekly challenges, the Vepra quiz and the word of the day, XP and Vepra Coins, friendship (discover, likes and matches between adults only). It is separate from My work: gender, preferences, social GPS, chats, XP and coins never enter job matching or the profile a business sees.

Friendship starts OFF for a new profile (you switch it on in the settings) and GPS OFF: suggestions follow the city you typed yourself. Discovery, likes, new matches and the chat are for adults only. With GPS ON only an approximate zone (0.05°) is stored, never the point. Liking, matching, communities and games are free; Social+ (4.99 €/month trial price, granted by the desk) opens the chat after a match — one of the two having it is enough — and the names of those who liked you. Blocking ends every contact.

The hotel uses the same amenity vocabulary (Wi-Fi, parking, pool, sea view…) as Booking, Expedia and the large hotel systems — choose them on the room and in the settings, the icons appear by themselves. The restaurant has categories with icons, dietary marks and the 14 EU allergens on every item, and illustrations (Twemoji, CC BY 4.0) for fruit, vegetables, bread, meat, dishes and drinks matched automatically from the name; upload a real photo when you want one. "Print the label" on the item page produces a QR; "Scan" in the POS opens the phone camera and the item loads by itself — the producer's barcode works too once added under "Barcodes". Nothing leaves the device.