Contact HumanTask API

Contact

This page exists to route different contact intents cleanly. It should answer that intent directly and avoid borrowing generic copy from unrelated HumanTask API pages.

Business and Enterprise

Use the business contact path for multi-location workflows, recurring field tasks, enterprise integrations or partnership discussions. Include the countries, approximate task type and expected frequency so the conversation starts with operational context.

Developer Questions

Integration questions should include the interface you plan to use, the capability you need and whether the task must be created by an AI agent or a conventional application.

Worker Support

Workers should use a separate support path for account, task, evidence or payout questions so supply-side issues do not get mixed with sales.

Marketplace Partnerships

Local operators, field networks or specialized service providers may be relevant as supply partners when they can execute standardized tasks in defined geographies.

Press and Research

Requests about the AI-to-human task category can be routed separately from customer support. The company should avoid presenting projected marketplace statistics as current facts.

Include Enough Context

A useful message names the task, location, timeline and desired integration. 'Tell me more' is harder to route than a concrete workflow.

Response Expectations

The page should not promise a response time that operations cannot guarantee. It should simply collect the information needed to send the inquiry to the right function.

Next Action

For Contact, use this page as the decision point for its specific intent. Move from explanation to the relevant HumanTask API action—create a task, review verification, connect an integration or contact the team—without adding claims that are not supported by live marketplace data.

Page-Specific Focus

Treat Contact as a decision page, not a catch-all. Its specific purpose is to route different contact intents cleanly; adjacent information should be linked rather than duplicated.

Future First-Party Content

Future improvements to Contact should come from product data, not filler. Real task patterns, interface states or customer workflows can make the page harder to copy and more persuasive.

Conversion Path for Contact

The page should lead to a next action that matches its intent instead of showing every possible CTA. For Contact, the visitor should move toward the most relevant route after understanding route different contact intents cleanly. Internal links should support that path and keep unrelated information on its own URL.

Content Maintenance

Review Contact when the product changes one of these related areas: Business and Enterprise, Developer Questions, and Worker Support. Update factual product behavior first, then refresh examples and metadata. Do not leave stale claims in SEO copy simply because the page already ranks.

SEO Intent Boundary

Contact should target its own intent and rely on internal links for adjacent questions. This prevents the core pages from becoming near-duplicates and makes it easier for search engines and AI systems to choose the correct URL for a specific query.