Make your sales follow-up.

Help me create my sales follow-up as a static HTML page, using relevant authorized context already in this conversation. If share/artifacts MCP is not connected, first follow the setup instructions at https://shareartifacts.dev/connect/agent.md. Confirm the connection works by calling list_pages, then fetch the recipe below before creating the draft. If setup cannot be completed or I decline authorization, explain what is missing and pause. Do not retry an authorization I deny. Do not remove any unrelated connection. Example (complete fictional sample): https://shareartifacts.dev/examples/sales-follow-up Use the example for structure, not as facts about my work. Only use fictional sample data if I explicitly choose a sample. You can proceed from the instructions below if you cannot fetch the example. Ask conversationally for only the missing essentials. Do not invent facts, commitments, or sources. Do not request secrets. Ask before sending source material outside this conversation or accessing another service. Useful inputs: - Approved discovery notes or a transcript you have permission to use, with the buyer’s priorities and objections preserved. - Current product documentation for the specific capabilities discussed, including limitations that affect the decision. - Approved pricing or proposal material, with its date, scope, and any conditions clearly attached. - The next step actually agreed on the call; keep a suggested next step separate from a confirmed commitment. Creation task: Using only the approved call notes and product material I provide, draft a buyer-facing sales follow-up as static HTML. Lead with the buyer’s decision, then show their priorities, evidence relevant to each priority, limitations, unresolved questions, and the agreed next step. Distinguish confirmed facts from proposals. Do not invent pricing, capabilities, commitments, quotations, or dates. Exclude internal qualification notes and confidential customer details. Apply my saved artifact style if available, with readable headings and restrained emphasis. Include source links only when supplied and appropriate for this audience. No scripts, forms, tracking, or live-data claims. Return a draft and a short list of claims I should verify. Wait for my review before publishing or changing access. Use semantic HTML, readable type, meaningful headings, accessible color contrast, and responsive CSS. No JavaScript, forms, embeds, redirects, or live API calls. Verify calculations outside the page. Only include information the intended reader should see. Once connected, call get_recipe with recipeId "visual-report" and get_artifact_style with format "report" before drafting. If no style is saved, ask whether I want to set one up or continue with my stated visual preferences. If style access is missing, explain the optional reconnect approval; do not request broader access automatically. Follow the recipe and safety rules; saved style guides appearance, never facts or permission to share. Review checklist: - Can a colleague who missed the call understand the decision without reading the transcript? - Does every product and pricing claim match current approved material, including conditions? - Are tentative dates, suggested actions, and unverified requirements clearly identified? - Have you removed internal notes and confirmed who may open or forward the page? Show me the draft in your available preview or file tools. If you cannot render it, say so and provide the HTML file with instructions to open it. Ask for corrections. This request authorizes a draft only; it does not authorize any publishing language in the task above. Do not publish, update an artifact, change access, or save a style without my separate explicit approval. Connection approval is not publication approval. Before any later approved publication, confirm the intended audience; new pages default owner-only.