Xaigh support

Ask Xaigh.
Get help with the work that matters.

Get answers about work, shifts, pay, accounts, trust, or employer operations. If an issue needs a person, Xaigh opens a tracked support case and returns a case number.

How trust works

Search verified answers

Search reads Xaigh's help library. It does not send a chat message.

Start with a common issue

Chat sessions use Xaigh's support controls and can open a tracked case.

Help grounded in Xaigh work

Support follows the real issue to its owner.

Routes real support

Xaigh handles what it can and opens a tracked case when a person needs to step in.

Verifies before offers

Credentials and role requirements are checked before anything goes out.

Keeps account actions gated

Support reviews sensitive account, pay, and trust changes before anything is changed.

Keeps a case trail

Every handoff gets a case number and is routed to the owning support queue.

Xaigh help library

Find the next useful answer.

Browse verified help by topic. Search and reading use the help library; Xaigh AI only runs when you open chat and send a message.

Getting StartedProfile setup, verification, and first shifts.3

Complete your worker readiness profile

A readiness profile is the operating record XaıGH uses to decide whether a worker can act on a shift. The goal is not to make a profile look full; it is to make the worker, employer, and support teams see the same verified inputs before work starts.

What readiness controls

Readiness affects which shifts you can apply to, which employers can review you, and which support team can help if a record looks wrong. XaıGH uses the readiness state to keep identity, role expectations, location fit, and payout records connected.

A completed profile does not guarantee a shift. It means the platform has enough trusted information for an employer to review you without asking support to reconstruct the basics.

Inputs to check first

Confirm your legal name, profile photo, role interests, work location, phone, email, and payout method. If an identity or employer-requested screening step is still processing, Xaigh keeps the check tied to the specific shift instead of making you repeat your account setup.

Profile photos and resumes should match the work you are applying for. Employers are looking for role fit, reliability, availability, and clear contact paths, not generic biography text.

When to open a support case

Open a support case if a completed step still appears unresolved, an old phone or email prevents verification, or the app asks for the same evidence twice. Include the affected screen and account email so support can route the case cleanly.

Do not send sensitive identity images through ordinary email unless support specifically routes you through an approved secure channel.

Legal name and contact details match the verification record.
Role interests and location are specific enough for local shift matching.
Payout method is connected before asking about payout eligibility.
Any unresolved step has a screenshot or exact status ready for support.

Apply for your first shift

A strong first application is specific. It should match your readiness state, location, availability, role experience, and the employer's coverage need.

Read the shift record

Open the shift and check the role, start time, end time, address context, pay, requirements, and required readiness checks. Do this before applying so you do not create a preventable cancellation later.

If the shift mentions equipment, certification, dress, language, heavy lifting, or arrival instructions, treat those as part of the acceptance decision.

Send a clean application

Use the profile and application fields to show availability and role fit. Do not promise skills, transportation, certifications, or arrival windows you cannot support.

If the app shows a blocker, resolve the blocker first. Applying around a blocker makes support slower because the case has to separate eligibility from employer review.

After you apply

Watch the application status and notifications. Employer response time can vary by urgency, shift date, and internal coverage workflow.

If a shift disappears, it may have been filled, closed, or changed by the employer. Search adjacent roles and keep your availability accurate.

Shift time and location work for your real commute.
Visible pay and requirements are understood before action.
Your profile supports the role you are applying for.
Notifications are enabled for application updates.

Understand the market feed

The market feed is a live work surface, not a static job board. It changes when employers post, close, adjust, or fill shifts and when your readiness or location context changes.

Why results move

Results can move when a shift is filled, a start time changes, a market becomes urgent, or an employer narrows requirements. Your own readiness, selected location, and role filters can also change what appears.

A missing result is not always an account problem. Check filters, distance, selected region, readiness state, and whether the shift date has passed.

How to improve matches

Keep role interests narrow enough to show relevant shifts but broad enough to catch adjacent work. For example, hospitality workers may want server, runner, prep, event staff, and porter roles if those are realistic options.

Use location honestly. Over-broad commute settings can create applications that later fail because the arrival window is not practical.

When support can help

Open support case when a specific shift link fails, your region is wrong after updating settings, or a readiness-approved account cannot see a role that should be available.

Include the market, role, filter state, and device context so the support team can separate content availability from an account or app issue.

