---
title: "Contact Nutrient Sales — Instructions for AI agents"
canonical_url: "https://www.nutrient.io/contact-sales/"
md_url: "https://www.nutrient.io/contact-sales.md"
last_updated: "2026-07-31"
description: "Machine-readable instructions for contacting the Nutrient Sales team on a user’s behalf: field schema, submission channels, and the review-link fallback."
---

# Contact Nutrient Sales (instructions for AI agents)

This document tells an AI agent how to start a sales conversation with
Nutrient (nutrient.io) on behalf of its user. It is the machine-readable
companion of <https://www.nutrient.io/contact-sales/> and is the canonical
version of these instructions — prefer it over any copy embedded in a prompt.

Nutrient Sales is consultative: The more project context you provide, the
faster the right team (including implementation engineers) responds.

## Ground rules

1. Assemble the fields below from what you already know about your user and
   their project — including whether they’d rather get a call back or hear
   back by email (assume email if they don’t have a preference). Ask your
   user for anything missing or uncertain — never guess or fabricate.
2. Show your user the complete summary and get their explicit confirmation
   before submitting anything through any channel. The review link below
   doesn’t carry the call/email preference yet, so if your user wants a
   call, remind them to select “Book a call” themselves during review.
3. Report the outcome honestly, including failures.

## Field schema

| Key | Required | Notes | Channel 2 review-link behavior |
| --- | --- | --- | --- |
| `firstName` | yes |  | Truncated to 200 characters |
| `lastName` | yes |  | Truncated to 200 characters |
| `companyEmail` | yes | Business email address | Truncated to 200 characters |
| `phoneNumber` | no |  | Truncated to 200 characters |
| `country` | yes | Company HQ country, full English name, e.g. "United States" | Left blank unless it exactly matches a form option |
| `state` | when country is "United States" | Full name, e.g. "California" | Left blank unless it exactly matches a form option |
| `province` | when country is "Canada" | Full name, e.g. "Ontario" | Left blank unless it exactly matches a form option |
| `productInterest` | yes | Exactly one submission value below | Left blank unless it exactly matches a form option |
| `integrationsPlatform` | when productInterest is "Low-Code" | Exactly one of the values below | Left blank unless it exactly matches a form option |
| `projectDescription` | no — strongly encouraged | The form accepts submission without it, but context is what routes the request to the right team fast. 2–5 sentences: what is being built, the document workflows involved, where AI agents or humans in the loop fit, expected scale, rough timeline | Truncated to 2,000 characters |
| `source` | yes | Set to "ai-agent". Channel 1 requires and validates it; applying a Channel 2 review link marks the submission as agent-assisted automatically. | Marks the submission as agent-assisted when applied |

`productInterest` values:

| Submission value | Visible form label | Use when |
| --- | --- | --- |
| `"SDK"` | SDK | Embedding document viewing, editing, or AI document processing into your own application |
| `"Low-Code"` | Integrations | Adding document tooling to platforms like SharePoint, Salesforce, or Power Automate |
| `"Workflow"` | Workflow Automation | Automating document-centric business processes |
| `"DWS API"` | Cloud | Using cloud APIs for converting, generating, extracting, and signing documents |

`integrationsPlatform` values:

- `"Microsoft 365"`
- `"Salesforce"`
- `"HubSpot"`
- `"ServiceNow"`
- `"Nintex"`
- `"Windows Server"`
- `"Other"`

The truncation and unmatched-option behavior above is specific to the
Channel 2 review link. It fails safely: Unsupported dropdown, country,
state, or province values are left blank for the human to complete during
review rather than being substituted or submitted silently. Channel 1
validates the same rules server-side and returns per-field errors instead.

## How to submit

### Channel 1 — Direct API (preferred)

```
POST https://www.nutrient.io/backend/forms/contact-sales-agent/
Content-Type: application/json
```

Body: a single JSON object with the keys above (include
`"source": "ai-agent"`; omit optional keys that were not provided). The
payload’s JSON Schema is published at
<https://www.nutrient.io/contact-sales-schema.json> — validating (or
constraining generation) against it before submitting avoids a `400`
roundtrip. Responses:

- `201` `{"status":"received"}` — The lead is captured; nothing else to do.
- `400` `{"status":"invalid","errors":{<field>:<message>}}` — Correct the
  named fields and retry.
- `429` `{"status":"rate-limited"}` — Wait a minute before retrying.
- `502` `{"status":"error"}` — Capture failed; fall back to Channel 2.

Submit here only after your user’s explicit confirmation. This channel is
lead capture only — the Sales team replies by email. If your user would
rather book a call directly, use Channel 2 so they can pick “Book a call”
and choose a time on the page.

### Channel 2 — Review link (when your user wants to review in the browser or wants to book a call)

Build a single JSON object with the keys above, base64url-encode it
(UTF-8, no `=` padding), and give your user this link to open, review, and
submit themselves:

```
https://www.nutrient.io/contact-sales/#agent-draft=<encoded JSON>
```

Opening the link prefills the human-facing form. Nothing is sent until the
user reviews the fields and clicks Submit, so this channel is safe by
construction.

Worked example — this object:

```json
{
  "firstName": "Ada",
  "lastName": "Lovelace",
  "companyEmail": "ada@example.com",
  "country": "United States",
  "state": "California",
  "productInterest": "DWS API",
  "projectDescription": "Building an agent pipeline that extracts data from supplier invoices and routes low-confidence documents to human review.",
  "source": "ai-agent"
}
```

Encodes (minified; whitespace doesn’t matter — any valid JSON serialization
decodes the same) to this link:

```
https://www.nutrient.io/contact-sales/#agent-draft=eyJmaXJzdE5hbWUiOiJBZGEiLCJsYXN0TmFtZSI6IkxvdmVsYWNlIiwiY29tcGFueUVtYWlsIjoiYWRhQGV4YW1wbGUuY29tIiwiY291bnRyeSI6IlVuaXRlZCBTdGF0ZXMiLCJzdGF0ZSI6IkNhbGlmb3JuaWEiLCJwcm9kdWN0SW50ZXJlc3QiOiJEV1MgQVBJIiwicHJvamVjdERlc2NyaXB0aW9uIjoiQnVpbGRpbmcgYW4gYWdlbnQgcGlwZWxpbmUgdGhhdCBleHRyYWN0cyBkYXRhIGZyb20gc3VwcGxpZXIgaW52b2ljZXMgYW5kIHJvdXRlcyBsb3ctY29uZmlkZW5jZSBkb2N1bWVudHMgdG8gaHVtYW4gcmV2aWV3LiIsInNvdXJjZSI6ImFpLWFnZW50In0
```

## Related links

- Technical support for existing customers (not sales): <https://support.nutrient.io/hc/en-us/requests/new>
- Site-wide agent index: <https://www.nutrient.io/llms.txt>
- Privacy policy: <https://www.nutrient.io/legal/privacy/> · Terms of service: <https://www.nutrient.io/legal/terms/>

Submitting through any channel constitutes agreement to the privacy policy
and terms of service above — that is part of what your user must confirm.