Your AI assistant, working with your envelopes.

If you already spend your day in Claude or ChatGPT, you can connect it to SignAndGo and ask about your envelopes, or have it send and chase them, without opening the app. Access is opt-in at every level: you approve the connection, your workspace sets the defaults, and each envelope can be opened up or kept private.

What a connected assistant can do

Read

  • List your envelopes and check where each one stands.
  • See the recipients and who has signed so far.
  • Fetch the completed, signed PDF.

Write

  • Create an envelope and send it for signing.
  • Resend to someone who has not acted yet.
  • Void an envelope that should no longer be signed.

In practice that means typing something like which supplier renewals are still waiting, or chase the new starter pack for anyone who has not finished it, into the chat window you already use, and getting an answer or an action back.

Consent in three layers

Signed agreements are sensitive, so the connector is closed until somebody deliberately opens it, at three separate points.

  • The connection. You approve it on a consent screen that shows whether the assistant is asking to read, to write or both.
  • Workspace defaults. An admin decides whether new envelopes are visible to assistants. Read and write are separate switches, and both start off.
  • Each envelope. Assistant read access and write access can be switched on or off per envelope. An envelope that has not been opened up cannot be seen or changed by the assistant, whatever the connection allows.

Every layer must say yes. Even with a connection allowed to write, an assistant is refused if it tries to void an envelope where write access is off.

An audit log of the assistant's work

SignAndGo writes a log entry for each thing the assistant does through the connection, noting when it happened, what was done and which envelopes it touched. Settings lists every connected assistant, and deleting a connection cuts its access at once.

A worked example: a bookkeeping practice in Exeter

Imagine a two-partner bookkeeping practice in Exeter. The practice is invented for illustration. One partner does most of her planning in an AI assistant. She connects it with read access, and switches read access on for client engagement letters only. On Monday mornings she asks which engagement letters are still waiting and gets a short list. When a client asks for a copy of their signed letter, she asks the assistant to fetch it. In the spring she switches on write access for the batch of annual renewal letters, so the assistant can resend to clients who have not signed. Payroll and staff paperwork stay switched off throughout, so the assistant never sees them.

Habits that keep the connection safe

  • Turn on reading first and leave sending off for a few weeks while you get a feel for the assistant's answers.
  • Ask it to repeat back the name, email address and document title before anything goes out. Clients called Jones or Patel can easily be muddled.
  • Keep staff records, medical paperwork and anything in dispute out of its reach unless you have a specific need.
  • Look at the list of connections in settings each quarter and delete the ones nobody uses.
  • Treat whatever it sends as sent by you, because it goes out in your name.

Nothing changes for the people you send to

A client in Plymouth receiving an envelope your assistant created gets exactly the email, signing page, audit trail and certificate they would get from one you made by hand. The connection only alters your side of the work.

Sorting envelopes before you switch anything on

Before flipping per-envelope switches one by one, spend ten minutes sorting your usual paperwork. Engagement letters and supplier renewals that you chase every month are where status questions eat time, so reading access pays off there first. Batch letters you resend regularly are the natural place to try sending access. Personal, medical or contested paperwork belongs in a group that stays closed. Put that sorting into a short team note, and colleagues will set the switches the same way rather than guessing.

Questions your data protection lead will ask

  • Which envelopes can the assistant read? Only those whose assistant access is switched on.
  • Who connected it, and can we remove it? Each connection is listed in settings, and removing one stops its access straight away.
  • Is there a record of what it did? Each action is logged with the time and the envelopes involved.
  • What does the assistant's provider do with what it is given? That depends on your account with the provider, so check their terms and your settings there.

If the assistant gets something wrong

An assistant can misread a request: chase the wrong client, or draft an envelope for the wrong person. Read what it proposes before you confirm. If something goes out that should not have, void the envelope at once, which stops anyone signing it. Then check the log to see what happened, and narrow the access if the mistake came from an envelope the assistant did not need to touch.

For the developer API and webhooks, see the API integration guide. Questions about the connector can go to privacy@myandgo.ai.

Frequently asked questions

Which assistants can connect?
Claude and ChatGPT, along with other assistants that support the same connection standard.
Can the assistant see every envelope once connected?
No. It only sees envelopes whose assistant access is switched on, and the workspace defaults start off.
Can I remove the connection?
Yes. Remove it in settings and its access stops straight away.
Is there a record of what the assistant did?
Yes. Each action is logged with the time and the envelopes involved.

See SignAndGo for your team

Send your first envelope in a few minutes, and keep every signed copy with its audit trail.

See how it works