#Before the call
The customer creates a UiPath Community account, installs Studio on the Windows machine where the work happens and installs Zoom if a remote working session is needed. They should have the SME, the process and representative test data ready.
#Choose the process
Start with one process that has a clear owner and a visible outcome.
#During the call
The SME demonstrates the process on their machine. With explicit consent, the developer can observe or take control through the agreed remote-session tool. The session captures the conversation, application steps, screenshots and target information needed to build the draft.
#After the call
AutoHub stores the evidence. Process Scribe produces the process specification. The SME reviews and approves it. Only then does Builder generate a workflow draft for developer review and packaging.
#The handoff
The customer receives a reviewable UiPath project or package, setup notes, known limitations and a test result. Credentials are configured by the customer in their own environment; they are never sent as part of the evidence bundle.