How can we help you today?

You can post jobs, projects, tutoring needs, assignments, or consultation requests.

Yes, you are free to select any expert based on your requirements and preferences.

No. Unlocking your contact on a Direct Connect job only lets someone message or call you -- it does not, by itself, let them rate you. Open "View Contacts" on that job and click "Authorize and send reminder for rating" only for the person(s) who actually did work for you; that's what sends them the rating request. Anyone who tries to submit a rating without this authorization will be blocked and notified by email that they need your authorization first.

On Wallet & Credits (Payment History):

• Total earned — A summary of what you have earned from released payments (figures include the platform share).
• Platform fee — SkillLynk’s portion on those payments.
• In escrow — Money still held until the client approves release (or before you’ve requested release).

It appears while funds are still in escrow. It sends a signal to the payer (client) to approve releasing that payment to you. If you see Awaiting payer approval, your request is waiting on them—you can remind them outside the app if needed. Released means that payment has cleared escrow toward your wallet for that row.

When you withdraw from Payments, your wallet balance for that request is reserved and a withdrawal request is created for our team.

• We review the request and pay your bank outside the app (manual transfer).
• After the transfer is sent, the request is marked Paid on our side.
• If a request is Rejected, the amount is returned to your SkillLynk wallet.

Payments are made securely through the platform. Wallet balances, escrow, and withdrawals are designed so funds are traceable and released only when rules for that payment are met.

Refunds depend on the situation (e.g. escrow disputes or rejected withdrawals). Specific cases follow platform policies and admin review.

The expert requests release when ready; the client (payer) approves release in the flow. After approval, funds move to the expert’s wallet. Exact screens may vary by role—see Payment History and payment approvals in your account menu.

• Funded / held in escrow — Payment succeeded; money is waiting for the release process.
• Release requested — The expert asked for payout; waiting on the payer to approve.
• Released — Escrow cleared for that payment; funds move toward the wallet side as designed.
• Refunded — Money returned per dispute or policy (case-by-case).

Creating a brand-new ticket requires an active Pro subscription. If you are on Basic, you will see guidance to upgrade from Plans & billing (or the upgrade link shown on the ticket screen).

If you already raised a ticket before changing plans, you can usually open and read that ticket to follow up, but new submissions stay a Pro benefit.

Not on Pro yet? Use Contact or your support email for urgent account or payment issues—we still want to hear from you.

1. Sign in to your SkillLynk account.
2. Go to Support ticket (from the FAQ footer link, your menu, or bookmark).
3. Choose Ticket type and Priority (Pro users creating a new ticket).
4. Enter a short Issue title so we can recognize the case at a glance.
5. In Describe the issue, explain what happened, what you expected, dates/times, job or payment references, and any steps to reproduce a technical problem.
6. Attach screenshots if they help (for example payment errors, UI bugs, or chat snippets—avoid sensitive personal data).
7. Submit. You should receive a confirmation by email with your ticket reference.

After submit, use My tickets to see all tickets you created.

When a ticket is created successfully, the app assigns a reference like INC0 followed by an internal number. That value appears in your confirmation and helps you and support refer to the same conversation. Mention it in any related email so we can match you faster.

Pick the label that best matches your situation (you can choose Other if unsure):

• Dispute — Conflicts about work quality, delivery, or agreement between parties on the platform.
• Query — General “how does this work?” questions that need an official answer.
• Complaint — Concerns about another user’s behavior, service, or policy violations.
• Technical issue — Bugs, errors, pages not loading, or features not behaving as described.
• Payment issue — Charges, escrow, wallet, withdrawals, or failed transactions.
• Account issue — Login, profile, roles, verification, or access problems.
• Feature request — Ideas to improve the product (we read all of them; timelines vary).
• Other — Anything that does not fit the categories above.

• Low — Minor inconvenience, no deadline, or a nice-to-have clarification.
• Normal — Default for most issues; use when you need help soon but nobody is blocked from working or being paid.
• High — You are materially blocked (e.g. cannot withdraw, cannot accept work, repeated errors) but there is no immediate safety emergency.
• Urgent — Severe financial loss risk, suspected fraud, account takeover, or another time-critical situation. Please still avoid marking every ticket urgent so real emergencies stay visible.

Statuses describe where the ticket is in the workflow:

• Created — Submitted and queued for the team.
• In progress — Support is actively working on it (often after the first reply or update).
• Re open — You indicated the issue is not fully resolved and want the case continued.
• More information required — We need something from you (screenshots, order ID, clarification) before we can proceed.
• Invalid issue reported — Closed after review; often used when the report does not match platform scope or policy (you may receive an explanation by email).
• Closed — Resolved or completed from our side; read the final message for next steps.

Exact wording on your screen may match these labels; use the ticket thread for the authoritative message from the team.

Open your ticket from My tickets (or follow the link from your email). On the ticket detail page you can post follow-up comments and attach additional images when the form allows it.

When you add a comment, the ticket owner (you) typically gets an email summary of the update. If support or staff posts while you are logged in, you may also get an in-app notification (bell) with a short preview—open it to jump back to the ticket.

If we asked for “more information”, reply in the same ticket instead of opening duplicates—that keeps history in one place.

Use My tickets for a list of tickets you created. Open a ticket from the list to see the full conversation, status, and any actions available to you.

• Email — You receive messages when the ticket is raised and when there is activity relevant to you (for example a new comment).
• In-app notifications — When someone else updates the ticket (for example support), you may see a notification in the header bell with a preview; open it or refresh My tickets to read the full text.
• Same thread — Always check the ticket page for the complete history; email is a summary, not a separate system.

Never paste passwords, full payment card numbers, government ID numbers, or unrelated third-party private data. Describe the issue and share screenshots that crop sensitive fields when possible.

If we need verified information, we will tell you the secure channel to use.

No. One ticket per issue keeps routing and history clear. If something new happens later, open a new ticket and mention the old INC reference in the description so we can link the cases.

We aim to review tickets as soon as possible during business hours. Actual time depends on complexity, evidence provided, and queue volume. Using the right ticket type, clear steps to reproduce, and screenshots speeds resolution. Urgent priority is for genuine time-critical cases—please use it responsibly.

No. End users only see tickets they created. A separate admin view exists for staff to manage the full queue; you will not have access to other users’ private tickets.

Fake postings, abuse, spam, or bypassing the platform are strictly prohibited.