Contact support

Choose the right path

Use one of the paths below so your request lands with the right team on the first pass.

How requests are routed

Use the right support path so the team can respond faster. Technical blockers, rollout planning, and sales conversations should not arrive through the same channel without context.

• Product questions and technical blockers should be submitted through Contact so the request reaches the right team on the first pass.
• Candidate access issues should first be resolved with the invite link from the hiring team, then escalated through support when needed.
• Integrations and rollout planning can start in Contact so the implementation team can scope access and timing.
• Sales, procurement, and partnership requests should be submitted through Contact with rollout context and target timelines.

What to include in a useful support request

Use the right support path so the team can respond faster. Technical blockers, rollout planning, and sales conversations should not arrive through the same channel without context.

• Role or workflow name affected by the problem.
• Candidate or session context when relevant.
• The exact route used and what happened instead of the expected result.
• Timestamp, screenshots, and exact error text whenever possible.