Prepare one working manual loop
Before hiring, make sure you can manually plant, harvest, craft or stock, and complete customer sales. Staff are confirmed by the official description, but an employee cannot repair missing supplies, full outputs, blocked destinations, or an unprofitable operating cycle.
Watch where you repeatedly interrupt an important task to perform a simple chore. That repeated action is the best candidate for automation if the live employee panel supports it. Public sources do not publish the complete role list, hire costs, unlock levels, speed, or limits.
Open the current staff control and read it
Use the hiring or staff interface presented as you level. Read the unlock condition, cost, role or assignment, and stated effect before confirming. Keep enough ordinary funds to replant the garden and continue one production cycle.
Hire once, then inspect the employee’s current status. If there is an assignment, toggle, or priority, use the exact live label. Change one setting at a time. Do not assume that every worker can harvest, craft, stock, or serve merely because another shop game uses those roles.
Give the employee valid work
Prepare the required input and a free destination. Keep stations and displays accessible. Clear narrow paths and move decoration away from interaction zones. If building mode permits, place frequently connected work areas closer without blocking players or customers.
An idle worker with no valid task is not broken. Create the supported work first, then observe the response.
Measure whether the hire helps
Before hiring or activating staff, observe a fixed session with similar stock and layout. Count completed useful actions or completed sales, and note how much time you spend on the repeated task. After hiring, repeat under similar conditions.
Look for a shorter customer queue, faster stock movement, less idle workstation time, or more player time available for planting, crafting decisions, and building. Character movement alone is not value. If the worker only shifts the bottleneck downstream, improve the newly blocked station rather than buying another employee immediately.
Compare the hire with another upgrade using the live price and effect. Staff are most valuable when work is continuous and reachable. Capacity is more valuable when the existing system remains full even with good routing.
Coordinate your work with staff
Let the employee handle a supported predictable task while you handle decisions and exceptions. Avoid competing for the same interaction unless the queue is larger than their capacity. Keep upstream production supplied so automation does not idle.
After moving a station or adding a building, test staff again. Layout changes can create longer routes or inaccessible targets. Make one building change, run a full cycle, and restore a simpler path if behavior worsens.
If an upgrade changes speed or capacity, observe whether the worker remains the limit. Do not upgrade staff when they spend most of the session waiting for materials.
Troubleshoot an idle or stuck worker
Check in this order: a valid task exists, required supplies exist, output space is free, the assignment is active, paths are open, and the shop or customer state allows work. Move your character away from tight interaction areas and remove one obstruction at a time.
If the employee repeatedly walks a long route, move connected stations closer before expanding. If they loop near an object, test with decoration removed. If the interface freezes, record the displayed status, wait for the action, and reconnect once. Confirm that the hire and assignment persisted before repeating a purchase.
If the problem remains repeatable, record the role, task, source, destination, layout, date, and server state. That information distinguishes a path issue from missing work or a version bug.
Staff FAQ
When should I hire my first employee?
After one manual loop works and a supported repeated task clearly consumes time needed elsewhere, while the shop can still fund its next production cycle.
Why is staff idle?
The normal causes are no task, no input, full output, inactive assignment, blocked route, or inactive customer state. Check them before reconnecting.
How many staff can I have?
No complete first-party capacity table was publicly available. Read the current live slots, locks, and upgrade effects.
Should I upgrade staff speed?
Only when that worker is continuously active and remains the measured bottleneck. Speed does not help a worker waiting for supplies.
Can staff craft bouquets?
That specific assignment is not publicly confirmed. Trust only the role and behavior shown by the current employee panel.