You are standing in a parking lot with your Android phone, still annoyed about a delivery that showed up crushed. You open JenAI Chat, tap the Commands icon, choose Write Letters, and say what happened. Thirty seconds later you have a polite, firm complaint letter with the order number in the right place, ready to share to email before you even start the car.
Why was that so fast? The built-in Commands work because someone already chose the role, the tone and the structure for you. You can do the same for the documents you write over and over, and make each one as quick as that complaint letter.
Give the Command a Role and a Few Questions
A custom Command has two working parts. The role tells the AI what it is ("You are a careful note-taker who writes short, factual incident reports"). The Questions are variables the app asks you for on every run, so you never skip the details that make the document useful.
Take a household incident note about a suspicious email that a family member opened on a shared laptop. The Command should ask three things: the sender's address, the time it arrived, and whether anything was clicked or downloaded. Those answers decide what happens next, and they fade from memory within an hour, which is why AI can improve cybersecurity response times. A practical breakdown treats fast, complete reporting as the step that shortens the gap between a bad click and a fix.
Setup takes about two minutes:
- Open JenAI Chat and tap the Commands icon in the bottom right corner.
- Pick an existing category or choose Custom.
- Tap the + in the top right and name the Command, such as "Incident Note."
- Start the Command text with a role, for example "You are an incident report writer."
- Add a Question for each detail you always need: sender, time, what was clicked.
The app's own walkthrough on how to create commands shows the same screens, plus a few playful examples like turning the AI into a thesaurus.
Why the Same Documents Keep Eating Your Evening
Most of the writing that drains your time is not creative. It is the meeting summary for the school committee, the note to the landlord about the leaking tap, the third version of a refund request. You already know the shape of each one. You still rebuild it from a blank screen every time.
The hidden cost is the decisions. Should the date go first? How formal is too formal? Did you mention the account number? A good Command settles those once, and the next fifty letters inherit the answers.
Voice makes it faster. JenAI Chat supports two-way voice, so you can answer a Command's Questions out loud, even through Android Auto, and get a finished draft without typing a word.
What Slows Down an Urgent Note
Urgent writing fails in a predictable way. A strange login alert arrives, or an email asks you to "confirm your bank details," and people either write nothing or write a panicked paragraph missing the one fact anyone needs. A Command with fixed Questions takes the panic out of the format.
Large organizations struggle here too. According to Weforum, organizations surveyed for the 2026 outlook say the biggest hurdles to using AI for cybersecurity are not having enough knowledge or skills (54%), the need for human oversight (41%) and uncertainty about risk (39%).
| Survey finding | Result |
|---|---|
| Leaders who see AI as the biggest driver of change in cybersecurity | 94% |
| Respondents naming AI-related vulnerabilities as the fastest-growing cyber risk | 87% |
| Organizations that assess the security of their AI tools | Up from 37% to 64% |
| Barrier cited: not enough knowledge or skills | 54% |
| Barrier cited: need for human oversight | 41% |
| Barrier cited: uncertainty about risk | 39% |
Take the oversight figure personally. Your Command drafts the note; you read it before it goes anywhere. Never paste passwords or full card numbers into any chat, and keep the incident note to what you actually saw.
Templates Worth Building This Week
Start with three Commands and use them until they feel boring. Boring means they work.
Meeting summary. Role: "You are a meeting secretary who writes summaries under 200 words." Questions: meeting name, date, decisions made, and who owns each follow-up. Ask for decisions first and action items second, so people who skim still see their task.
Complaint letter. Role: "You are a calm, firm customer advocate." Questions: company name, order or account number, what went wrong, and the outcome you want, such as a refund or replacement by a specific date. The built-in Write Letters Command is a good model. Your own version can also lock in your name, address and preferred sign-off.
Household incident note. Role: "You are a factual incident reporter. Do not speculate." Questions: what happened, when, sender or source, whether anything was clicked or downloaded, and what has been done so far, like changing a password. Tell the Command to end with a one-line list of open questions, because that is what your bank, employer or IT contact will ask first.
For longer pieces, borrow from Write Articles: add Questions for audience and word count, and the drafts stop drifting off length.
Build the incident note tonight, before you need it. When a strange email lands, you won't be hunting for the sender's address or guessing when it arrived. You'll tap the Command, answer three questions, and have a note ready for your bank or IT contact in under a minute.