Campaign insights · 7 November 2026 · Knowix
An AI Agent Launch Demo Script for X: Approve or Decline?
Use this worked demo script to show where an AI agent waits for permission, what approval triggers, and what stays pending or stops when a user declines.
Show both decisions in the demo
If your AI agent needs permission to act, build your X launch demo around the moment a user grants or declines it. Show what the agent proposes, what the user can review, and what happens after each choice. Record both paths from the same starting state so the viewer can see what the decision changes. Put the approval in the first clip and in the launch copy so people know what they are agreeing to try.
Use one consequential action that makes sense to your buyer. In the hypothetical example below, a purchasing agent reads a supplier’s delivery update and proposes changing the expected arrival date on a sample purchase order. It can prepare the change. The buyer has to approve it before the agent writes to the purchasing system.
Write the narration around the decision
Open on the supplier update and the affected order. Say, “The supplier moved this delivery to Friday. The agent has found the order and prepared a date change for review.” Keep the current date and proposed date legible in the frame. Use a sample account and invented order data so the recording can show the details without exposing a customer or supplier.
When the approval appears, pause long enough to read the action and its destination. Say, “I can see which order and field will change before I approve.” If your product shows why it proposed the change, show that context. If it only shows the proposed value, describe exactly that. Anthropic’s guide to building agents explains why human checkpoints can be useful in agent workflows. The behavior you can claim in your launch comes from the build your team verifies.
Two takes from the same approval screen
Start at the order
Show a supplier update moving delivery from Wednesday to Friday. Open the sample order so the current Wednesday date is visible.
Hold on the proposed change
Show the agent waiting for a decision, with the affected order and the Wednesday-to-Friday change visible.
Take A: approve
Approve the change and open the sample order to show Friday in the expected delivery field.
Take B: decline
Replay the approval screen, decline the change, and open the order to show Wednesday still in place.
End each take with evidence of the result
An approval click tells the viewer the user agreed. Open the destination to show whether the update actually happened. If the action is asynchronous, keep “approved” and “completed” separate in your narration and show the result when it is available. In the decline take, show the order field still holding the original value. If your product keeps the proposal for later review, tell viewers what remains pending and where.
Record the branch your product supports. Some agents let users decline a proposal. Others let them leave it awaiting approval. If your product has no decline control, show the pending state and the unchanged order instead. If users must change the proposed value by editing the order themselves, keep that manual step visible. The point is to answer the buyer’s question about who can change what.
Before recording, write down which account role you used, which integration is connected, and which release the clip shows. Ask your product reviewer to repeat both takes from the same sample order and check the field after each decision. If the experience changes by role or access level, name the one in the clip. That gives the creator a specific fact to carry into their post and tells viewers whether they can reproduce the workflow.
Use the same wording in launch copy and creator posts
Turn the demo into one sentence the team can approve: “It proposes an order update from a supplier message and applies it after you approve.” Use that sentence as the factual anchor. A creator can explain why reviewing the exact date matters to their audience or show the decline branch. Give them the same approved build or a clip they can accurately describe, plus the destination a viewer can actually access.
Put the critical distinction on screen and in the post text. X documents options for video captions and subtitles. Check the uploaded preview and make sure a viewer watching without sound can tell which take they are seeing. If a public sandbox differs from the campaign recording, say what a visitor can try before they click.
What we prepare for your launch on X
Your team brings the working product, safe sample access, verified facts, the launch goal and final approvals. We build the campaign strategy around the buyer’s task, write the launch post and demo script, brief relevant creators on the approved workflow and coordinate when the posts go live. For agreed follow-up, we can turn recurring questions about the approval step into a short clarification or another approved clip. Your product team remains the source for what the agent does after a decision.
How we help
We help AI companies launch their products on X. We handle campaign strategy, launch posts, demos, creator coordination and content after launch. You bring the product, access for a demonstration and approval of the campaign.
Tell us about your launch ↗Sources and campaign evidence
Explore your launch
Frequently asked questions
Do both approval outcomes need to fit in one X post?
No. Use both when the main claim depends on the choice. If the second take needs more explanation, use an agreed supporting post and keep the approval requirement visible in the launch clip.
What if a user can only leave the action pending?
Show the pending screen and the unchanged destination. Use the wording your product uses and make clear what has to happen before it can act.
Should we show the agent changing a real purchase order?
Use a sample account or an approved sandbox. Confirm that it reproduces the behavior you describe and that every visible record is safe to share.
What should creators receive for this demo?
Give them the approved script notes, safe recording or access, the exact action boundary and the correct launch link. Agree on what they can record and who checks the claims.
How can you help if our agent demo is already recorded?
We can review the footage against your X launch message, identify which evidence is missing, and prepare the agreed launch copy, creator briefs, timing and follow-up.