Using It
Example prompts, what happens when the assistant creates a case, and habits that keep you safe.
Once connected, you talk to your assistant normally. When a request involves sending something for signature, the assistant calls NextSign's create_case tool with the details you gave it — or, when you name one of your templates, looks it up in your document library and calls create_case_from_document with the fields filled in.
Example prompts
| You say | What the assistant sets up |
|---|---|
| "Send contract.pdf to jane@example.com for signature." | One case, one signer, sent immediately by email |
| "Anna (anna@firm.dk) signs first, then Jonas (jonas@firm.dk)." | Two signers in order — Jonas is only asked once Anna has signed |
| "Send it to +45 12 34 56 78 by SMS." | An SMS signer — a phone number replaces the email |
| "Make it a draft so I can check it first." | A draft case — nothing is sent until you open it in the dashboard and send it yourself |
| "It should expire in 14 days and remind them every 3 days." | Expiry and automatic reminders on the case |
| "Which templates do we have?" | Lists your document library — names, whether each is a fillable template, and how many fields it has |
| "Send our Employment Contract to Andreas, starting 1 September, 37 hours a week." | Finds the template, reads its fields, fills what you said, asks about any required field you did not mention, then creates and sends the case |
What actually happens
- The assistant calls
create_casewith a title, the signers, and the documents. - NextSign creates the case and — unless it's a draft — emails or texts every signer their signing link.
- The case appears in your dashboard immediately, attributed to you, and the assistant reports back the case id, its state, and the delivery status per signer.
The assistant only knows what you tell it. Exact names, correctly spelled email addresses, and which document to use are your job — it cannot look colleagues up in your address book.
How the assistant gets the document
Three ways, depending on what you have:
- A link — a public
https://URL the document can be fetched from. - The file itself — attach it in the conversation and the assistant sends the contents along (up to 20 MB). Whether attachments reach the tool depends on the assistant app.
- Your NextSign library — a document that already lives in NextSign (Dashboard → Documents). The assistant can list the library, read which fields a template needs, and fill them from what you tell it. Fields it cannot fill from your message, it will ask about — a required field left blank is rejected rather than sent empty.
Working from a template
A .docx in your library is a template with {tag} fields — a name, a start date, a list of terms. When you ask for a case from one, the assistant:
- Finds the document with
list_documents(by the name you used). - Reads its fields with
get_document— which are required, which are dropdowns, which depend on others. - Builds the values from your message and asks you for anything required that is missing.
- Calls
create_case_from_document, which fills the template, renders it to PDF and sends it.
The library the assistant sees is the one you would see in the dashboard: the company's shared documents, your own private ones, and anything another company has shared with yours. A colleague's private template is not available to it.
Good habits
Ask for a draft when unsure. A draft case sends nothing — you review it in the dashboard and press send yourself. There is no undo for a sent case; recalling it means deleting the case after signers were already emailed.
Give complete details up front. One message with title, signers (in order, with addresses), and the document beats a back-and-forth where something gets lost.
Asking twice creates two cases. If the assistant reports an error or a timeout, check the dashboard before asking again — the case may already exist, and a second request would email your signers a second case. See Troubleshooting.