Help and ownership
Calling in human help
Know when to keep working with Patsy, when to use direct controls, and when a person should take over.
What you should take away
- Product help and hands-on services are not the same thing.
- Migration and custom implementation are quoted before work begins.
- The in-app handoff carries the active mode, conversation, recent messages, relevant shared facts, and problem summary.
- Urgent client, payment, privacy, or domain issues deserve direct human review.
Choose the right kind of help
Ask Patsy for an explanation or prepared change
Use Patsy when the request is clear, reversible, and easy to review, such as revising a page, organizing supplied facts, or preparing a draft.
Use product support for a product problem
PA Digital Studio is the accountable company behind Patsy. Essential and Studio both include shared-context human product support by request.
Scope hands-on service separately
Migration, custom implementation, and having a person operate parts of the studio are separate services. They should have an agreed scope, price, responsibility, and timeline before work starts.
Make a handoff useful
Describe impact and urgency
Say who is affected, what is blocked, and when the issue becomes harmful. A live client-payment problem is different from a design preference.
Preserve the current state
Avoid deleting records, changing DNS repeatedly, or rebuilding an automation while asking for help. Save the relevant link, screen, message, and recent change.
Confirm what context transfers
The request includes the workspace, active mode, conversation, recent messages, relevant shared facts, and a concise problem summary. Studio shows pending, assigned, or resolved status. An asynchronous reply is labeled Your human support and remains in the same conversation after reload.