Region and commute settings match where you can actually work.
Role filters match your experience and availability.
Readiness blockers are resolved before assuming a feed bug.
Support requests include market, role, and filter details.

Payment & BillingPayout review, direct deposits, and tax forms.3

Payout rails and standard transfers

Payout support works fastest when the shift, receipt, employer confirmation, payout method, and processor status are tied to one record.

What has to happen first

A payout depends on the completed shift record, employer confirmation, account eligibility, payout method, and processor timing. Fast payout movement is only available when those checks are ready and the shift supports it.

If the app shows standard payout timing, support cannot turn the article into a payout override. Open a case only when the visible record looks incorrect or stuck.

What to include in a payout case

Include the shift date, employer, receipt ID if visible, payout method type, requested payout time, and the exact status shown in the app. Do not include full bank numbers or card numbers.

Screenshots are useful when they show status labels, not sensitive account details. Crop anything that exposes unnecessary personal information.

Bank and processor timing

Standard bank transfers can take normal processor and bank settlement time. Weekends, holidays, bank reviews, and payout method changes can add delay.

If a payout is marked sent but not received, support needs the payout reference shown in the app and the receiving bank's posted timing before it can escalate.

Shift shows completed or confirmed before payout escalation.
Payout method is active and not recently changed without review.
Support case includes receipt or shift details, not sensitive bank numbers.
Payout eligibility is checked from the app record.

Shift receipts and tax records

Receipts connect the shift, employer, worker, time window, payout context, and support history. Keep questions tied to the receipt so payroll-grade records stay traceable.

What a receipt proves

A receipt is the record XaıGH support uses to connect a completed shift to payout and dispute context. It can include the role, employer, time, status, and payout reference depending on the route.

If a receipt is missing, first confirm whether the shift was completed, cancelled, disputed, or still waiting on employer closeout.

Tax-support boundaries

XaıGH can help locate platform records, receipts, and account information shown in the product. It cannot give personal tax advice through the help center.

If a tax form or yearly record looks wrong, open support case with the account email, affected tax year, and the specific shift or payout records you believe are missing.

Protect sensitive details

Do not send full tax IDs, full bank details, or full identity documents through an ordinary help message. If sensitive evidence is required, support should route you to the approved secure collection path.

Keep your message focused on record mismatch, missing receipt, payout status, or profile details that need correction.

Receipt ID or shift date is available before opening support.
Question is tied to a specific record, not a general account feeling.
No full tax ID or full bank details are included in chat or email.
Tax advice is handled by your own advisor, not the help center.

Employer billing support

Employer billing questions should stay attached to the organization, job, shift, invoice, and approval owner so support can separate finance review from worker support.

Route billing by record

Start with the invoice, shift, worker closeout, or membership record that triggered the question. A support case without those identifiers becomes a finance research task instead of a billing correction.

If a charge is tied to a disputed shift, keep the dispute and billing conversation connected. Do not ask the worker to resolve billing outside the platform.

Who should open the case

Use an account that belongs to the employer organization and has billing or admin authority. This protects worker privacy and keeps invoices away from unauthorized team members.

If the billing owner has left the company, open an account-access case first so support can validate the organization before discussing billing details.

What support can and cannot do

Support can help identify invoice status, shift closeout state, membership context, and missing record details shown in the product. Payment movement, refunds, credits, pricing commitments, and production account changes require approval through the right internal route.

For enterprise contracts, include the contract owner and rollout context. That prevents a public support message from becoming an unauthorized commercial change request.

Case is opened by an authorized employer account.
Invoice, shift, membership, or organization record is named.
Worker dispute and billing issue remain linked when both are involved.
No refund, credit, or pricing commitment is assumed from a help article.

Trust & SafetyReporting issues, suspensions, and appeals.3

Report a shift safety issue

Safety reports need speed and structure. XaıGH support needs to know who is involved, what happened, where it happened, whether the shift is active, and whether immediate danger exists.

Use emergency services first

If anyone is in immediate danger, contact local emergency services first. The help center is not an emergency response system.

After the immediate risk is handled, open a XaıGH case with the shift, employer or worker, location, time, and evidence that can be safely shared.

What to include

Include the shift ID or date, location, people involved, whether the shift is still active, and what action you need support to review. Keep the report factual and chronological.

For harassment, unsafe conditions, threats, or conduct concerns, include screenshots or photos only when collecting them does not create more risk.

How XaıGH routes it

