# Share a customer onboarding pack through a controlled AI connection Canonical: https://opendataroom.com/guides/customer-onboarding-ai-pack Updated: 2026-10-17 Prepare the customer next-step checklist from the approved onboarding plan. Keep the relevant documents in OpenDataRoom, then let your own or the recipient’s compatible AI work from that selected evidence. You choose the sources, access and sharing window. ## How OpenDataRoom helps Market: Customer success and implementation teams Prepare the customer next-step checklist from the approved onboarding plan. Keep source documents organised in drops, like folders, and select named packs for each audience. OpenDataRoom manages access and request records; the recipient uses their own AI for analysis. Current AI tools return extracted text, not complete original files. - [Named recipients and separate packs](/guides/separate-packs-per-audience): Choose who can connect. Prepare separate packs when people are allowed to see different documents. - [Source access for your AI](/guides/ai-document-connection): Let a compatible AI list, search and read the supplied text. Ask it to cite the file and passage so you can check the answer. - [Access deadlines and revocation](/guides/time-limited-ai-access): Choose a review window and stop future requests when it ends. Previously retrieved copies cannot be recalled. ### Workflow impact The customer can ask their own AI what remains before the next milestone using the same approved plan and checklist. The delivery team can focus the next meeting on outstanding decisions rather than resending the project context. ### Bring these documents - Implementation plan.md - Readiness checklist.md ### Prompt for your own compatible AI Using only this approved pack, prepare the customer next-step checklist from the approved onboarding plan. Start with this source question: What is the next step before our test import? Cite the file and passage. Distinguish supplied facts, assumptions, missing evidence and contrary evidence. Do not infer human reading or investment intent from request records. Review the AI draft against the originals, resolve open questions with the document owner, and take the checked result into your own meeting, report or customer response. ## Frequently asked questions ### What would this change in my workflow? The customer can ask their own AI what remains before the next milestone using the same approved plan and checklist. The delivery team can focus the next meeting on outstanding decisions rather than resending the project context. The practical task is to prepare the customer next-step checklist from the approved onboarding plan. ### Which documents should I include? For the example on this page, start with Implementation plan.md, Readiness checklist.md. Use the approved versions relevant to the task and include source dates, definitions and any known gaps. Review the prepared text and disclosure scope before sharing. The fictional examples illustrate the structure; OpenDataRoom does not supply or verify your underlying research. ### How do I keep the information current for staff or customers? Assign a document owner, include version and effective dates, and review the content before sharing it. When a source file changes, use the drop update flow and review the affected permissions. After an update is accepted, fresh requests to existing packs serve the current versions of their selected files. Previously retrieved material in an AI chat does not refresh automatically. Newly added files stay private until selected, and changed excerpt selections need review. Access-change notices are queued for affected recipients; provider acceptance is not proof of inbox delivery. Tell recipients which effective date applies. ### How does the recipient connect, and who gets access? Choose your own AI or invite the intended email recipient. For a private invitation, the recipient verifies the authorised email and completes the required approval flow, then adds the connection in a compatible AI app’s settings. Forwarding an invitation alone does not authorise a different email. Permission covers the selected pack; create separate packs when audiences may see different documents. ### Can I keep the files and end someone’s access? Your wallet contains source drops, like folders. Each named pack shares selected files or passages from one drop. The source drop and its access packs have separate deadlines. You can keep the source until its displayed retention deadline while ending a recipient’s future access. Choose a sharing window, revoke it earlier when needed, and approve an extension deliberately. Expiry cannot recall material that an AI app or recipient has already retrieved. ### What happens when I update or remove a file? After you review and accept a drop update, fresh authorised requests receive the current versions of files already selected for their packs. This does not force an AI to fetch the files again or refresh its existing chat context. New files do not join those packs automatically. Review changed selected passages explicitly. Removing a file or its permission stops future retrieval, and access-change notices are queued for affected recipients. Provider acceptance is not proof of inbox delivery. This cannot erase content already retrieved. ### What if my files or AI app are not supported? Check the compatibility guide and try the public service-information sample first. An app must support the required MCP connection and authorisation; pasting a URL into ordinary chat does not install it. Use supported text-based files and inspect the preparation report. Originals are retained in encrypted storage, but the current AI tools return extracted text, not complete original files. Charts, images and layout are not faithfully delivered by those tools. Image-only scans and standalone images are refused; no OCR, audio transcription or spreadsheet recalculation is provided. Current pilot limits are listed on the pricing page. ### What information is recorded about use of the pack? The ledger records requests received by the service, authorised connection references, requested source information and preparation outcomes. Recipients can also deliberately submit a request, comment or note after approving the exact text. The owner sees that message, the verified connection identity and time in Recipient inbox for up to 90 days, unless deleted sooner. Received does not mean read or answered; no agent or automatic research is started. It does not record the entire AI conversation. Search text is supplied by the AI and may differ from the human question. An AI can reuse retrieved material without making another request. Literal search can miss relevant material; neither a search nor a file request proves that the AI reviewed the entire pack. Owners can investigate no-match searches before deciding whether to clarify wording, repair extraction or add information. A no-match result alone is not proof that a document is missing. ### Who can read my files in the hosted connection? Private-library file names and contents are encrypted in the browser with your wallet key. A hosted AI connection uses a separate access copy that you approve and that the service can decrypt for authorised retrieval. The receiving AI gets the content it retrieves and applies its own data policies. An optional desktop connector can decrypt locally, but it requires installation and is not a universal mobile connection. Review the security and compatibility pages before choosing a route. ## Your working output A customer-specific checklist before the next delivery meeting ## Before you share 1. Bring the approved, dated versions of: Implementation plan.md, Readiness checklist.md. 2. Check the readable text, source dates and permitted audience. 3. Choose your own compatible AI or invite the intended recipient with an appropriate access deadline. 4. Check the result against the source before using it; retain open questions rather than filling gaps. ## Fictional example documents These are invented teaching documents, not customer evidence. ### Implementation plan.md Fictional Project Willow requires the customer to appoint an owner and approve the field mapping before a test import. ### Readiness checklist.md An owner is appointed. Field mapping is still awaiting customer approval. No production import is scheduled. ## A source question What is the next step before our test import? Illustrative answer: Approve the field mapping. The owner requirement is already met; the supplied plan does not schedule a production import. ## Sources and further reading ## Related workflows - https://opendataroom.com/guides/hotel-guest-information-pack - https://opendataroom.com/guides/product-documentation-ai-pack - https://opendataroom.com/guides/partner-documentation-ai-pack Admission is by invitation. Join the waiting list: https://opendataroom.com/signup Check compatibility and the separate public service-information sample: https://opendataroom.com/compatibility ## Try the fictional example https://opendataroom.com/example-demo.html?example=customer-onboarding-ai-pack