Store-client block state
How it works
Customer blocking and unblock tools
Block or unblock a problematic customer at the store-client relationship level and keep that state visible to owner surfaces.
Some businesses need a way to manage customers who repeatedly no-show, abuse booking flows, or create operational problems. Dorak exposes block/unblock state for authorized owner/admin use without turning it into a public customer-facing label.
Best fit
Use this when a business needs an operational safety control tied to customer management and booking rules.
Customer workflow
- Customers normally book, reserve, or request through supported Dorak flows.
- If a store blocks a customer, backend booking rules and customer-facing app behavior can prevent or explain blocked actions where implemented.
- The action remains tied to that business relationship rather than being a public marketplace claim.
Business-owner workflow
- Open the owner-facing client/customer surface.
- Block or unblock the selected customer for the store when needed.
- Review notes, no-show count, booking history, and status context before making operational decisions.
Concrete supported capabilities
Owner/dashboard block and unblock action
Backend cached-client block projection consumed by booking rules
Upcoming appointment cancellation behavior when block events are consumed where implemented
Customer-facing blocked-state handling in app surfaces
Connected no-show and customer-history context
Who uses it
- Repeat no-shows
- Problematic booking behavior
- Store-client safety
- Owner operations
- Customer history review
Screenshot still needed: Best screenshot: owner client detail screen showing block/unblock action with synthetic data.
Related industries
Related features
Related industries
Block or unblock a problematic customer at the store-client relationship level and keep that state visible to owner surfaces.
Join Dorak free