Support may route a safety case to trust and safety, employer operations, worker support, or billing depending on the issue. Some cases require both safety review and shift closeout review.

Account actions, payment movement, legal claims, or public statements are not automatic outcomes from a help article. They require review through the correct internal process.

Immediate danger is handled outside the help center first.
Case includes shift, location, time, and people involved.
Evidence is shared only when it is safe and appropriate.
The requested support action is clear.

Appeal an account or shift action

An appeal should focus on the decision, the affected record, and the evidence that changes the review. General frustration is understandable but does not give reviewers enough to act.

Name the exact action

State whether the issue is a reliability score change, cancellation mark, account restriction, shift status, payment hold, or employer action. Appeals move faster when the reviewer can identify the record immediately.

If you received a notification, include the date and the exact label. Do not rewrite the notice in your own words only.

Evidence that helps

Useful evidence can include arrival context, employer messages, shift instructions, app error screenshots, payout or receipt status, or proof that a requirement was completed before the deadline.

Keep evidence relevant. Extra unrelated messages can slow review because support has to separate the timeline from unrelated account history.

What happens after submission

Support reviews the case against the platform record and may ask for additional context. Some outcomes require trust, employer operations, payroll, or account-access review.

Submitting an appeal does not guarantee reversal. It creates a review path with the right owner and evidence.

Appeal names the exact decision or status being challenged.
Affected shift, account, notification, or receipt is identified.
Evidence is chronological and related to the decision.
No sensitive identity or bank information is sent unnecessarily.

Protect your account and messages

Account security protects work records, payment context, employer communications, and support review. Keep sensitive workflows on-platform whenever possible.

Keep the record on XaıGH

Use XaıGH messaging for shift instructions, worker questions, employer updates, closeout issues, and support-relevant context. Off-platform messages can be harder to verify if a dispute or payout question appears later.

Never move payment, identity, or sensitive account requests to an unofficial channel because someone asks for speed.

Watch for risky requests

Be careful with requests for passwords, one-time codes, full bank details, tax IDs, payment outside XaıGH, or documents sent to personal email addresses.

If a message looks suspicious, capture the context and open support case. Do not keep replying to test whether the other person is legitimate.

Secure your login

Use a strong password, keep your email and phone current, and reset access if you suspect someone else used the account.

If you lose access to your email or phone, open support case with the old and new contact path plus enough account context for review.

Payment and identity requests stay on approved XaıGH routes.
Suspicious messages are reported with context.
Password and contact recovery details are current.
Support cases avoid sharing one-time codes or full financial details.

Account SettingsPasswords, notifications, and privacy.3

Reset your password and secure login

Account recovery needs proof that support is helping the right person without asking for unsafe information in a general message.

Start with reset flow

Use the password reset route from the same email tied to your account. If you do not receive the message, check spam, spelling, and whether your account uses a different email.

Do not share reset links or one-time codes with anyone claiming to help. Support will not need your password.

When reset does not work

Open support case when the email is unavailable, the phone number is old, the reset link is expired immediately, or the account appears locked after repeated attempts.

Include your account email, current contact path, device type, and the exact error label. Do not include passwords or codes.

After recovery

Update your phone, email, password, and notification settings. Review recent messages and account actions if you suspect someone else had access.

Employers should confirm organization admin access after a billing or hiring owner changes roles.

Password reset starts from the official route.
No passwords, reset links, or one-time codes are sent to support.
Support request includes device, error label, and contact context.
Account contact details are updated after access is restored.

Manage notifications and privacy

Notifications are operational signals. Turning everything off can hide application, shift, payout, or safety updates that need quick action.

Keep critical alerts visible

Workers should keep application status, shift changes, employer messages, payout status, and readiness blockers visible. Employers should keep applicant, coverage, billing, and closeout signals visible.

Mute marketing-style updates only after confirming they are not part of the operational workflow you rely on.

Privacy settings

Review profile, location, messaging, and account settings to understand what other platform participants can see. Some information is necessary for hiring or shift coordination.

If a privacy question involves identity, location, safety, or employer access, open support case with the setting name and the concern rather than sending broad personal details.

Device-level issues

If XaıGH notifications are enabled in the app but not arriving, check device notification permissions, focus modes, browser settings, and whether the app is installed on the current device.

For support, include device type, operating system, app or browser, and one example notification you expected.

Critical shift, message, payout, and account alerts stay enabled.
Device notification permissions match app settings.
Privacy questions name the exact setting or screen.
Support requests include device and route context.

