Practical answers for buyers and sellers

Use Post a Task, add a clear title, describe what you need, choose the city and category, set a budget, and publish when the details are ready.

Explain the scope, location, timing, budget, and anything the seller should know before offering. Clear details reduce back-and-forth later.

Yes. A realistic budget helps sellers decide whether the task fits their time, travel, and skill level.

You can edit task details when the current task state allows it. If offers are already involved, keep changes clear so sellers know what changed.

Choose the closest category and make the description specific. Sellers rely more on the written scope than on the category alone.

Eligible sellers can send an offer with their price, message, and availability. Buyers compare offers before accepting one.

Yes. A task can receive multiple offers, but the current marketplace flow moves forward with one accepted seller.

Compare the seller's profile, reviews, message quality, price, timing, and whether they clearly understand the work.

Look at price, scope, availability, profile quality, reviews, and any details the seller adds. The cheapest offer is not always the best fit.

Use the platform conversation where available to clarify timing, scope, and expectations before accepting an offer.

Create an account, build your profile, and complete the required payout setup shown in your account before sending offers.

Giggly needs a connected payout setup so completed work can move through the platform payment flow instead of relying on private payment promises.

In the current flow, sellers need the required payout setup before sending offers. Check your profile or payments area if you are unsure what is missing.

Task acceptance is not payout availability. Funds move toward release after completion in the platform flow, and availability can depend on payment state, connected payout setup, and provider timing. The seller's payout is the offer price minus Giggly's 10% platform fee.

Availability can wait on completion confirmation, task or payment status, payout account setup, or payment provider timing. Check the task and payments area first.

When a buyer accepts an offer, payment starts through Giggly's in-platform flow and stays connected to the task record.

Giggly charges a 10% platform fee to each side of the transaction. The buyer pays the offer price plus 10% at checkout, and the seller's payout is the offer price minus 10%.

The seller fee covers the platform work behind each completed job, including hosted payments, escrow, dispute handling, verification checks, and account tools that help sellers get paid safely. Both sides contribute so pricing stays predictable and the marketplace can keep running.

No. Paying through Giggly keeps the task, offer, and payment together. Private transfers create more confusion and less platform context.

The accepted seller is tied to the task, payment starts through the platform flow, and both sides use the task and conversation history to keep work clear.

Funds move toward release after the task reaches the appropriate completion point in Giggly's payment flow. Exact payout availability can vary.

Keep communication tied to the task, document what happened, and use the reporting or support path with the task reference and useful details.

Verification means the platform check shown on the profile has been completed. It is a trust signal, not a full guarantee of future behavior or work quality.

No. Verification can reduce uncertainty, but you should still review profiles, reviews, pricing, scope, and communication before moving forward.

No. Keep payments on Giggly for the clearest task record and the strongest platform context if something goes wrong.

Watch for pressure to move payment off-platform, unclear pricing, changing scope, refusal to keep details in writing, or behavior that feels suspicious.

Keep payment on Giggly, keep important details in writing, confirm scope before work starts, review profiles and reviews, and report suspicious behavior early.

Reviews are tied to completed task activity and help buyers and sellers build reputation over time.

No. Reviews are useful signals, but you should also consider profile quality, communication, price, task fit, and scope clarity.

Look for a clear name or business identity, useful description, relevant skills, review history, and communication that matches the task.

Completed task history can show that someone has worked through the platform flow before, which helps build credibility over time.

Pause, keep communication tied to the task, write down what happened, and use the most relevant support or reporting path.

Document the timeline in the task conversation where possible. If the issue affects payment, completion, or safety, use Report a Problem.

Pause and clarify the new scope, price, and timing in writing before continuing. Do not rely only on a verbal change.

Do not continue privately. Use the reporting or help path and include the task reference, timeline, screenshots, and relevant messages where possible.

Go to Report a Problem, choose the closest issue type, and include clear details so the issue is easier to understand.

After signing in, use your profile or settings area to update public details, skills, availability, and other account information that is editable in product.

Use the login and password reset flows. If you still cannot access your account, use the relevant support path with the email connected to your account.

Read the Privacy and Cookies pages for how Giggly explains data use and cookie choices.

Use the GDPR Data Request page for data access or deletion requests and include the account email that matches your request.