Your brand.
Services on demand.
An ecosystem
built around time.
Launch and manage instant or scheduled hourly services across house help, wellness, IT support, drivers, cooks and more. Connect the customer app, partner app and admin operations—from the first request to the final payout.
Subscription options · White-label launch · Configurable service models
Right when you need it.
Choose your service.
One app. Multiple service categories.
Illustrative customer app
Product illustration · Sample data · Not a live booking
A SERVICE MODEL, NOT A SINGLE INDUSTRY
Different services.
The same connected operating system.
Configure the service catalogue, coverage, duration and partner rules for your market. Select a category to explore an example.
Examples show the model’s flexibility. Specialist fields, partner eligibility, pricing and operating requirements are confirmed during setup.
TWO BOOKING MODES
“I need help now.”
“I need help tomorrow.”
Offer instant requests and scheduled bookings in the same customer journey.
THE QUICK SERVICE OS JOURNEY
From a customer’s tap
to a completed, settled job.
A connected flow for the customer, service partner and operating team.
Discover & book
Select the service, location, mode and duration. Add customer instructions and choose an available payment option.
Assign & accept
Send the request through supported automatic rules or manual dispatch. Partners receive an alert and respond.
Verify & start
Use configured OTP verification to start the job. Record the start event against the booking.
Time & extend
Track the service session. Apply the agreed extension process when the customer needs more time.
Complete & bill
Record completion, work proof and the final service charge under your billing rules.
Review & settle
Collect customer feedback and review payment status, commissions and partner payouts.
Assignment, verification, extension approval, billing increments and settlement rules depend on the selected package and configuration.
TIME IS PART OF THE SERVICE
Booked time.
Service time.
A clear extension process.
Hourly services need more than a calendar slot. Quick Service OS connects the service timer to the booking, with extension and administrative stop workflows configured around your business.
- Define service durations and rate cards
- Record start and completion against the job
- Support timer, extension and force-stop workflows
- Agree rounding, overtime, approvals and dispute handling
The display is illustrative. Exact charging rules, paused time, refunds and extension approval behaviour must be agreed before launch.
Animated illustration, not an actual running timer
THE COMPLETE PRODUCT ECOSYSTEM
One brand outside.
Connected operations inside.
Build the customer, partner and office experience around your service model. Deliverables follow your selected package.
Admin & operations
Manage service categories, locations, bookings, partners, rate cards, payments, commissions and reports under the agreed setup.
need today?
Customer experience
Service discovery, instant or scheduled requests, duration selection, booking status, payments and reviews.
Partner experience
Assignment alerts, accept/reject, job details, configured verification, timer workflows and job history.
A branded booking website completes the customer-facing package where included. Customer apps, platforms, branding and website scope are confirmed separately from the core admin-plus-partner SaaS offer.
SOLVE THE OPERATING PROBLEMS
Demand can arrive instantly.
Your team still needs a clear process.
Give requests, assignment decisions, time records and payments one connected home.
Requests arrive, but ownership is unclear.
Calls and messages do not show who is handling the booking.
A shared booking record with assignment and service status.
The wrong partner receives the job.
Availability, location and service eligibility need to shape dispatch.
Configure supported assignment criteria and give the office manual control.
Customers and partners disagree about time.
An hourly service needs a recorded start, end and extension process.
Connect timer events to the booking and agree charging rules in advance.
Extra time becomes an unclear charge.
Ad hoc extensions make the final bill difficult to explain.
Define extension approvals, rate rules and how extra time reaches billing.
The team repeats the same updates manually.
The customer wants status; the partner needs job details.
Configure customer WhatsApp and partner app notifications around service events.
Revenue and partner earnings sit apart.
Payments, commissions and completed work must be reconciled.
Use payment records, commission configuration, payouts and reports by plan.
WHATSAPP & PUSH UPDATES
Keep the customer informed.
Give the partner the next action.
Connect supported notifications to booking and service events. Decide who receives what, and at which stage, during configuration.
- Booking confirmation and assignment updates
- Partner job alerts through the app
- Service-event messages using approved templates
- Follow-up and repeat-service campaigns by scope
Messages are examples. WhatsApp template approval, consent, provider charges and trigger configuration apply. Push delivery depends on connectivity and device settings.
House help · 60 minutes. Open your booking to see the latest assignment status.
Review the service, location and booked duration. Respond through the partner app.
Review the extension under your configured approval and billing process.
Illustrative notifications · No messages are being sent
PASSES, PACKAGES & RETURNING CUSTOMERS
A repeat-service model
designed around your offer.
Your reference app includes a pass entry point. Quick Service OS can be scoped around repeat bookings, hour bundles or membership benefits where these fit your commercial model.
Pass entitlements, validity, redemption, rollover, refunds and recurring charges require an agreed configuration or custom scope. A software subscription is separate from a membership sold to your customers.
CHOOSE YOUR LAUNCH MODEL
Subscribe to operate.
White-label to build your brand.
Choose the product scope and commercial model that fit your launch. Both require a clear service catalogue and operating rules.
Quick Service OS on SaaS
Start with the operational platform and agree the hourly/instant modules and customer-facing add-ons your business needs.
- Core admin panel and partner app subscription
- Quick-service configuration confirmed for the chosen plan
- Customer app and website separately scoped where needed
- Plan limits, billing terms and integrations agreed up front
Your own quick-service brand
Launch a branded ecosystem with customer app, partner app, admin and website deliverables defined in your package.
- Your app name, brand and agreed platforms
- Instant and scheduled service workflows by scope
- One-time software licence under the quoted package
- No recurring per-user or monthly software licence fee under that package
Hosting, APIs, messaging, app-store accounts, support/AMC and custom development may be charged separately. Source-code access is separately agreed.
| Component | Subscription | White-label |
|---|---|---|
| Admin + partner app | Core SaaS; modules by plan | Branded scope and platforms agreed |
| Customer app + booking website | Add-ons / separately scoped package | Deliverables specified in quotation |
| Timer, extensions & instant assignment | Quick-service plan and rules confirmed | Configured within agreed scope |
| Passes, memberships & special pricing | Configuration or custom development | Configuration or custom development |
| Integrations & custom workflows | Assessed and quoted separately | Assessed and quoted separately |
A PRACTICAL LAUNCH PROCESS
Define the rules.
Then build the experience.
Use a demo to validate your actual operating model before confirming the delivery scope.
01 / Map your model
Choose categories, cities, coverage, durations, partner types and whether requests are instant, scheduled or both.
02 / Agree your ecosystem
Confirm apps, website, admin modules, branding, payment and messaging integrations, plus any custom rules.
03 / Configure, test & launch
Validate booking, assignment, timers, extensions, completion and settlement before rollout. Timelines follow approved scope and store review requirements.
QUICK SERVICE OS FAQ
Your service model.
Your questions answered.
Bring the workflow you want customers and partners to follow. We’ll identify the product configuration and any custom work.
What is SERQ Quick Service OS?
It is a specialised SERQ offering for instant and scheduled time-based services. It connects customer booking, partner operations and the admin workflow, with apps, modules and commercial terms defined in the chosen package.
Can I launch a service model like Snabbit or Pronto?
You can discuss a similar instant or hourly service business model under your own brand. The scope is built around your categories, coverage and operating rules; this does not imply affiliation with those companies or a feature-for-feature replica.
Is it only for house help?
No. The model can be configured for house help, at-home wellness, IT support, drivers, cooks and other time-based services. Specialist intake fields, eligibility and industry workflows must be reviewed during scoping.
Can customers book now or choose a future slot?
The offering supports instant-request and scheduled-service models under the agreed configuration. Actual availability and arrival times depend on your service coverage, partner supply and assignment process.
How are timer extensions and extra charges handled?
Quick-service workflows include time tracking and extension requirements. Agree the duration units, rounding, overtime, approvals, force-stop behaviour and final billing rules for your package before launch.
Does every subscription include customer apps?
No. The core SaaS offer includes admin and partner operations. A complete customer-facing subscription ecosystem can be scoped with app and website add-ons; the exact Quick Service OS modules and deliverables are confirmed in the package.
Can I sell passes or memberships to my customers?
Share the entitlement and redemption rules you want. Passes, hour bundles, memberships, expiry, refunds and recurring payments are assessed for configuration or custom development rather than assumed universal inclusions.
Can one platform run several service categories?
Yes, a multi-category service model can be scoped in one platform. Set the catalogue, rates, coverage and partner eligibility for each service, and review any category-specific booking or delivery requirements.
Does white-label mean there are no ongoing costs?
The agreed white-label licence can have no recurring per-user or monthly software licence fee. Hosting, third-party APIs, messaging, payment processing, store accounts, support/AMC and optional development remain separate according to your agreement.
Do you guarantee a fixed launch or arrival time?
No fixed arrival promise is made on this page. Customer arrival times depend on your operations. Software delivery depends on scope, branding, account readiness, integrations and app-store review.
BUILD YOUR QUICK-SERVICE BUSINESS
Your next service brand
starts with a clear operating model.
Tell us your categories, target locations and hourly-service rules. See how Quick Service OS can connect your customer, partner and office workflows.