Update profile and contact details

Profile and contact changes can affect verification, messaging, employer review, and payout support. Make updates carefully when active applications or shifts exist.

Change the right field

Use profile settings for worker-facing role, contact, region, and bio details. Use organization settings for employer company, billing owner, hiring team, and contact routing details.

If legal name, identity, or verification information is wrong, support may need a different review path than ordinary profile editing.

Active work considerations

Avoid changing critical contact or region settings during an active shift unless necessary. Employers and support need stable contact routes when a shift is live.

If a wrong phone or email blocks an active workflow, open support case with the active shift or organization context.

Employer organization details

Employer admins should keep company name, job-site locations, billing owner, and hiring contacts current. This prevents support from routing worker, billing, and closeout questions to the wrong person.

If an admin left the company, access changes may require organization verification before support discusses sensitive account details.

Worker profile edits are separated from legal identity corrections.
Active shifts are considered before changing contact details.
Employer organization owner and billing owner remain current.
Support request names the affected account, shift, or organization.

Employers CentralPosting jobs, billing, and enterprise tools.3

Post a shift workers can act on

A production shift post is an operating contract. Workers need enough clarity to decide quickly, and support needs enough structure to resolve the record later.

Name the work precisely

Use a role title that matches the actual work. Include start time, end time, location context, required clothing or equipment, physical requirements, language needs, and any certification requirements.

Avoid vague phrases like general help or flexible support when the worker needs to know whether the shift is kitchen prep, receiving, event breakdown, customer-facing retail, or warehouse loading.

Make acceptance safe

Workers should see enough pay, commute, schedule, and requirement context before they act. If a condition is not optional, put it in the shift record.

Keep off-platform instructions out of the acceptance path when they could affect pay, safety, or dispute review.

Close out the record

After the shift, confirm attendance, time, and issues promptly. Closeout delays can block payouts, receipts, reliability review, and support routing.

If the shift had a dispute, keep billing, worker support, and closeout context connected instead of opening separate unrelated cases.

Role, location, schedule, pay context, and requirements are clear.
Worker instructions stay attached to the platform record.
Closeout owner knows who confirms attendance and issues.
Disputes stay connected to the shift and billing context.

Review worker readiness signals

Worker review should connect the job requirement to the readiness signal. This keeps hiring decisions tied to operational fit instead of generic profile impressions.

Readiness is not one score

Look at role fit, availability, location fit, verification state, reliability history, and relevant profile details. A single signal rarely explains the whole hiring decision.

If a worker is missing a requirement, use the platform workflow rather than asking for sensitive evidence through personal messages.

Keep decisions tied to job requirements

Decide against the posted role and schedule. If a requirement was not in the post, do not surprise workers with it after they apply.

For enterprise or high-volume hiring, align the review criteria before posting so multiple hiring managers do not create inconsistent decisions.

Escalate review issues

Open support case when a readiness signal looks inconsistent, a worker appears eligible but cannot be selected, or the review screen does not match the shift requirement.

Include the job, worker application, organization, and the signal that looks wrong.

Review criteria match the posted requirements.
Sensitive proof requests stay inside approved XaıGH workflows.
Multiple hiring managers use the same decision criteria.
Support cases include job and application context.

Manage coverage, messaging, and closeout

Coverage is not complete when a worker applies. It is complete when the worker is selected, briefed, arrives, finishes, and the record is closed correctly.

Manage the full lane

Track open shifts, applications, selected workers, messages, arrival needs, and closeout status together. Splitting these across personal messages and spreadsheets weakens support visibility.

For urgent coverage, keep the shift record current instead of relying only on a chat thread.

Use messages for operational clarity

Send arrival instructions, onsite contact details, role-specific notes, and changes through XaıGH where they can support the shift record.

Do not move payment, identity, or dispute decisions to personal channels. Those decisions need platform records.

Close out quickly

Confirm attendance, time, and any issue as soon as possible after the shift. Closeout affects worker receipts, payout support, employer billing, and reliability review.

If there is a problem, open the support case from the shift context with the action needed: attendance correction, dispute review, payout hold review, or billing review.

Selected worker, arrival instructions, and onsite contact are visible.
Payment and dispute decisions stay on-platform.
Closeout is completed after the shift.
Support cases name the shift, worker, and requested action.

Platform UpdatesRelease notes and protocol changes.3

