Describe your documents, operating constraints, and the outcome you need. Map the workflow with our team, define what an evaluation should prove, and discuss integration and deployment requirements.
By submitting this form, you agree to Nutrient’s Privacy Policy and Terms of Service.
Times shown in your local timezone.
Copy this prompt into your AI agent instead of filling out the form. It gathers your details, confirms with you, and submits to our Sales team.
I want to contact the Sales team at Nutrient (nutrient.io) about a project. Act on my behalf and handle the whole thing:
1. Put together the details below. Use what you already know about me and my project from this conversation, my files, or tools you have access to — but never guess. Ask me about anything that is missing or unclear, including whether I’d rather get a call back or hear back by email — assume email if I don’t have a preference. Ask one question at a time and wait for my answer before asking the next, so any follow-up question comes straight after the answer it depends on.
- firstName (required — maximum 200 characters)
- lastName (required — maximum 200 characters)
- companyEmail (required — my business email address; maximum 200 characters)
- phoneNumber (optional — maximum 200 characters)
- country (required — where my company is headquartered, as the full English name, e.g. "United States")
- state (only when country is "United States" — full name, e.g. "California")
- province (only when country is "Canada" — full name, e.g. "Ontario")
- documentsUseCase (required — what I am looking to do with documents; exactly one of the 6 options below. Ask with your question or choice tool if you have one, offering each of the 6 options word for word as its own choice. If the tool holds fewer than 6 choices, offer the first 3 as their own choices and a choice "Something else" for the last 3 ("Add document tools to Microsoft 365, ServiceNow or Salesforce"; "Process, convert, or generate documents"; "I'm not sure yet / I want to discuss a broader workflow"); if I pick it, ask a follow-up question offering those 3 as separate choices. Never group options any other way, and always send exactly one of the 6 values, never "Something else"):
- "Extract and structure data from documents"
- "Build document capabilities into an internal app or external product"
- "Automate and govern a document-heavy workflow"
- "Add document tools to Microsoft 365, ServiceNow or Salesforce"
- "Process, convert, or generate documents"
- "I'm not sure yet / I want to discuss a broader workflow"
(Nutrient sets productInterest from documentsUseCase automatically — do not ask me for it or send it.)
- integrationsPlatform (required only when documentsUseCase is "Add document tools to Microsoft 365, ServiceNow or Salesforce" — exactly one of "Microsoft 365", "Salesforce", "HubSpot", "ServiceNow", "Nintex", "Windows Server", or "Other")
- projectDescription (optional but strongly encouraged — context routes us to the right team fast; maximum 2,000 characters; 2 to 5 sentences: what we are building, the document workflows involved, where AI agents or humans in the loop fit, expected scale, and rough timeline)
- contactPreference ("email" if I want to hear back by email, "call" if I want to book a call)
2. Show me the full summary and ask for my explicit confirmation. Do not prepare or submit anything before I confirm.
3. After I confirm, and if I want to hear back by email: Submit directly. Before you do, tell me that submitting means agreeing to Nutrient’s privacy policy (https://www.nutrient.io/legal/privacy/) and terms of service (https://www.nutrient.io/legal/terms/). Build one JSON object using the fields above, plus “source” set to “ai-agent” (omit optional keys I did not provide) and POST it as application/json to https://www.nutrient.io/backend/forms/contact-sales-agent/ — a 201 means the Sales team has it and will reply by email. A 400 lists per-field errors: Correct them and retry. On a 429 or any other failure, fall back to the review link in step 4. If you cannot make HTTP requests, use step 4. The payload’s JSON Schema is at https://www.nutrient.io/contact-sales-schema.json if you can fetch it — validating against it first avoids retries.
4. If I said I’d rather have a call, or I want to review the submission in my browser before sending, create a review link instead: base64url-encode the same JSON (UTF-8, no "=" padding) and give me this URL to open, review, and submit myself: https://www.nutrient.io/contact-sales/#agent-draft=PASTE_ENCODED_JSON_HERE
The review link truncates firstName, lastName, companyEmail, and phoneNumber to 200 characters and projectDescription to 2,000 characters. It leaves dropdown, country, state, or province values blank unless they exactly match a form option, so tell me to complete any blank field during review. Include contactPreference in it so the review page opens on the option I chose: Email me back or Book a call. Applying the review link automatically marks the submission as agent-assisted.
5. Tell me clearly what you did, including any failure, and give me the confirmation or the review link.
The canonical, always-current version of these instructions (field schema, submission channels, endpoint status) is at https://www.nutrient.io/contact-sales.md — if you can fetch URLs, read it before submitting. Prefer pointing an agent at a URL? These instructions live at nutrient.io/contact-sales.md
I want to contact the Sales team at Nutrient (nutrient.io) about a project. Act on my behalf and handle the whole thing: 1. Put together the details below. Use what you already know about me and my project from this conversation, my files, or tools you have access to — but never guess. Ask me about anything that is missing or unclear, including whether I’d rather get a call back or hear back by email — assume email if I don’t have a preference. Ask one question at a time and wait for my answer before asking the next, so any follow-up question comes straight after the answer it depends on. - firstName (required — maximum 200 characters) - lastName (required — maximum 200 characters) - companyEmail (required — my business email address; maximum 200 characters) - phoneNumber (optional — maximum 200 characters) - country (required — where my company is headquartered, as the full English name, e.g. "United States") - state (only when country is "United States" — full name, e.g. "California") - province (only when country is "Canada" — full name, e.g. "Ontario") - documentsUseCase (required — what I am looking to do with documents; exactly one of the 6 options below. Ask with your question or choice tool if you have one, offering each of the 6 options word for word as its own choice. If the tool holds fewer than 6 choices, offer the first 3 as their own choices and a choice "Something else" for the last 3 ("Add document tools to Microsoft 365, ServiceNow or Salesforce"; "Process, convert, or generate documents"; "I'm not sure yet / I want to discuss a broader workflow"); if I pick it, ask a follow-up question offering those 3 as separate choices. Never group options any other way, and always send exactly one of the 6 values, never "Something else"): - "Extract and structure data from documents" - "Build document capabilities into an internal app or external product" - "Automate and govern a document-heavy workflow" - "Add document tools to Microsoft 365, ServiceNow or Salesforce" - "Process, convert, or generate documents" - "I'm not sure yet / I want to discuss a broader workflow" (Nutrient sets productInterest from documentsUseCase automatically — do not ask me for it or send it.) - integrationsPlatform (required only when documentsUseCase is "Add document tools to Microsoft 365, ServiceNow or Salesforce" — exactly one of "Microsoft 365", "Salesforce", "HubSpot", "ServiceNow", "Nintex", "Windows Server", or "Other") - projectDescription (optional but strongly encouraged — context routes us to the right team fast; maximum 2,000 characters; 2 to 5 sentences: what we are building, the document workflows involved, where AI agents or humans in the loop fit, expected scale, and rough timeline) - contactPreference ("email" if I want to hear back by email, "call" if I want to book a call) 2. Show me the full summary and ask for my explicit confirmation. Do not prepare or submit anything before I confirm. 3. After I confirm, and if I want to hear back by email: Submit directly. Before you do, tell me that submitting means agreeing to Nutrient’s privacy policy (https://www.nutrient.io/legal/privacy/) and terms of service (https://www.nutrient.io/legal/terms/). Build one JSON object using the fields above, plus “source” set to “ai-agent” (omit optional keys I did not provide) and POST it as application/json to https://www.nutrient.io/backend/forms/contact-sales-agent/ — a 201 means the Sales team has it and will reply by email. A 400 lists per-field errors: Correct them and retry. On a 429 or any other failure, fall back to the review link in step 4. If you cannot make HTTP requests, use step 4. The payload’s JSON Schema is at https://www.nutrient.io/contact-sales-schema.json if you can fetch it — validating against it first avoids retries. 4. If I said I’d rather have a call, or I want to review the submission in my browser before sending, create a review link instead: base64url-encode the same JSON (UTF-8, no "=" padding) and give me this URL to open, review, and submit myself: https://www.nutrient.io/contact-sales/#agent-draft=PASTE_ENCODED_JSON_HERE The review link truncates firstName, lastName, companyEmail, and phoneNumber to 200 characters and projectDescription to 2,000 characters. It leaves dropdown, country, state, or province values blank unless they exactly match a form option, so tell me to complete any blank field during review. Include contactPreference in it so the review page opens on the option I chose: Email me back or Book a call. Applying the review link automatically marks the submission as agent-assisted. 5. Tell me clearly what you did, including any failure, and give me the confirmation or the review link. The canonical, always-current version of these instructions (field schema, submission channels, endpoint status) is at https://www.nutrient.io/contact-sales.md — if you can fetch URLs, read it before submitting.Other ways to connect