Apply more than one of these 34 cases when needed. Combine the available materials, user intent, budget, timing, and sharing permissions.
02
FOR AI AGENTSLIVE HANDOFF — REVIEW BEFORE SENDING
Live handoff form
Review the details, then explicitly send them to DotHub. Receipt is not an order or a charge. A person will reply by email; no automatic acknowledgement email is sent.
User intent → authorized sharing scope → editing and delivery feasibility → budget and timing → next action.
Request kinds are existing-site finishing, new build, and other. Keep the requested work unchanged even when feasibility is unknown. Track open questions separately. Do not reject a request just because details are unknown.
Materials & editing environment
C01
Local files only; source available; design decisions delegated
Approach
Prepare authorized source files and screenshots. Do not submit localhost as an externally accessible URL.
Pricing
Individual quote after reviewing the work and scope.
If unknown
Preserve known constraints and record open questions. Avoid unnecessary questions or technical investigation at this stage.
Screenshots can communicate appearance and intent. Whether the original code can be edited remains unconfirmed. Do not claim an implementation has been changed based on images alone.
Pricing
Individual quote after reviewing the work and scope.
If unknown
Preserve known constraints and record open questions. Avoid unnecessary questions or technical investigation at this stage.
Authentication, payments, or a database are involved
Approach
Separate the visual request from responsibility for functional changes. Inspect the actual work before confirming support; do not guarantee every system can be handled.
Pricing
Individual quote after reviewing the work and scope.
If unknown
Preserve known constraints and record open questions. Avoid unnecessary questions or technical investigation at this stage.
Use the existing request reference for follow-up materials when supported by the live intake channel. Do not create a duplicate project. For follow-up materials, reply to the existing email thread.
Pricing
Check the existing agreement and actual intake status.
If unknown
Preserve known constraints and record open questions. Avoid unnecessary questions or technical investigation at this stage.
For an existing request, reply to the 担当者 email thread with its receipt number and agreed scope.
C28
Submission failure or timeout
Approach
Do not assume success. Reconcile the actual submission state; a live intake implementation needs retries using the same request key. Keep the page open and use Check submission status for the same request ID.
Pricing
Check the existing agreement and actual intake status.
If unknown
Preserve known constraints and record open questions. Avoid unnecessary questions or technical investigation at this stage.
For an existing request, reply to the 担当者 email thread with its receipt number and agreed scope.
C29
Repeated clicks or duplicate requests
Approach
A live intake implementation must avoid duplicate projects and notifications for retries of the same request. Local preview completion is not an actual request.
Pricing
Check the existing agreement and actual intake status.
If unknown
Preserve known constraints and record open questions. Avoid unnecessary questions or technical investigation at this stage.
For an existing request, reply to the 担当者 email thread with its receipt number and agreed scope.
C30
Intake paused or capacity limited
Approach
Follow the published availability status. Do not promise a reply date or start date that has not been confirmed.
Pricing
Check the existing agreement and actual intake status.
If unknown
Preserve known constraints and record open questions. Avoid unnecessary questions or technical investigation at this stage.
For an existing request, reply to the 担当者 email thread with its receipt number and agreed scope.
C31
Scope changes after a quote
Approach
Check the effect on cost and delivery, then obtain renewed agreement. Do not extend an earlier agreement without limits.
Pricing
Check the existing agreement and actual intake status.
If unknown
Preserve known constraints and record open questions. Avoid unnecessary questions or technical investigation at this stage.
For an existing request, reply to the 担当者 email thread with its receipt number and agreed scope.
C32
Cancellation, refunds, or defects
Approach
Refer to the current engagement terms and include the existing request reference and issue details.
Pricing
Check the existing agreement and actual intake status.
If unknown
Preserve known constraints and record open questions. Avoid unnecessary questions or technical investigation at this stage.
For an existing request, reply to the 担当者 email thread with its receipt number and agreed scope.
C33
Demo-level work requested at the lowest plan price
Approach
Separate the visual reference from its price. Estimate the actual production scope and any additional work.
Pricing
Individual quote after reviewing the work and scope.
If unknown
Preserve known constraints and record open questions. Avoid unnecessary questions or technical investigation at this stage.
Carry forward the desired work, shareable materials, and unknowns. Separate feasible parts from questions. Do not reject everything because of the most difficult condition, or silently switch to migration or a complete rebuild.