Release changes affecting shifts

Release notes matter when they change a workflow you depend on. Focus on the route, the audience, the visible state, and what action changed.

Read by workflow

Look for whether the update affects worker applications, employer posting, readiness checks, messaging, payouts, closeout, or support routing.

A visual change is only important if it changes where a record appears, what action is available, or what support context is collected.

When an update seems wrong

If a release appears to break a route, include the page path, device, account role, expected action, and what actually happened.

Do not assume a release caused every missing shift or notification. Check account state, market filters, readiness, and device settings first.

Support routing

Support needs to know whether you are a worker, employer, or organization admin. Route-specific issues should include the affected page and record.

If the change affects money, safety, identity, or production account data, it may require deeper review and cannot be resolved by a public article alone.

Update is tied to a workflow, route, and user role.
Support request includes expected versus actual behavior.
Account state and filters are checked before filing a bug.
Sensitive route changes are handled through support review.

Mobile app readiness path

The mobile app is the fastest worker operating surface, but account, support, and employer records still need to stay aligned across web and mobile.

Use mobile for active work

The mobile path is built for finding shifts, receiving updates, managing readiness blockers, messaging, and checking shift context while moving.

Keep notifications enabled for active work. A missed schedule or employer message can become a real coverage issue.

Keep account records aligned

If you update profile, phone, email, payout, or verification details, confirm the change appears in the surface you use for active shifts.

When web and mobile appear different, note which route, app version, or browser showed each state before opening support.

Install and route issues

If an app link, QR code, or deep link fails, use the web route as a fallback and open support case with the exact link or screen.

Support should know whether the issue is install, login, notification, readiness, shift action, or messaging related.

Mobile notifications are enabled for active shift workflows.
Profile and readiness changes appear across active surfaces.
Broken links are reported with exact path or QR source.
Support request names app, device, and affected route.

Support case routing standards

A production support request names the user role, affected route, affected record, expected outcome, and risk level. That lets XaıGH route the case to the right owner.

Make the owner obvious

State whether the case is worker, employer, billing, trust and safety, account access, payout, mobile, or platform behavior. If more than one area is involved, name the primary blocker first.

A clear owner prevents a payout question from being treated like a login issue or a safety report from being treated like a generic shift problem.

Name the affected record

Include the shift, application, invoice, receipt, organization, market, route, or support case that the request is about. General messages are harder to route and easier to misread.

For product behavior, include expected behavior, actual behavior, device, browser or app, and whether the issue repeats.

Respect approval boundaries

Support can investigate, route, and explain records shown in the product. It cannot use a public help article to approve payment movement, refunds, pricing changes, legal commitments, account ownership changes, production data changes, or public statements.

If the request crosses those boundaries, support should collect the evidence and move it to the proper review owner.

Case includes user role and primary support owner.
Affected record or route is named.
Expected and actual behavior are clear.
Request does not assume approval for money, legal, deploy, or account-control changes.

Frequently asked

How long does identity verification take?

Standard identity review is usually fast when the submitted name, photo, and contact details match. Manual review can take longer when the record needs a human check. XaıGH shows the readiness blocker that still needs attention before a worker can apply to protected shifts.

When do I get paid for a completed shift?

Fast payouts can be requested after a shift is confirmed and the payout method is ready. Standard bank transfers usually settle after normal processor and bank timing. Every payout question should include the job, shift date, receipt, and payout method shown in the app.

What happens if I need to cancel a shift?

Cancel as soon as possible from the shift record so the employer has a clean coverage signal. Late cancellations and no-shows can affect reliability because the platform has to protect active schedules, payroll records, and other workers who could have accepted the work.

How is my hourly rate determined?

Shift pay is shown before action and can depend on the role, location, schedule, urgency, requirements, and employer contract. XaıGH support can help explain the visible pay record for a specific shift, but compensation changes must stay attached to the platform record.

Can I negotiate pay directly with an employer?

No. All compensation should stay on XaıGH so shift records, receipts, taxes, disputes, and payout support stay attached to the same job.

Always a person in the loop

Xaigh prepares the move. You approve it.

Pay changes, messages, and account actions never happen automatically. Xaigh does the work and holds for a human before anything commits.

Controls and current status

EncryptedRole permissionsHuman reviewExplainable AIGDPR / CCPA controlsSOC 2 (in progress)

Ask Xaigh.Get help with the work that matters.