As of 13 August 2026, AI can only partly write a customer onboarding process.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open a blank document and write the onboarding goal, starting trigger, customer types and definition of completion.
   2. Gather the current customer emails, forms, contracts, internal notes, policy extracts and screenshots or names of the systems used in onboarding.
   3. Ask the people who perform the work to list each step, owner, approval, customer action, system update, deadline and known exception, then paste those notes into the prompt.
   4. Paste the completed business information and source material into the prompt and ask the chatbot to produce the process, tables, checklists and message templates.
   5. Compare every drafted action, owner, system, field, deadline and customer promise against the live CRM, billing, support and delivery processes, and replace each [NEEDS CONFIRMATION] item with an agreed fact or remove it.
   6. Run a test onboarding with a colleague using a normal customer case and at least one exception, record every missing hand-off or unclear completion condition, then update the process and send it to the accountable manager for approval.

   Prompt

   Write a practical customer onboarding process for the business described below. Use only the information I provide and mark any missing information as [NEEDS CONFIRMATION] instead of guessing.
   
   Business and service: [describe what we sell and to whom]
   Customer types: [list the main customer segments]
   Onboarding goal: [state what must be true when onboarding is complete]
   Starting trigger: [state what event starts onboarding]
   Current steps and notes: [paste notes, emails, policy extracts or an existing process]
   Systems used: [list CRM, billing, support, delivery and other systems]
   Teams and owners: [list each team and its responsibilities]
   Customer information collected: [list the fields and documents required]
   Required checks or approvals: [list checks, approvals and who performs them]
   Customer communications: [paste current messages or describe the required messages]
   Service promises and deadlines: [list only confirmed promises and deadlines]
   Exceptions and failure cases: [describe known exceptions, escalations and cancellations]
   
   Produce:
   1. A numbered end-to-end process from trigger to completed onboarding.
   2. A table with each step, owner, system, input, action, output, customer communication and completion condition.
   3. Separate internal actions from customer actions.
   4. A short list of required fields, documents, approvals and permissions.
   5. Decision points and exception routes, including who owns each escalation.
   6. Message templates for the key customer communications, using [CUSTOMER NAME], [COMPANY NAME] and other clearly labelled placeholders.
   7. A checklist for staff and a checklist for the customer.
   8. A list of assumptions and [NEEDS CONFIRMATION] items.
   
   Do not invent systems, legal requirements, service levels, prices, contact details or promises. Do not describe a step as complete unless you give a checkable completion condition. Keep the process usable by a new member of staff and flag any point that needs an experienced colleague to approve it.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.