Outcome: Explain what work an agent may move forward and complete a four-part handoff for one familiar task.
The idea
An agent can choose and carry out steps toward an outcome within delegated limits. It may handle a recurring job or a one-off task. A chat window does not tell you what it can do: chatbots and copilots may also call tools. Ask what actions can execute, who authorises them, and what record remains.
The academy teaches outcome, steps in existing tools, gates, record. A team describes the result; the agent prepares or performs allowed steps; a named person approves sensitive execution; an action log records intent and outcome. This is a teaching design, not a claim about a verified product release.
Academy policy always requires a separate named-person approval before send, pay or delete, including small amounts and familiar recipients. A draft can wait. A timeout holds or escalates; it never means yes.
Before you try a handoff
Use the fictional examples below first. Before using your own material, write down authorised data and purpose, the smallest mailbox/folder/field access, the named owner and backup, retention, and the person and stop route for an exception. No live outbound action is allowed outside the stated approval process. If any of those are missing, keep this a paper exercise.
Singapore's Personal Data Protection Act 2012 and Thailand's Personal Data Protection Act B.E. 2562 are practitioner briefing references, not legal advice. Flag people in Thailand for the customer's privacy lead/counsel to assess. IMDA's Model AI Governance Framework for Agentic AI is the governance reference. Editions, URLs, dates and sections are pending verification; see the regional briefing. Formal questions go to customer counsel and, for FusionWork, its DPO.
Approving a send is not privacy consent from everyone named in the email. Track where data goes: mailbox → evidence → draft → approver → destination → logs/backups. Remote viewing from Bangkok and processing in Singapore or another country need review too. Keep only necessary records for an agreed period. An incident goes first to the responsible customer incident/privacy lead, who decides notifications.
Four ways this could help Lane & Hoy
Lane & Hoy is a fictional Singapore wholesaler with work connected to Bangkok. All people, amounts, mailboxes and domains are invented; .invalid addresses cannot be used as real destinations. These examples do not imply a standard software stack for Thai small businesses.
| Role | Outcome, preparation and human stop |
|---|---|
| Operations / delivery | Find the missing delivery document for PO-TH-18. Compare the authorised delivery folder and prepare a request. Do not invent a document or send the request without the operations approver. |
| Sales / CRM | Find incomplete company records and prepare a follow-up for a contact who has an authorised relationship with the team. Show proposed field changes and evidence; a salesperson approves the exact outbound message. |
| Support | Classify a return question, retrieve the current policy and draft a reply. If policies conflict or translation is uncertain, hold for the duty officer; every send still needs approval. |
| Finance | Match invoice INV-4200 against purchase order and delivery note. Mei Tan, the fictional finance lead, reviews the exact supplier query and payment batch separately. A match does not authorise payment. |
Worked handoff: a delivery document across two cities
Outcome: Prepare the evidence and a short request for the missing document for PO-TH-18. Steps: read only the authorised order and delivery records, identify the gap, draft a request. Gate: the operations approver reviews recipient, body and attachment; the operations director is backup. Record: source versions, draft, exact approval, intent and send receipt, with restricted retention.
The approval card says 16 November 2026, 09:00 Asia/Singapore (UTC+08:00) = 08:00 Asia/Bangkok (UTC+07:00). Store an offset-bearing timestamp and display both zones; do not write only “tomorrow at nine.” Spell out dates rather than guess whether 11/12 means November or December.
Bilingual teaching card — English and romanised Thai (pending native-speaker review). English: “Total THB 4,200. Payment is not yet approved.” Thai (romanised): “Yot ruam THB 4,200. Yang mai anumat hai chamra ngoen.” Preserve the original currency; SGD 4,200 is a different amount and must never be substituted. The fictional bilingual review record accepts the amount and the absence of payment authority. If a translation changes that meaning, the card is held for a bilingual reviewer and must be approved again after correction. This is a simulated review example; native-script localisation and an independent Thai-language review remain pending verification before real teaching use in Thai.
Mei's finance version might say: “Collect authorised invoices, match them, draft queries and prepare a batch. Do not send or pay until I approve the exact action.” Adding an attachment after approval changes the action: return it for approval. A vague “looks good” in an unrelated chat is insufficient.
Try it
Choose any one of the four roles above. Deliver one page containing:
- A two-sentence outcome and its exclusions.
- The actual steps, allowed sources and proposed changes.
- Every send/pay/delete stop, named approver, backup and timeout behavior.
- A completed access/privacy/stop preflight and a log/retention plan.
- One fictional normal case and one exception. Show what remains held and why.
A reviewer should be able to find the missing delivery document, unsupported sales claim, conflicting support policy or invoice mismatch from your evidence. Attractive wording cannot compensate for an unsafe handoff.
Check yourself
- Does a chatbot interface prove that a tool cannot act?
- Does a clean invoice match, a small payment or an expired timer permit execution?
- What if the bilingual review is uncertain or an attachment changes?
Answers
- No. Inspect its tool access, authority and controls; interface labels overlap.
- No. Academy send/pay/delete policy requires the named person's approval of that exact action, alongside adequate access. Timeout holds or escalates.
- Hold the action. Resolve uncertainty with the appropriate reviewer, then create a fresh approval for the changed content. Record the decision without keeping personal data forever.