A BETTER WAY TO SHARE THE WORK
Give your customer a clear path to their first useful result
Your customer should know what happens next, what you need from them, and what success will look like.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
How do I create a customer onboarding plan with an AI agent?
Give your agent the agreed customer outcome, kickoff notes, prerequisites, and confirmed owners on both sides. Ask for a customer-facing plan that leads with the first useful result and the next action—not a tour of every feature. Review the draft, then share a readable page while keeping task updates and approvals in your existing tools.
01 / SEE THE DIFFERENCE
A first report, with responsibilities on both sides
A fictional customer and reporting service. These supplied kickoff facts become a shared path, not a claim that onboarding is complete.
Cedar Studio and Signal Desk agreed the first useful result: review one weekly campaign summary, identify one change, and record one next action. Mira must confirm the campaign and supplied field meanings; pending. Theo prepares the draft only after those inputs. Jules checks totals against the supplied source and records the action in the existing project thread. Review is proposed within five working days after required inputs are confirmed; no date booked. A synthetic sample can demonstrate the format while waiting, but it does not count as customer first value. Live connections and wider rollout are excluded. First value is not yet achieved.
- First useful result
- Review one weekly campaign summary, identify one change, and record one next action. First value is not yet achieved.
- Customer next step
- Mira confirms the campaign and supplied field meanings. These inputs are pending.
- Vendor next step
- Theo prepares the draft after required inputs are confirmed. A synthetic sample may demonstrate the format but does not count as customer first value.
- Evidence
- Jules checks totals against the supplied source and records the action in the existing project thread.
- Timing and limits
- Review proposed within five working days after required inputs are confirmed; no date booked. Live connections and wider rollout are excluded.
Open a complete fictional HTML example, with its source notes →
Create my customer onboarding plan02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
Agree on one first useful result
Start with what the customer bought the service to accomplish. 'Attend training' is an activity; 'review one report and choose a next action' describes a useful result. Use the customer's agreed definition and evidence. If they have not agreed one, make that the next question rather than inventing a success target.
Show what each side needs to do
Separate customer inputs from vendor work. Attach each prerequisite to the work it unlocks and name the confirmed owner. A vague request to 'finish setup' hides whether the customer needs to supply information or the vendor needs to prepare something. Keep credentials and sensitive source material out of the page.
Make the sequence honest
Show a few milestones with the input, output, and reviewer for each. Preserve dependency-based timing: five days after inputs arrive is not the same as a booked date. Label blocked, proposed, and unconfirmed work in words. A sample demonstration can help while waiting, but it is not evidence the customer's actual outcome has been achieved.
Lead with the next action, not the whole backlog
Put the immediate request near the top, followed by responsibilities, milestones, and supporting resources. Explain what is excluded from this first phase so a pilot does not look like a full rollout. Include the confirmed route for questions without inventing a response-time promise.
Review the plan with the customer in mind
Check that a customer can tell what they need to provide and what you will do next. Verify the audience, links, evidence and dates before sharing. Show a snapshot date and plan owner. Record progress, changing commitments, and customer confirmation in the agreed project workflow; update the reading page after review.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
Using only materials I provide or have authorized you to access, create a customer onboarding plan for [customer] and [service]. Ask only for missing essentials: the agreed first useful outcome, scope and exclusions, customer and vendor owners, prerequisites, evidence of success, timing conditions, and the approved help and tracking channels. Separate agreed goals from proposed goals. Lead with the customer's next action and show what vendor work it unlocks. For each milestone state the prerequisite, output, confirmed owner, and reviewer. Preserve unresolved inputs and dependency-based timing; do not invent calendar dates, commitments, permissions, provisioning steps, completed tasks, or evidence that first value has been achieved. A sample demonstration is not proof of customer success. Keep credentials and private source material out of the page and include only audience-safe details and approved links. Create readable static HTML with no scripts or forms. Use my saved artifact style if available. Include the supplied snapshot date and plan owner, and keep authoritative progress and approvals in our existing project workflow. Show me the draft and unresolved questions for review. Do not publish or change access without separate explicit approval.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- Is the customer's agreed first useful result clear, with evidence rather than a generic completion percentage?
- Can each side identify its next action, owner, and dependency?
- Are dates and commitments agreed, proposed, or unresolved exactly as the sources state?
- Is a sample demonstration clearly different from the customer's actual result?
- Are sensitive inputs, credentials, and internal-only notes excluded?
- Does the page name its snapshot owner and explain where updates and questions belong?
When HTML fits
A customer-ready reading page assembled from your authorized kickoff notes, outcome agreement and task records. Use it to make the shared plan understandable without requiring the customer to learn another editor just to read it.
When another format fits better
Use an onboarding or project platform when customers need to submit inputs, update tasks, receive automated reminders, or track live progress. Keep provisioning, credentials, approvals, and authoritative completion records in their existing systems. This page explains the plan; it does not execute it.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
How is this different from a new-hire onboarding guide?
A new-hire guide helps an employee do their first tasks and find internal policies. A customer onboarding plan coordinates two organizations around a purchased service: agreed value, customer prerequisites, vendor work, and evidence that the first outcome has been reached.
What if the customer has not supplied the inputs yet?
Name the missing inputs, the confirmed owner, and the work waiting on them. Keep any dependent date conditional. You can offer a clearly labeled sample if appropriate, but do not mark the customer's outcome achieved because a demonstration worked.
Can the customer check off tasks on this page?
No. It is a static reading page, not a live checklist. Direct the customer to the agreed project workflow for updates and questions, then revise this snapshot after reviewing those changes.