vylan

Request automations

A document request or form request has rules of its own. The most useful one sends it for you.

They are on its Automations tab, its row in the job, and its template.

  • After the intake call
    1. WhenWhen a specific task, document request or form request has a status of: Intake call is Done
    2. Thenthen send the document request

What its rules can watch

ConditionWatches
When the form request has a status of / When the document request has a status ofIts own status.
When the form request is approaching the due date, When the form request is past the due date, When the form request reaches the due dateIts due date. A document request asks the same.
When the parent job has a status ofIts job.
When a specific task, document request or form request has a status of, When the previous task, document request or form request has a status ofA named row on its job, or the row above.
When all previous tasks have a status of, When all previous document requests and form requests have a status of, When all previous tasks, document requests and form requests have a status ofEverything above its row. Not the whole job: that would count itself.
When the parent job is approaching a date, When the parent job reaches a dateIts job's dates.

The questions about the parent job are offered only while it is attached to a job. Then its rules can also notify everyone on the parent job.

One attached to nothing keeps any such rule, and its card says it is waiting for a job. If its job goes to the bin, it goes with it, and comes back with it.

Sending itself

then send the form request or then send the document request sends it as its Send button does. It emails your client, and it appears in their portal. Send to picks who gets it.

  • It sends once, and never one already sent.
  • A status or a date can send it: a date rule sends it by itself, with nobody clicking.
  • It is the only place a rule sends a form request or a document request: a job's or a task's rules never do.
  • One made with a job stays a Draft until sent by hand or by a rule.
  • One still waiting for its client to accept the proposal it came with goes into their portal when they accept, with no email (a prospect, who has no portal, gets its link by email). If it has one of these rules, the rule decides when, once they have. Nothing sends it before they accept: not a rule, not the Send button.
  • Sent with the Send button or by a rule, it does not go to a client who has never been invited to their portal, or whose portal isn't activated: it stays a draft. One an acceptance releases waits in their portal until they are invited.
  • On a document request, only people whose permission set can add tasks can add one; on a form request, it takes Send form requests. It stops if its author loses that.

Its other rules

Its other actions: then put someone on it, then send a client email, then send team member notification and then create a job.

Its status moves by itself (Draft, With client once it is sent, Needs review once the client is done), so no rule on it sets its status.

A form request or document request has one due date, the same one the client sees. then set the due date moves it. Reminders are set on the request: see how reminders work.

Still stuck?

If you can't find it here, write to us. A real person reads it.