Sanaf AI
Start free
Signatures

eSignatures.io, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your eSignatures.io account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Signatures
  • Connects with a key
  • 7 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What eSignatures.io is

eSignatures.io provides a platform for sending and signing mobile-friendly contracts over the web.

You paste in a key from your own eSignatures.io account. It is kept encrypted, and you can withdraw it from inside eSignatures.io whenever you like.

How a run works

One message in, the work done in eSignatures.io.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in eSignatures.io. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own eSignatures.io account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

7 tools it already has

What it can do in eSignatures.io

These are the ready-made tools your AI employee already has in eSignatures.io. It is not limited to them, but it never has to be taught these.

  • Create ContractTool to create a new contract using a specified template and signer details. use after selecting a template when you need to send a contract for signature.
  • Create SignerTool to create a new signer profile. use when you need to add a signer to an existing signature request.
  • Create TemplateTool to create a new template. use when you want to register a reusable contract template after defining document elements.
  • Delete TemplateTool to delete a specific template by its id. use when you need to remove an unused or outdated template after confirming its id.
  • Get TemplateTool to retrieve details of a specific template by its id. use when you need to fetch a template’s metadata after selecting its id.
  • List TemplatesTool to retrieve a list of all templates. use when you need to browse available templates before selecting one.
  • Withdraw ContractTool to withdraw a contract by its id. use when you need to prevent further signing of a contract that hasn't been fully signed.
Access, and who is in charge of it

You stay the boss of your eSignatures.io account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own eSignatures.io account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in eSignatures.io is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in eSignatures.io and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about eSignatures.io

Can an AI employee really work inside eSignatures.io?
Yes. It signs in to your own eSignatures.io account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of eSignatures.io?
No. Nothing moves and nothing is replaced. Your records stay in eSignatures.io, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my eSignatures.io account?
You paste in a key from your own eSignatures.io account. It is kept encrypted, and you can withdraw it from inside eSignatures.io whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in eSignatures.io?
It has 7 ready-made tools in eSignatures.io today, among them Create Contract, Create Signer and Create Template. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use eSignatures.io and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in eSignatures.io and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in eSignatures.io?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in eSignatures.io is written down with what it did and when.