Introduction and Context
About 2 minutesLet's look at a day's messagesFictional example; numbers are illustrative
She receives dozens of messages a day: delivery notifications from suppliers, leave requests from staff, and task screenshots from the regional manager.
Previously, she would read each message, note it down, and then sift through chat histories at night to organize them, often missing things.
She wants her phone to help: when a message arrives, send it to Dragon Warrior with one tap, have it organize the tasks, and save them to the notes app. But she has concerns: will it reply to others on her behalf? Will it read messages it shouldn't?
Step-by-Step: Sharing, Screenshots, and Shortcuts
About 11 minutesTwo Gatekeeping Rules
Minimum Permissions
Grant only the permissions necessary to complete the task. Avoid granting access to contacts, photos, location, or microphone unless absolutely necessary; for photos, select 'Limited Access'.
Draft Only, Do Not Send
Let it draft messages intended for others, but only draft them. For emails, chat replies, or notifications, copy the text, review it yourself, and then click send.
Share Menu: Sending Content to an AI App
Convert Screenshot to To-Do
Quick Actions: Combining Two or Three Steps into One
Step One
Select an action like 'Get Clipboard Content' to read the text you just copied.
Step 2
Select an action like 'Send text to an app.' If you can't find a corresponding AI app, stop at Step 1 and paste manually instead.
Step 3
Select 'Save result to Notes.'
Industry Edition: Take a photo, save to Notes, and share. Draft only, do not submit.Fictional example; numbers are illustrative
After handling an issue on-site, he converts the record into a description within a work order; before shift handover, he also writes a duty handover report.
Before taking a photo, first cover the serial number, network address, and customer identifier according to the masking checklist. Save the photos and voice notes to Notes first.
Share with the AI app, instructing it only to draft the work order description: symptoms, actions taken, and follow-up items. Do not include causes or conclusions.
Copy the draft back to the work order system, read it himself, and then click submit himself. The 'submit' action is never delegated to it.
Mobile Project Card Step 2: Connect the workflow
Gatekeeping, Prompts, and Pitfalls
About 5 minutesThree things before starting work
Copyable prompts
Suggested timeHere is a message I received: [Paste or share the content]. Please organize it into a to-do list: task, responsible person, deadline. Write 'to be confirmed' for missing information; do not guess. Draft only; do not reply to anyone on my behalf.
This is a screenshot of tasks. Transcribe each task item by item, then organize them into a to-do list: task, responsible person, deadline. Highlight any items that are unclear. Do not add content not present in the image.
Please draft a reply to the following message, with a [friendly/formal] tone, no more than [fifty] words. This is just a draft; I will review it and send it myself: [Paste message]
Mobile phone pitfalls
Quiz and Wrap-Up
About 2 minutesThree quick questions to check yourself
Question 1: Which of the following practices aligns with 'minimum permissions, draft only, do not send'?
Next lesson: Privacy, costs, and subscriptions
How should mobile users make their choices?
- Open the privacy section in your system settings, review the permissions for each app, and revoke access for any you don't use.
- Record the time spent and number of errors for each session this week; you will need this data when calculating costs in Lesson 10.
Show the full transcript (video narration)
Cross-App Workflows on Mobile
Welcome to Lesson 9 of the 'AI Implementation Workshop' Mobile-Specific Channel. This lesson covers cross-app workflows, which means linking two or three apps together. It follows two core rules: minimum permissions, granting only the access needed to complete the task; and draft only, do not send, meaning any message intended for external recipients must be finalized by the user with a final click.
Let's look at a day's messages
Let's look at a scenario, which is fictional, with illustrative numbers. Store Manager Fang, who manages a chain of stores, receives dozens of messages a day: delivery notifications from suppliers, leave requests from staff, and task screenshots from the regional manager. Previously, she would read each message, note it down, and then sift through chat histories at night to organize them, often missing things. She wants her phone to help: when a message arrives, send it to Dragon Warrior with one tap, have it organize the tasks, and save them to the notes app. But she has concerns: will it reply to others on her behalf? Will it read messages it shouldn't? These two rules in this lesson are designed to address these concerns.
Two Gatekeeping Rules
Two rules for gatekeeping. First, least privilege: whenever an app requests permission, ask yourself, 'Do I really need this?' For contacts, photos, location, and microphone, deny if possible. If you must allow, choose 'while using the app' rather than 'always allow.' For photos, select only specific images. Second, draft but do not send: let it write messages for others, but never send them automatically. For emails, chat replies, or notifications, always copy the output, review it yourself, and then click send. You can revoke permissions at any time; location settings are typically found under Privacy in System Settings, though the exact path depends on your current version.
Share Menu: Sending Content to an AI App
Use the Share Menu to send content to an AI app in four steps. First, in a chat, browser, or file app, long-press the text or tap the 'Share' icon. Second, look for the AI app's icon in the share menu. You might need to tap 'More' to find it, or it might not be there; if so, revert to copy-paste. Third, once the content is in the input box, add a request and send it. Fourth, copy or save the result to your Notes. Before sending anything in, check the message for client privacy, unpublished data, passwords, or original contract text.
Convert Screenshot to To-Do
Converting a Screenshot to a To-Do List involves four steps. First, Blur Before Screenshot: before taking the screenshot, blur or crop out unrelated chats, avatars, and phone numbers. After capturing, use the crop function in your photo album to keep only the parts relevant to the task. Second, Let It Organize: in the app, select the screenshot and say: 'Organize into a to-do list. Clearly state the task, responsible person, and deadline. Mark missing items as 'To Be Confirmed.' Third, check item by item against the screenshot to ensure nothing was missed or fabricated. Fourth, copy to Notes or Reminders, and set the reminder time yourself. Anything unclear or missing must be marked 'To Be Confirmed.' Do not let it guess.
Quick Actions: Combining Two or Three Steps into One
The system's built-in shortcut actions can combine several steps into one. The entry point and action names vary by system, so refer to your current version for verification. The simplest combination involves three steps: Step 1, select an action like 'Get clipboard content' to read the text you just copied. Step 2, select 'Send text to an app.' If you can't find the corresponding AI app, stop at Step 1 and paste manually. Step 3, select 'Save result to Notes.' It's okay if you can't get it to work; the Share menu plus Notes is sufficient. Don't spend more than five minutes on shortcut actions.
Industry Edition: Take a photo, save to Notes, and share. Draft only, do not submit.
The Industry Edition is also fictional. For Duchuan Communications' Network Operations Engineer Hong Zhiyuan, after handling an issue on-site, he converts the record into a description within a work order; before shift handover, he also writes a duty handover report. Before taking a photo, he first covers the serial number, network address, and customer identifier according to the masking checklist, and saves the photos and voice notes to Notes. He shares with the AI app, instructing it only to draft the work order description: symptoms, actions taken, and follow-up items. He does not include causes or conclusions. He copies the draft back to the work order system, reads it himself, and then clicks submit himself. The 'submit' action is never delegated to it. Duty handover is the same: read-only; alarms it hasn't seen cannot be written as 'no anomalies.'
Mobile Project Card Step 2: Connect the workflow
Step 2 of the Mobile Project Card is to integrate the task selected in the previous lesson into the workflow. For example, for Monday's inspection report: the input is voice or screenshot, the processing is your four-line template, the output is the draft in Notes, and review and send are completed by you. Write this workflow as a single line, for example: 'Voice key points, paste template, generate draft, I verify numbers, I send.' Start running it today, and record the time taken and number of errors each time.
Three things before starting work
Before starting, there are three things to do. First, confirm that your company permits you to use real materials for testing, and record who approved it, when, and what was approved as a release record. Second, if this task is performed only once a week, two weeks of samples are insufficient: extend the trial period to four weeks and use historical materials for backtesting to supplement the sample. Third, the total of live runs and backtests must be at least eight to ten items, specifying how many belong to each category. These figures will be needed for the calculations in Lesson 10.
Copyable prompts
Three copyable prompts. Convert messages to to-do items: write 'to be confirmed' for missing information, do not guess, draft only, and do not reply to anyone on your behalf. Convert screenshots to to-do items: highlight unclear items and do not add content not in the image. Draft replies: this is just a draft; you will review it and send it yourself. Each prompt must include constraints like 'draft only' and 'do not guess'. In the workflow, the steps 'I review' and 'I send myself' are both essential.
Mobile phone pitfalls
There are five pitfalls on your mobile phone. First, sharing menu sends to the wrong recipient: chat contacts often appear at the top of the menu; check the icon carefully before selecting. Second, shortcut operations run automatically: before testing, set them to run only when manually triggered. Third, excessive permissions: develop the habit of checking permission settings once a month. Fourth, privacy in screenshots: clear the notification bar, chat avatars, and phone numbers before taking a screenshot. Fifth, auto-reply: do not let any app reply automatically on your behalf; any outgoing message must be sent by a human. Dates, amounts, names, and deadlines must be verified by you before entering them into reminders.
Quiz
Quiz: Which of the following practices aligns with 'minimum permissions, draft only, do not send'? A, Allow it to read all chat history and reply automatically. B, Send only one message, have it generate a draft, and I will review and send it myself. C, Grant all permissions to the app to save future setup efforts. The answer is B. Grant only the permissions necessary for this task; the final sending action for outgoing messages must be performed by a human.
Next lesson: Privacy, costs, and subscriptions
The next lesson is Lesson 10 of the Mobile Phone Series: Privacy, Costs, and Subscriptions. It covers how to select apps, how to calculate costs, and how to check data toggles. For today, please open the privacy section in your system settings, review the permissions for each app, and revoke access for any you don't use. Also, record the time spent and number of errors for each session this week; you will need this data when calculating costs in Lesson 10. Thank you for watching. See you in the next lesson. This video's narration is AI-generated.