Agent setup
Set up DeskPOS Quickstart.
Private POS setup with sales, bookings, payments, receipts, stock, customers, and daily close actions.
First proof
Working checkout, booking flow, MMQR receipt, and daily close insight on their starting catalog.
Queued job
Intake-to-first-proof packet with source manifest, first run steps, acceptance tests, and approval boundary.
Kickoff pack
Client-ready kickoff message, source request, 48-hour plan, and operator checklist.
What we need
- Business type
- Menu or product list
- Staff list
- Wallet name
- Logo and hours
Accepted samples
- service menu
- staff list
- payment wallet name
- last ten sales or bookings
Role playbook
Choose owner, operator, or technical admin mode above. The selected role is added to this setup request as a routing hint.
Owner
- First action: Approve the first proof target: Working checkout, booking flow, MMQR receipt, and daily close insight on their starting catalog.
- Approval focus: Scope, price, payment route, external sends, connector writes, and first production run.
- Success signal: Owner can decide whether the worker saves time, reduces risk, or moves revenue before any recurring claim.
Operator
- First action: Collect the starting source pack: service menu, staff list, payment wallet name.
- Approval focus: Confirm sample quality, missing fields, edge cases, and whether the first proof matches daily work.
- Success signal: Operator can repeat the workflow with less manual checking and fewer missed follow-ups.
Technical admin
- First action: Map the approved source boundary for spa data before any connector access.
- Approval focus: Accounts, permissions, API/export path, audit logs, vaulting, and rollback plan.
- Success signal: Technical admin can explain what the worker can read, what it cannot do, and how every action is logged.