Requesting an automation
The four-question flow that files a request for an automation you cannot build yourself.
Automations are authored on the web, from templates. When you want one that does not exist, the phone files a request for it instead of pretending to build one.
Open it from the + in the Automations tab, or the dashed Request new automation button under the list.
The four questions
The request is a scripted conversation rather than a chat with an agent, so the questions are always the same four and there is nothing to prompt-engineer.
- What it does.
- When it runs.
- Which records it covers.
- Whether anything needs approval first.
Each question offers example answers as chips you can tap, which is faster than typing and shows the level of detail that is useful. Your answers appear as messages, with a progress bar and a counter in the header so you know how many are left.
Reviewing before you send
After the last answer, a summary card lists your four answers. Tapping any line reopens that question so you can change it. Restart clears the draft and begins again.
What happens after you send
The request goes to your organization's admins with a name taken from your first answer, all four answers as the description, and the context of where you sent it from. An admin builds it as a template on the web, and once the template is enabled you can create automations from it.
The confirmation screen says as much: someone will build it. There is no status to check on the phone.
Writing a good request
Answer question two concretely. "When a meeting ends" and "every Monday morning" produce a template someone can build; "when it makes sense" does not. The same goes for question four: naming who should approve is more useful than saying that approval is needed.