Go-live checklist

Use this checklist before you rely on an automation for everyday work.

Before you start

You should already have one automation that has finished at least one run. If you do not, begin with Getting started.

1. Check the job itself

1. Run the automation on three or four real examples, not only the easy one.
2. Include an awkward example: a request with a detail missing, or one that should not be handled at all.
3. Confirm that Tensor stops when information is missing or conflicts. It should not guess.
4. Read the receipt for each run. Check what came in, each step, what you approved, and the result.

2. Check how work arrives

1. If work arrives by email, forward a real email and confirm that a run starts.
2. If a website form feeds the job, submit the form and confirm that its notification email starts a run. A form can start a run only through the email it sends.
3. If your team will type requests in the app, have one teammate try it.

3. Check connections

1. Confirm that each connection the job needs is working: Gmail, Google Calendar or Google Sheets.
2. For anything else that runs in a browser, confirm that the steps you showed still match how you do the job today.

4. Set approvals and limits

1. Leave approvals as they are for the first days. Tensor asks before it writes or sends anything.
2. Once results are steady, decide which routine steps may run without asking, and set limits for them.
3. Remember that a reply or message Tensor writes always waits for your approval.
4. Agree who on your team approves, and what they do when they are away.

5. Check your team

1. Add the people who need access. Each plan includes a set number of users.
2. Give each person the role that fits what they do.

6. Check your plan

1. Estimate how many runs the automation will finish in a month. Each finished run costs one credit.
2. Compare that with your plan's monthly credits.
3. Decide what you will do if your credits run out: add extra credits, or let work pause until your monthly credits reset.

The numbers are in Billing in credits.

7. Have a way back

1. Note which version of the automation you are going live with.
2. If a later correction makes results worse, roll back to that version.

The first week

• Read receipts every day for the first few days.
• Correct any run that is not right. Each correction becomes a new version.
• Widen limits only after you have seen steady results.
• Add a second automation once the first one runs without surprises.

If something goes wrong

See Troubleshooting, or email support@tensorautonomous.com.