Pack-out skipped, reason given
A restaurant manager refuses a fixture change, and the merchandiser can't check out until she records why.
The story
Zoe · Merchandiser · Grill House, Burwood
Zoe arrives at Grill House in Burwood at 3:00 to fit the new drinks menu board and reset the cooler. The manager, Tony, says the franchise owner hasn't approved the new board and won't let her fit it. She completes the cooler reset but leaves the menu board task. When she taps Check Out, FieldKo asks for a reason. She picks "refused by store", names Tony, and checks out at 3:25.
Configured for your team.
On the phone
- No silent missesCheck-out asks for a reason for every unfinished task, so nothing disappears.
- Who refused, and whyThe reason and the store contact are saved, so the account team knows who to talk to.
- Visible on MondayThe refusal shows in the exceptions report, alongside every other unfinished task.
In Salesforce, after sync
Zoe syncs at 3:40. The refusal is on Monday's exceptions report.
One visit, itemized
Everything this visit sent back to Salesforce.
Each line is a record in your own org, under your permissions, reportable with the tools your team already uses.
Features in this exampleFIELDKOGrill House BurwoodFri 14 Nov
Check-in3:00 PM
Tasks1 of 2
Unfinished with reason1
Check-out3:25 PM
Sent toSalesforce
✓ SYNCED
Related examples
On the phoneWorks Offline