feat(api): complete unified v2 mobile surface
This commit is contained in:
41
backend/query-api/src/data/faqs.js
Normal file
41
backend/query-api/src/data/faqs.js
Normal file
@@ -0,0 +1,41 @@
|
||||
export const FAQ_CATEGORIES = [
|
||||
{
|
||||
category: 'Getting Started',
|
||||
items: [
|
||||
{
|
||||
question: 'How do I complete my worker profile?',
|
||||
answer: 'Finish your personal info, preferred locations, experience, emergency contact, attire, and tax forms so shift applications and clock-in become available.',
|
||||
},
|
||||
{
|
||||
question: 'Why can I not apply to shifts yet?',
|
||||
answer: 'The worker profile must be complete before the platform allows applications and shift acceptance. Missing sections are returned by the profile completion endpoints.',
|
||||
},
|
||||
],
|
||||
},
|
||||
{
|
||||
category: 'Shifts And Attendance',
|
||||
items: [
|
||||
{
|
||||
question: 'How does clock-in work?',
|
||||
answer: 'Clock-in validates that you are assigned to the shift, near the configured hub geofence, and using the expected clock-in source such as near-field communication when required.',
|
||||
},
|
||||
{
|
||||
question: 'What happens if I request a swap?',
|
||||
answer: 'The assignment moves to swap-requested status so operations can refill the shift while keeping an audit trail of the original assignment.',
|
||||
},
|
||||
],
|
||||
},
|
||||
{
|
||||
category: 'Payments And Compliance',
|
||||
items: [
|
||||
{
|
||||
question: 'When do I see my earnings?',
|
||||
answer: 'Completed and processed time records appear in the worker payments summary, history, and time-card screens after attendance closes and payment processing runs.',
|
||||
},
|
||||
{
|
||||
question: 'How are documents and certificates verified?',
|
||||
answer: 'Uploads create verification jobs that run automatic checks first and then allow manual review when confidence is low or a provider is unavailable.',
|
||||
},
|
||||
],
|
||||
},
|
||||
];
|
||||
Reference in New Issue
Block a user