Requesting an automation
The four-question flow that sends your admin a request for an automation you cannot build yourself.
Automations are built on the web, from templates. When you want one that does not exist, the phone sends your admin a request for it.
Tap the dashed Request Automation button at the top of the Automations list (menu, under Organization). The screen is titled Request an automation, with "Auron scopes it, your admin builds it" underneath.
The four questions
The request is a scripted conversation with fixed questions, not a chat with an agent, so the same four come up every time.
| Question | Example answers offered as chips |
|---|---|
| What should this automation do? | "Log call summaries to CRM"; "Recap a customer visit"; "Chase a quiet deal"; "Draft follow-up emails" |
| When should it run? | "When a call or chat ends"; "On a schedule"; "When a record goes quiet" |
| Which records should it cover? | "All customers"; "Only my accounts"; "Specific sites" |
| Should anything wait for your approval before it happens? | "Yes, before anything sends"; "No, let it run"; "Only for external emails" |
Tap a chip to send it as your answer, or type your own. A counter in the header (1/4, 2/4 and so on) and a progress bar show how far along you are.
Reviewing before you send
After the last answer, a summary card lists your four answers. Tap a line to answer that question again. Start over clears everything and begins again.
Tap Send to admin when it looks right.
What happens after you send
The request goes to your organization's admins. Its name is taken from your first answer, and its description is all four answers. An admin builds it as a template on the web, and once the template is enabled, automations can be created from it.
The confirmation reads Request sent: "Your admin will build it as a template. You will get an update when it is ready to run." See my automations takes you back to the list. There is no request status to check on the phone.
Writing a good request
Answer the second question concretely. "When a meeting ends" or "every Monday morning" gives your admin something to build; "when it makes sense" does not. The same goes for the last question: naming who should approve helps more than saying that approval is needed.