ATS with ChatGPT: query your candidate database

In the app or plugin flow available in your ChatGPT environment, search for Hice and start connecting it. Sign into Hice and authorize the account you intend to use. A useful first request is to show available operations and read a known record without changing anything.

If your environment allows custom connectors, Hice's MCP endpoint is https://app.hice.ai/mcp. Interface and availability depend on the product, plan and workspace rules. Current conditions are described in the ChatGPT plugins guide. Do not paste an API key into a regular conversation to establish this connection.

Separate necessary requirements from preferences: skills, experience, location and verifiable constraints. Ask the assistant to search accessible Hice data and show evidence and missing information for each candidate. Availability should not be inferred merely because a profile is public.

Connector search and model analysis are not automatically the same engine as Hice's native matching. Check available operations before requesting a function. If an attachment or semantic search is inaccessible through the connector, use the app's supported flow rather than expecting the model to read content it has not received.

Use a table with requirement, profile evidence and information to verify. Request an explanation for each suggestion rather than only a score. A useful request is: 'Compare these three candidates for this search and prepare questions that clarify their differences.'

Keep facts separate from interpretations. 'Has worked with Java' can be documented; 'will be the best team member' needs more evidence. A shortlist is a proposal for the recruiter rather than an automatic hiring decision. Review the supporting information before sharing a summary with the client.