When to use support

Use support when a product action is blocked, unclear or needs manual review. Examples include signup issues, billing checkout problems, a brief that cannot publish, a provider profile that will not save, partner attribution questions or a trust concern.

What to include

• The account email and whether you are using an organisation, provider or partner account.
• The page or route where the issue happened, such as /dashboard/employer/jobs or /dashboard/worker/profile.
• What you expected to happen, what actually happened and any visible error message.
• Screenshots or short screen recordings when layout, billing, verification or profile-preview issues are involved.

Use the right route

• Use /contact for general product support or a blocked public-site action.
• Use /dashboard/privacy for signed-in export, deletion and marketing preference actions.
• Use /privacy for public-site data requests such as newsletter, newsroom and contact-form data.
• Use trust review routes or support when the issue involves misleading claims, proof misuse, message conduct or suspicious marketplace activity.

During launch

Some support paths are manual. Give enough context for Deployed Works to review the correct account, brief, profile, introduction or billing record without a long back-and-forth.